<div class="gmail_quote">
<div>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3">Hi Peter, </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3">thank you very much for the suggestion. In fact, with the XHTTP_AUTH enable, SIP Communicator (JITSI) doesn’t work with XCAP of Kamailio. With the XHTTP_AUTH comment out. The Presence authorization finally works, but partially.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3">When bob add alice as a contact, there is a authorization request popup to alice, and alice click accept, then the auth req result popup appear to alice saying the bob has accepted the request! After that, bob can see the presence status of alice correctly. But alice always see the bob is offline. In the xcap table, we see there is an entry in the rls (contact alice in the user bob entry) and another entry in the presence rules (contact alice in the user bob entry).</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3">But when I try to add bob as a contact from alice, nothing happen, there is no popup of authorization request to bob. And alice always see the bob is offline. Any idea?</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3">Thank you very much.</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3"> </font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3">Best Regards,</font></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Calibri" size="3">Laura</font></p></div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Message: 2<br>Date: Tue, 19 Apr 2011 10:17:34 +0100<br>From: Peter Dunkley <<a href="mailto:peter.dunkley@crocodile-rcs.com">peter.dunkley@crocodile-rcs.com</a>><br>
Subject: Re: [sr-dev] Presence problem<br>To: Development mailing list of the sip-router project<br> <<a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a>><br>Message-ID: <1303204654.4056.10.camel@pd-laptop-linux><br>
Content-Type: text/plain; charset="utf-8"<br><br>Hi Laura,<br><br>I have recently been testing presence with Kamailio as well.<br><br><br>> - The change status of the presentity is immediately visible<br>
> by watcher with the only exception, when the user goes offline, the<br>> presentity keeps online in the watcher buddy list, any idea? Can you<br>> help me?<br>><br><br>I have had the same issue with clients I was testing with. In my case<br>
it turned out to be problems with the client.<br><br>You should take a LAN trace from the client side and check that the<br>client logging out is properly updating presence status on log-out. If<br>that is OK, then take a trace on the client still logged in, it could be<br>
that the client is receiving the status update but not displaying it.<br><br><br>><br>> The xcap table is empty. Do I need to configure also the xcap table?<br>> Or it?s automically done by kamailio presence server?<br>
><br><br>The xcap table will be empty for new subscribers. When the client<br>requests a document (of supported type) from Kamailio that is not on the<br>server it will get a "404 Not Found" response. The client should then<br>
create a new document (with sensible defaults for the client) on the<br>server using an HTTP PUT.<br><br>If the client requests a document that is not of supported type Kamailio<br>will return a "500 Server Error" response and the client should continue<br>
(if it can) without support for that document.<br><br>During my testing I came across a client that didn't support HTTP<br>authentication properly, so when Kamailio responded with a 401 the<br>client gave up instead of authenticating. Disabling HTTP authentication<br>
(take out the "#!define WITH_XHTTPAUTH" line in kamailio.cfg).<br><br>Regards,<br><br>Peter<br><br>--<br>Peter Dunkley<br>Technical Director<br>Crocodile RCS Ltd<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.sip-router.org/pipermail/sr-dev/attachments/20110419/ede41163/attachment-0001.htm" target="_blank">http://lists.sip-router.org/pipermail/sr-dev/attachments/20110419/ede41163/attachment-0001.htm</a>><br>
<br>------------------------------<br><br>_______________________________________________<br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br><br>End of sr-dev Digest, Vol 30, Issue 39<br>**************************************<br></blockquote></div><br>