[Spce-user] xcap authentication issue with jitsi auto provisinoing

Andreas Granig agranig at sipwise.com
Wed May 22 06:53:18 EDT 2013


On 05/17/2013 02:03 PM, Barry Flanagan wrote:
> On 17 May 2013 12:51, Oliver Vermeulen <oliver at oliverv.com
> <mailto:oliver at oliverv.com>> wrote:
>     Change authentication to username at sipdomain and passwd ,
>     provisioning put only username and password.____
>     __
> I'm not sure what you mean. Change which? Provisioning credentials in
> Jitsi are currently user at domain. SIP authentication is working fine. It
> is only xcap auth which fails.

The problem with the Jitsi auto-provisioning and XCAP is that it 
currently uses the IP of the load-balancer as host part of the URL, 
instead of the SIP domain of the user.

What you can try is making a csc.conf.customtt.tt2 in 
/etc/ngcp-config/templates/etc/ngcp-www-csc/ and change the "host" to 
the SIP domain you're using. A more flexible way is to modify 
/usr/share/perl5/Sipwise/JitsiProvisioning.pm and change this line:

   my $xcap_ip = $cfg->{uaprovisioning}->{xcap}->{host};

to something like

    my $xcap_ip = $domain;

The problem with that approach is that it only works if the domain part 
of your SIP URI resolves to your CE IP in an A or AAAA record and 
doesn't point to a different host via SRV (e.g. your SIP domain is 
sip.example.org, and this resolves to the IP of the CE, instead of 
having an SRV record sip.example.org resolving to something else like 
ce.sip.example.org, because Jitsi doesn't do an SRV lookup for the XCAP 

In any case, the second approach should work quite well in cases without 
SRV. We're going to push a fix for that in the next days.


More information about the Spce-user mailing list