<div dir="ltr">Hello Daniel,<div>Thank you for your reply. I checked the RFC 4662 document witch contains the rls notify body. Indeed, the watcherinfo body should not be present in the multipart response. But, I think that it's an issue with the RLS or (but I can't see how I could break this) in my configuration. Let's take the case where bob adds alice in his resource list and presrules. Alice didn't made any decision yet. So, bob has alice as a friend but alice doesn't.</div>
<div>Bob makes a rls subscribe to his list. The expected behavior is to receive RLMI with state "pending" and also her display-name (from resource list). This is not working: the state is not pending. The display-name is never returned event if the subscriber has authorized him or not.</div>
<div><br></div><div><a href="http://tools.ietf.org/html/rfc4662#section-5.5">http://tools.ietf.org/html/rfc4662#section-5.5</a><br></div><div>"The "state" attribute contains the subscription state for the</div>
<div> identified instance of the resource. This attribute contains one of</div><div> the values "active", "pending", or "terminated"."</div><div><br></div><div>A rls notify example for RLMI:</div>
<div><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><list xmlns="urn:ietf:params:xml:ns:rlmi"
uri="<a href="mailto:sip%3Aadam-friends@pres.vancouver.example.com">sip:adam-friends@pres.vancouver.example.com</a>"
version="1" fullState="true">
<name xml:lang="en">Buddy List at COM</name>
<name xml:lang="de">Liste der Freunde an COM</name>
<resource uri="<a href="mailto:sip%3Abob@vancouver.example.com">sip:bob@vancouver.example.com</a>"">
<name>Bob Smith</name>
<instance id="juwigmtboe" state="active"
cid="<a href="mailto:bUZBsM@pres.vancouver.example.com">bUZBsM@pres.vancouver.example.com</a>"/>
</resource></pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px"></list></pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px">
<br></pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal">I understand that the state of the instance should have the state of the subscription. This information exists in the watcherinfo (presence.winfo): instance state is pending if I make a subscription to a subscriber that didn't authorized me yet.</span><br>
</pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal"><br></span></pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px">
<span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal">Do you understand the same?</span></pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal"><br>
</span></pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px"><span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal">Best regards,</span></pre><pre class="" style="font-size:1em;margin-top:0px;margin-bottom:0px">
<span style="color:rgb(34,34,34);font-family:arial;font-size:small;white-space:normal">Mihai M</span></pre></pre></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 15, 2014 at 6:20 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hello,<br>
<br>
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).<br>
<br>
Have you tried with two subscriptions, one for each event?<br>
<br>
Cheers,<br>
Daniel<div><div class="h5"><br>
<br>
On 15/04/14 17:15, Mihai Marin wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div class="h5">
<div dir="ltr">Hello,
<div>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.</div>
<div><br>
</div>
<div>Could you give me a hint on this one please?<br>
<br>
Thank you.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Mihai M<br>
<br>
<div class="gmail_quote">---------- Forwarded message
----------<br>
From: <b class="gmail_sendername">Mihai Marin</b> <span dir="ltr"><<a href="mailto:marinmihai@gmail.com" target="_blank">marinmihai@gmail.com</a>></span><br>
Date: Mon, Apr 14, 2014 at 10:20 PM<br>
Subject: rls multipart body does not contain watcherinfo+xml<br>
To: "Kamailio (SER) - Users Mailing List" <<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>><br>
<br>
<br>
<div dir="ltr">Hello Sirs,
<div>I'm trying to accomplish a rls subscribe but I have
some miss-understandings regarding the multipart publish
response that should come.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>The request contains the following headers:</div>
<div>Event: presence<br>
</div>
<div>Supported: eventlist<br>
</div>
<div>Accept: multipart/related, application/pidf+xml,
application/rlmi+xml, application/watcherinfo+xml<br>
</div>
<div><br>
</div>
<div>The response only sends the first two:<br>
</div>
<div>
<pre>--4kSPpRGyJQct4DIhyGnyobqO
Content-Transfer-Encoding: binary
Content-ID: <a href="mailto:1397508890.sip:bob@93.187.138.214.681064155" target="_blank"><1397508890.sip:bob@93.187.138.214.681064155></a>
Content-Type: application/rlmi+xml;charset="UTF-8"
<?xml version="1.0"?>
<list uri="<a href="mailto:sip%3Abob@93.187.138.214" target="_blank">sip:bob@93.187.138.214</a>" xmlns="urn:ietf:params:xml:ns:rlmi" version="4" fullState="false"><resource uri="<a href="mailto:sip%3Aalice@93.187.138.214" target="_blank">sip:alice@93.187.138.214</a>"><instance id="Scf8UhwQ" state="active" cid=<a href="mailto:1397508890.sip:alice@93.187.138.214.1552580371" target="_blank">"1397508890.sip:alice@93.187.138.214.1552580371"</a>/></resource></list>
--4kSPpRGyJQct4DIhyGnyobqO
Content-Transfer-Encoding: binary
Content-ID: <a href="mailto:1397508890.sip:alice@93.187.138.214.1552580371" target="_blank"><1397508890.sip:alice@93.187.138.214.1552580371></a>
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="<a href="mailto:sip%3Aalice@93.187.138.214" target="_blank">sip:alice@93.187.138.214</a>">
<dm:person id="p6850">
<rpid:activities/>
<rpid:status-icon><a href="http://93.187.138.214:5060/xcap-root/oma_status-icon/users/sip:alice@93.187.138.214/sip_communicator" target="_blank">http://93.187.138.214:5060/xcap-root/oma_status-icon/users/sip:alice@93.187.138.214/sip_communicator</a></rpid:status-icon>
</dm:person>
<tuple id="t7673">
<status>
<basic>open</basic>
</status>
<contact><a href="mailto:sip%3Aalice@93.187.138.214" target="_blank">sip:alice@93.187.138.214</a></contact>
<note>Online</note>
</tuple>
</presence>
--4kSPpRGyJQct4DIhyGnyobqO--</pre>
<pre></pre>
<pre>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.</pre>
<pre>Thank you in advance for you help.</pre>
<pre>Best regards,</pre>
<pre>Mihai M</pre>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<br>
<pre cols="72">--
Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</font></span></div>
<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div>