Hi again,
Then it is the time for Eugen to add it in his sip client and send the patch for enhancing kamailio's presence server with rfc4481, as well
:o)
I start my application, and make my own status be shown. I change my status back and forth a few times between Away and DoNotDisturb (each time a publish is sent), the status returned (in notify) is good. When I change my status to Online/Available (and only to this), kamailio returns a double tuple. Is it normal to have a double tuple? If yes, which one to choose (the one with latest timestamp)? Here it is:
NOTIFY sip:eugen.dedu@82.238.108.175:5060 SIP/2.0 CSeq: 7 NOTIFY Via: SIP/2.0/UDP 86.64.162.35;branch=z9hG4bK7634.4d863c14.0 User-Agent: Kamailio (1.5.3-notls (i386/linux)) From: sip:eugen.dedu@ekiga.net;tag=f85b0bd16aaafa8479586ac9f88b3198-29fc Call-ID: 8a0d723b-0f8d-e011-84d7-0024d693d8e8@snoopy To: sip:eugen.dedu@ekiga.net;tag=7c75723b-0f8d-e011-84d7-0024d693d8e8 Contact: sip:86.64.162.35:5060 Subscription-State: active;expires=270 Event: presence Content-Length: 938 Content-Type: application/pidf+xml Max-Forwards: 70
<?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns: rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="pres:eugen.dedu@ekiga.net"> <tuple id="T00000002"> <status> <basic>open</basic> </status> <contact priority="1">sip:eugen.dedu@ekiga.net</contact> <note>online - </note> <timestamp>2011-06-04T13:55:56+02:00+02:00</timestamp> </tuple>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="T00000001"> <status> <basic>open</basic> </status> <contact priority="1">sip:eugen.dedu@ekiga.net</contact> <note>away - jjk</note> <timestamp>2011-06-04T13:54:37+02:00+02:00</timestamp> </tuple> <dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" id="pid1"> rpid:activities rpid:away/ </rpid:activities> </dm:person> </presence>
The id of both tuples are different so the server must keep both. However the client sholud use if-match header on the second PUBLISH to ensure it will replace the existing one.
El 10/06/2011 21:32, "Eugen Dedu" Eugen.Dedu@pu-pm.univ-fcomte.fr escribió:
Hi again,
Then it is the time for Eugen to add it in his sip client and send
the patch for enhancing kamailio's presence server with rfc4481, as well
:o)
I start my application, and make my own status be shown. I change my status back and forth a few times between Away and DoNotDisturb (each time a publish is sent), the status returned (in notify) is good. When I change my status to Online/Available (and only to this), kamailio returns a double tuple. Is it normal to have a double tuple? If yes, which one to choose (the one with latest timestamp)? Here it is:
NOTIFY sip:eugen.dedu@82.238.108.175:**5060http://sip:eugen.dedu@82.238.108.175:5060SIP/2.0 CSeq: 7 NOTIFY Via: SIP/2.0/UDP 86.64.162.35;branch=**z9hG4bK7634.4d863c14.0 User-Agent: Kamailio (1.5.3-notls (i386/linux)) From: sip:eugen.dedu@ekiga.net;tag=**f85b0bd16aaafa8479586ac9f88b31**98-29fc Call-ID: 8a0d723b-0f8d-e011-84d7-**0024d693d8e8@snoopy To: sip:eugen.dedu@ekiga.net;tag=**7c75723b-0f8d-e011-84d7-**0024d693d8e8 Contact: sip:86.64.162.35:5060 Subscription-State: active;expires=270 Event: presence Content-Length: 938 Content-Type: application/pidf+xml Max-Forwards: 70
<?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:**pidf" xmlns:dm="urn:ietf:params:xml:**ns:pidf:data-model" xmlns: rpid="urn:ietf:params:xml:ns:**pidf:rpid" entity="pres:eugen.dedu@ekiga.** net <pres%3Aeugen.dedu@ekiga.net>"> <tuple id="T00000002"> <status> <basic>open</basic> </status> <contact priority="1">sip:eugen.dedu@**ekiga.netsip%3Aeugen.dedu@ekiga.net </contact> <note>online - </note> <timestamp>2011-06-04T13:55:**56+02:00+02:00</timestamp> </tuple>
<tuple xmlns="urn:ietf:params:xml:ns:**pidf" id="T00000001"> <status> <basic>open</basic> </status> <contact priority="1">sip:eugen.dedu@**ekiga.netsip%3Aeugen.dedu@ekiga.net </contact> <note>away - jjk</note> <timestamp>2011-06-04T13:54:**37+02:00+02:00</timestamp> </tuple> <dm:person xmlns:dm="urn:ietf:params:xml:**ns:pidf:data-model" xmlns:rpid="urn:ietf:params:**xml:ns:pidf:rpid" id="pid1"> rpid:activities rpid:away/ </rpid:activities> </dm:person> </presence>
Yes, correct. I don't think this is anything to do with Kamailio, I will detach you from the thread,
Thanks for all your assistance!
-------- Robert Jongbloed Vox Lucida Pty. Ltd.
On 12/06/2011, at 8:11 PM, Iñaki Baz Castillo wrote:
The id of both tuples are different so the server must keep both. However the client sholud use if-match header on the second PUBLISH to ensure it will replace the existing one.
El 10/06/2011 21:32, "Eugen Dedu" Eugen.Dedu@pu-pm.univ-fcomte.fr escribió:
Hi again,
Then it is the time for Eugen to add it in his sip client and send the patch for enhancing kamailio's presence server with rfc4481, as well
:o)
I start my application, and make my own status be shown. I change my status back and forth a few times between Away and DoNotDisturb (each time a publish is sent), the status returned (in notify) is good. When I change my status to Online/Available (and only to this), kamailio returns a double tuple. Is it normal to have a double tuple? If yes, which one to choose (the one with latest timestamp)? Here it is:
NOTIFY sip:eugen.dedu@82.238.108.175:5060 SIP/2.0 CSeq: 7 NOTIFY Via: SIP/2.0/UDP 86.64.162.35;branch=z9hG4bK7634.4d863c14.0 User-Agent: Kamailio (1.5.3-notls (i386/linux)) From: sip:eugen.dedu@ekiga.net;tag=f85b0bd16aaafa8479586ac9f88b3198-29fc Call-ID: 8a0d723b-0f8d-e011-84d7-0024d693d8e8@snoopy To: sip:eugen.dedu@ekiga.net;tag=7c75723b-0f8d-e011-84d7-0024d693d8e8 Contact: sip:86.64.162.35:5060 Subscription-State: active;expires=270 Event: presence Content-Length: 938 Content-Type: application/pidf+xml Max-Forwards: 70
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns: rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="pres:eugen.dedu@ekiga.net">
<tuple id="T00000002"> <status> <basic>open</basic> </status> <contact priority="1">sip:eugen.dedu@ekiga.net</contact> <note>online - </note> <timestamp>2011-06-04T13:55:56+02:00+02:00</timestamp> </tuple>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="T00000001"> <status> <basic>open</basic> </status> <contact priority="1">sip:eugen.dedu@ekiga.net</contact> <note>away - jjk</note> <timestamp>2011-06-04T13:54:37+02:00+02:00</timestamp> </tuple> <dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" id="pid1"> <rpid:activities> <rpid:away/> </rpid:activities> </dm:person> </presence>
-- Eugen
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Eugen Dedu -
Iñaki Baz Castillo -
Robert Jongbloed