Hi Peter,
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.
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).
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?
Thank you very much.
Best Regards,
Laura
Message: 2
Date: Tue, 19 Apr 2011 10:17:34 +0100
From: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Subject: Re: [sr-dev] Presence problem
To: Development mailing list of the sip-router project
<sr-dev(a)lists.sip-router.org>
Message-ID: <1303204654.4056.10.camel@pd-laptop-linux>
Content-Type: text/plain; charset="utf-8"
Hi Laura,
I have recently been testing presence with Kamailio as well.
- The change status of the presentity is
immediately visible
by watcher with the only exception, when the user goes offline, the
presentity keeps online in the watcher buddy list, any idea? Can you
help me?
I have had the same issue with clients I was testing with. In my case
it turned out to be problems with the client.
You should take a LAN trace from the client side and check that the
client logging out is properly updating presence status on log-out. If
that is OK, then take a trace on the client still logged in, it could be
that the client is receiving the status update but not displaying it.
The xcap table is empty. Do I need to configure also the xcap table?
Or it?s automically done by kamailio presence server?
The xcap table will be empty for new subscribers. When the client
requests a document (of supported type) from Kamailio that is not on the
server it will get a "404 Not Found" response. The client should then
create a new document (with sensible defaults for the client) on the
server using an HTTP PUT.
If the client requests a document that is not of supported type Kamailio
will return a "500 Server Error" response and the client should continue
(if it can) without support for that document.
During my testing I came across a client that didn't support HTTP
authentication properly, so when Kamailio responded with a 401 the
client gave up instead of authenticating. Disabling HTTP authentication
(take out the "#!define WITH_XHTTPAUTH" line in kamailio.cfg).
Regards,
Peter
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd