<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body text="#000000" bgcolor="#ffffff">
    <br>
    Hi,<br>
    <br>
    Thanks. I've already been sniffing the network. The capture file of
    the presence server (kamailio) and the ua (watcher) is attached.<br>
    <br>
    Backend subscriptions must be sent to what CSCF of the presentity
    domain? The S-CSCF? You wrote me that Kamailio uses dns queries in
    order to determine the ip of the next IMS entity. In case of a
    subscription to <a class="moz-txt-link-abbreviated" href="mailto:list@open-ims.test">list@open-ims.test</a>, what dns query will Kamalio do?<br>
    <br>
    The subscription message is:<br>
    <br>
    <font face="Courier New, Courier, monospace">SUBSCRIBE
      <a class="moz-txt-link-freetext" href="sip:restricted_areas_presentities@open-ims.test">sip:restricted_areas_presentities@open-ims.test</a> SIP/2.0<br>
      Call-ID: nYhLl92BHRHtSTy3f8iNZ1v6irOhhfd2fNnFtSXTOlk.<br>
      CSeq: 1 SUBSCRIBE<br>
      From: "restricted_areas"
      <a class="moz-txt-link-rfc2396E" href="sip:restricted_areas@open-ims.test">&lt;sip:restricted_areas@open-ims.test&gt;</a>;tag=f733f739<br>
      To: <a class="moz-txt-link-rfc2396E" href="sip:restricted_areas_presentities@open-ims.test">&lt;sip:restricted_areas_presentities@open-ims.test&gt;</a><br>
      Via: SIP/2.0/TCP
155.54.190.245:8060;rport;branch=z9hG4bK-d8754z-a71d1c184df2d432-1---d8754z-<br>
      Max-Forwards: 70<br>
      Event: presence<br>
      Accept: multipart/related, application/rlmi+xml,
      application/pidf+xml, application/auth-policy+xml<br>
      Expires: 30000<br>
      Contact: <a class="moz-txt-link-rfc2396E" href="sip:restricted_areas@155.54.190.245:8060">&lt;sip:restricted_areas@155.54.190.245:8060&gt;</a><br>
      Supported: eventlist<br>
      Route: <a class="moz-txt-link-rfc2396E" href="sip:orig@scscf.open-ims.test:6060;lr">&lt;sip:orig@scscf.open-ims.test:6060;lr&gt;</a><br>
      Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
      SUBSCRIBE, INFO<br>
      User-Agent: X-Lite IMS-OSGi-Client 0.1
      CVS-Mon_Jan_03_09-56-46_CET_2011<br>
      Content-Length: 0</font><br>
    <br>
    <br>
    And the XCAP document:<br>
    <font face="Courier New, Courier, monospace">&lt;?xml version="1.0"
      encoding="UTF-8"?&gt;&lt;rls-services
      xmlns:rl="urn:ietf:params:xml:ns:resource-lists"
      xmlns="urn:ietf:params:xml:ns:rls-services"&gt;&lt;service
      uri=<a class="moz-txt-link-rfc2396E" href="sip:restricted_areas_presentities@open-ims.test">"sip:restricted_areas_presentities@open-ims.test"</a>&gt;&lt;resource-list&gt;&lt;list

      name="friends"&gt;&lt;rl:entry
      uri=<a class="moz-txt-link-rfc2396E" href="sip:testuser01@open-ims.test">"sip:testuser01@open-ims.test"</a>/&gt;&lt;rl:entry
