[jitsi-users] Help with CUSAX?


#1

Is anyone available to help me get CUSAX working? I saw the instructions at
https://jitsi.org/Documentation/CUSAX and wondered how the experience might
improve on using a vanilla Jitsi (which I gather uses something called
Jingle instead). Is CUSAX even useful for two desktop Jitsi users to
communicate with each other?

Presumably, Step 0: Get a SIP account somewhere and enter it into the Jitsi
client on the Accounts tab.

Step 1: Provisioning. I don't know how to do this, and it's apparently not
required, so I'm skipping it.

Step 2: I assume all I have to do here is go to Tools > Options, go to the
Advanced tab, go to the Property Editor, click the disclaimer button, find

net.java.sip.communicator.impl.protocol.jabber.accXYZ.CALLING_DISABLED=false

in there (where XYZ is some long digit sequence), and set it to true.

Step 3: "Make sure every XMPP user’s vCard in your XMPP installation
contains a phone (and potentially a video) number for the corresponding SIP
account." I can't find any vCard setting in the options dialog. Does this
have something to do with Tools > Account Info? Please explain.

Step 4: Again, I assume this just requires going back to the Property
Editor screen, clicking Add, and typing in

net.java.sip.communicator.impl.protocol.sip.accsip1.cusax.XMPP_ACCOUNT_ID=accXYZ

where XYZ is the same digit sequence as above. Perhaps I'd have to select
the SIP account on the Accounts tab first?

Step 5: SIP INVITEs. No idea how to do this.

···

--
Jason Melancon


#2

Hi Jason,

Is anyone available to help me get CUSAX working? I saw the instructions
at https://jitsi.org/Documentation/CUSAX and wondered how the experience
might improve on using a vanilla Jitsi (which I gather uses something
called Jingle instead). Is CUSAX even useful for two desktop Jitsi users
to communicate with each other?

Jitsi uses Jingle for calls over XMPP. CUSAX is a way of making it use
SIP instead. It more or less just "maps" Jabber contacts to SIP contacts
and hands off the calling feature to the SIP protocol implementation. No
more magic ;).

It is useful in that SIP appears to be more reliable for calls. I do
not really know why, because the signalling layer is somewhat
independent of the call itself, but I imagine that the main reason is
the broad colelction of features available through SIP in terms of PBX
and stuff.

Presumably, Step 0: Get a SIP account somewhere and enter it into the
Jitsi client on the Accounts tab.

Right.

Step 2: I assume all I have to do here is go to Tools > Options, go to
the Advanced tab, go to the Property Editor, click the disclaimer
button, find

net.java.sip.communicator.impl.protocol.jabber.accXYZ.CALLING_DISABLED=false

in there (where XYZ is some long digit sequence), and set it to true.

Not "some" digits, but the generated account ID. But I think that is
what you meant.

Step 3: "Make sure every XMPP user’s vCard in your XMPP installation
contains a phone (and potentially a video) number for the corresponding
SIP account." I can't find any vCard setting in the options dialog. Does
this have something to do with Tools > Account Info? Please explain.

You are about halfway right here. vCards are managed by the XMPP server
for every user. On most servers, users manage their vCards on their own
behalf. That would mean that every user has to enter their SIP
account/number in their vCard if you want to be able to call them, and
yes, that's what you can find at Tools→Account Info.

Step 4: Again, I assume this just requires going back to the Property
Editor screen, clicking Add, and typing in

net.java.sip.communicator.impl.protocol.sip.accsip1.cusax.XMPP_ACCOUNT_ID=accXYZ

where XYZ is the same digit sequence as above.

Yep.

Step 5: SIP INVITEs. No idea how to do this.

I imagine this is done automatically by any client implementing CUSAX.

Cheers,
Nik


#3

Is anyone available to help me get CUSAX working? I saw the instructions
at https://jitsi.org/Documentation/CUSAX and wondered how the experience
might improve on using a vanilla Jitsi (which I gather uses something
called Jingle instead). Is CUSAX even useful for two desktop Jitsi users
to communicate with each other?

No. Stick with calls over XMPP (Jingle).

Jitsi uses Jingle for calls over XMPP. CUSAX is a way of making it use
SIP instead. It more or less just "maps" Jabber contacts to SIP contacts
and hands off the calling feature to the SIP protocol implementation. No
more magic ;).

It is useful in that SIP appears to be more reliable for calls. I do
not really know why, because the signalling layer is somewhat
independent of the call itself, but I imagine that the main reason is
the broad colelction of features available through SIP in terms of PBX
and stuff.

It is primarily meant to provide reliable presence and chat for SIP accounts, not the other way round. You'll often find an existing SIP infrastructure for calling in a company. On top of that, you want presence. SIP SIMPLE or even XCAP would be alternatives to XMPP, but both aren't as reliable as XMPP and even less readily available.

Presumably, Step 0: Get a SIP account somewhere and enter it into the
Jitsi client on the Accounts tab.

Right.

Step 1: Provisioning. I don't know how to do this, and it's apparently
not required, so I'm skipping it.

Provisioning is meant for companies or providers to preconfigure Jitsi with all its accounts and settings from a central server.

Step 2: I assume all I have to do here is go to Tools > Options, go to
the Advanced tab, go to the Property Editor, click the disclaimer
button, find

net.java.sip.communicator.impl.protocol.jabber.accXYZ.CALLING_DISABLED=f
alse

in there (where XYZ is some long digit sequence), and set it to true.

Not "some" digits, but the generated account ID. But I think that is
what you meant.

Step 3: "Make sure every XMPP user’s vCard in your XMPP installation
contains a phone (and potentially a video) number for the corresponding
SIP account." I can't find any vCard setting in the options dialog. Does
this have something to do with Tools > Account Info? Please explain.

You are about halfway right here. vCards are managed by the XMPP server
for every user. On most servers, users manage their vCards on their own
behalf. That would mean that every user has to enter their SIP
account/number in their vCard if you want to be able to call them, and
yes, that's what you can find at Tools→Account Info.

Step 4: Again, I assume this just requires going back to the Property
Editor screen, clicking Add, and typing in

net.java.sip.communicator.impl.protocol.sip.accsip1.cusax.XMPP_ACCOUNT_ID=acc
XYZ

where XYZ is the same digit sequence as above.

Yep.

Step 5: SIP INVITEs. No idea how to do this.

I imagine this is done automatically by any client implementing CUSAX.

For outgoing calls yes. But calls coming in must also have this header so it needs to be set by the server, e.g. Asterisk.

Cheers,
Nik

Ingo