Hello,
iirc, there has to be a subscription for each event. Not sure it was
amended by new RFC documents. Perhaps the best is to check with RFC 4662
and/or RFC 4826 (they are indicated by RLS module README).
Have you tried with two subscriptions, one for each event?
Cheers,
Daniel
On 15/04/14 17:15, Mihai Marin wrote:
Hello,
Does anyone has a clue on this one bellow? I'm stuck on this part
because I don't know if the rls publish should include the watcherinfo
part in the body or I should subscribe twice with 2 different events:
event presence and event precence.winfo.
Could you give me a hint on this one please?
Thank you.
Best regards,
Mihai M
---------- Forwarded message ----------
From: *Mihai Marin* <marinmi...@gmail.com <mailto:marinmi...@gmail.com>>
Date: Mon, Apr 14, 2014 at 10:20 PM
Subject: rls multipart body does not contain watcherinfo+xml
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>>
Hello Sirs,
I'm trying to accomplish a rls subscribe but I have some
miss-understandings regarding the multipart publish response that
should come.
I'm using the integrated xcap from the kamailio with all the xml files
added. My problem is that event if I request a multipart
containing application/pidf+xml, application/rlmi+xml,
application/watcherinfo+xml I only get the first two.
The request contains the following headers:
Event: presence
Supported: eventlist
Accept: multipart/related, application/pidf+xml, application/rlmi+xml,
application/watcherinfo+xml
The response only sends the first two:
--4kSPpRGyJQct4DIhyGnyobqO
Content-Transfer-Encoding: binary
Content-ID: <1397508890.sip:bob@93.187.138.214.681064155>
Content-Type: application/rlmi+xml;charset="UTF-8"
<?xml version="1.0"?>
<list uri="sip:bob@93.187.138.214 <mailto:sip%3Abob@93.187.138.214>" xmlns="urn:ietf:params:xml:ns:rlmi" version="4" fullState="false"><resource
uri="sip:alice@93.187.138.214 <mailto:sip%3Aalice@93.187.138.214>"><instance id="Scf8UhwQ" state="active"
cid="1397508890.sip:alice@93.187.138.214.1552580371"/></resource></list>
--4kSPpRGyJQct4DIhyGnyobqO
Content-Transfer-Encoding: binary
Content-ID: <1397508890.sip:alice@93.187.138.214.1552580371>
Content-Type: application/pidf+xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<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="sip:alice@93.187.138.214
<mailto:sip%3Aalice@93.187.138.214>">
<dm:person id="p6850">
<rpid:activities/>
<rpid:status-icon>http://93.187.138.214:5060/xcap-root/oma_status-icon/users/sip:alice@93.187.138.214/sip_communicator</rpid:status-icon>
</dm:person>
<tuple id="t7673">
<status>
<basic>open</basic>
</status>
<contact>sip:alice@93.187.138.214
<mailto:sip%3Aalice@93.187.138.214></contact>
<note>Online</note>
</tuple>
</presence>
--4kSPpRGyJQct4DIhyGnyobqO--
What do I missing? I need the body part with the watchers info in oder to see
the state of the watcher (active, pending) - to accomplish the authorization
for users.
Thank you in advance for you help.
Best regards,
Mihai M
_______________________________________________
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
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
_______________________________________________
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