uri=<a class="moz-txt-link-rfc2396E" href="sip:testuser02@open-ims.test">"sip:testuser02@open-ims.test"</a>/&gt;&lt;/list&gt;&lt;/resource-list&gt;&lt;packages&gt;&lt;package&gt;presence&lt;/package&gt;&lt;/packages&gt;&lt;/service&gt;&lt;/rls-services&gt;</font><br>
    <br>
    The URI for the document is: <br>
    <font face="Courier New, Courier, monospace">/xcap-root/rls-services/users/<a class="moz-txt-link-freetext" href="sip:restricted_areas@open-ims.test/index">sip:restricted_areas@open-ims.test/index</a></font><br>
    <br>
    <br>
    Could anyone send me a capture file with the whole process of the
    subscription to the rls and the notifies sent along with the
    configuration files of Kamailio (if needed) and the xcap documents?<br>
    <br>
    <br>
    Thank you all,<br>
    &nbsp; Andr&eacute;s.<br>
    <br>
    <br>
    El 04/01/11 15:08, Klaus Darilion escribi&oacute;:
    <blockquote cite="mid:4D2329ED.2020409@pernau.at" type="cite">
      <br>
      <br>
      Am 04.01.2011 13:06, schrieb "Andr&eacute;s S. Garc&iacute;a Ruiz":
      <br>
      <blockquote type="cite">
        <br>
        Hello,
        <br>
        <br>
        Thanks for your responses and happy new year!
        <br>
        <br>
        Could anyone tell me how to make the RLS module work properly?
        <br>
        <br>
        I've tried several different solutions, but I still don't know
        what's
        <br>
        the expected behaviour of the RLS.
        <br>
        <br>
        I'm using the Kamailio integrated presence server + RLS. Then,
        the RLS
        <br>
        is supposed to send a SUBSCRIBE to each of the presentities in
        the
        <br>
        subscribed presence list?
        <br>
      </blockquote>
      <br>
      Correct. So-called "backend subscriptions"
      <br>
      <br>
      <blockquote type="cite">In that case, and if the domain of the
        presentity is the same as the
        <br>
        used by the watcher, the SUBSCRIBE will go back to the Kamailio?
        <br>
      </blockquote>
      <br>
      yes.
      <br>
      <br>
      <blockquote type="cite">This is the reason why I don't receive the
        notify. There are no dialogs
        <br>
        for the subscription:
        <br>
        <br>
        5(13925) DEBUG: presence [notify.c:1302]: found 0 dialogs( 0 in
        database
        <br>
        and 0 in hash_table)
        <br>
        5(13925) DEBUG: presence [notify.c:1387]: Could not get
        subscription dialog
        <br>
        5(13925) DEBUG: presence [notify.c:1461]: dialog info:
        <br>
        5(13925) DEBUG: presence [notify.c:122]:
        <br>
        [pres_uri]= <a class="moz-txt-link-freetext" href="sip:restricted_areas_presentities@open-ims.test">sip:restricted_areas_presentities@open-ims.test</a>
        <br>
        [to_user]= restricted_areas_presentities [to_domain]=
        open-ims.test
        <br>
        [w_user]= restricted_areas [w_domain]= open-ims.test
        <br>
        [event]= presence
        <br>
        [status]= active
        <br>
        [expires]= 0
        <br>
        [callid]= nYhLl92BHRHtSTy3f8iNZ1v6irOhhfd2fNnFtSXTOlk.
        [local_cseq]=1
        <br>
        [to_tag]= a6a1c5f60faecf035a1ae5b6e96e979a-5cc7 [from_tag]=
        f733f739
        <br>
        [contact]= <a class="moz-txt-link-freetext" href="sip:restricted_areas@155.54.190.245:8060">sip:restricted_areas@155.54.190.245:8060</a>
        [record_route]=
        <br>
<a class="moz-txt-link-rfc2396E" href="sip:mo@scscf.open-ims.test:6060;lr">&lt;sip:mo@scscf.open-ims.test:6060;lr&gt;</a>,<a class="moz-txt-link-rfc2396E" href="sip:mo@pcscf.open-ims.test:4060;lr">&lt;sip:mo@pcscf.open-ims.test:4060;lr&gt;</a>
        <br>
        5(13925) DEBUG: presence [hash.c:471]: pres_uri=
        <br>
        <a class="moz-txt-link-freetext" href="sip:restricted_areas_presentities@open-ims.test">sip:restricted_areas_presentities@open-ims.test</a>
        <br>
        5(13925) DEBUG: presence [notify.c:643]: No record exists in
        hash_table
        <br>
        5(13925) DEBUG: presence [notify.c:1515]: Could not get the
        notify_body
        <br>
        5(13925) DEBUG: presence [notify.c:225]: state = terminated
        <br>
        5(13925) DEBUG: presence [notify.c:1555]: headers:
        <br>
        Max-Forwards: 70
        <br>
        Event: presence
        <br>
        Contact: <a class="moz-txt-link-rfc2396E" href="sip:155.54.190.245:5060;transport=udp">&lt;sip:155.54.190.245:5060;transport=udp&gt;</a>
        <br>
        Subscription-State: terminated;reason=timeout
        <br>
        <br>
        Any hints?
        <br>
      </blockquote>
      <br>
      That shouldn'T be the problem. You should see the backend
      subscription by sniffing on the loopback interface, e.g. to sniff
      an all interfaces (and in nice format) use:
      <br>
      <br>
      ngrep -d any -W byline -t -P "" port 5060
      <br>
      <br>
      regards
      <br>
      Klaus
      <br>
    </blockquote>
    <br>
  </body>
</html>