<div dir="ltr">Hi Barry,<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
An update has been pushed to 2.8, you might want to try again the auto-provisioning. Again, the restriction still applies that if you've an SRV record behind your SIP domain, it will still not work, as Jitsi doesn't do SRV for XCAP URIs. Should work in most other cases now though.<span class="HOEnZb"><font color="#888888"><br>
<br></font></span></blockquote><div><br></div><div style>Thanks Andreas. We do use SRV so it won't do anything for me at present. For testing I have just set the auth_db use_domain parameter to 0 in the proxy as usernames are unique anyway. </div>
<div style><br></div><div style>-Barry</div><div style><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
Andreas</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 05/22/2013 12:53 PM, Andreas Granig wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
On 05/17/2013 02:03 PM, Barry Flanagan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 17 May 2013 12:51, Oliver Vermeulen <<a href="mailto:oliver@oliverv.com" target="_blank">oliver@oliverv.com</a><br>
<mailto:<a href="mailto:oliver@oliverv.com" target="_blank">oliver@oliverv.com</a>>> wrote:<br>
<br>
Change authentication to username@sipdomain and passwd ,<br>
provisioning put only username and password.____<br>
<br>
__<br>
<br>
<br>
I'm not sure what you mean. Change which? Provisioning credentials in<br>
Jitsi are currently user@domain. SIP authentication is working fine. It<br>
is only xcap auth which fails.<br>
</blockquote>
<br>
The problem with the Jitsi auto-provisioning and XCAP is that it<br>
currently uses the IP of the load-balancer as host part of the URL,<br>
instead of the SIP domain of the user.<br>
<br>
What you can try is making a csc.conf.customtt.tt2 in<br>
/etc/ngcp-config/templates/<u></u>etc/ngcp-www-csc/ and change the "host" to<br>
the SIP domain you're using. A more flexible way is to modify<br>
/usr/share/perl5/Sipwise/<u></u>JitsiProvisioning.pm and change this line:<br>
<br>
my $xcap_ip = $cfg->{uaprovisioning}->{xcap}<u></u>->{host};<br>
<br>
to something like<br>
<br>
my $xcap_ip = $domain;<br>
<br>
The problem with that approach is that it only works if the domain part<br>
of your SIP URI resolves to your CE IP in an A or AAAA record and<br>
doesn't point to a different host via SRV (e.g. your SIP domain is<br>
<a href="http://sip.example.org" target="_blank">sip.example.org</a>, and this resolves to the IP of the CE, instead of<br>
having an SRV record <a href="http://sip.example.org" target="_blank">sip.example.org</a> resolving to something else like<br>
<a href="http://ce.sip.example.org" target="_blank">ce.sip.example.org</a>, because Jitsi doesn't do an SRV lookup for the XCAP<br>
host).<br>
<br>
In any case, the second approach should work quite well in cases without<br>
SRV. We're going to push a fix for that in the next days.<br>
<br>
Andreas<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/<u></u>listinfo/spce-user</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/<u></u>listinfo/spce-user</a><br>
</div></div></blockquote></div><br></div></div>