<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
for requests within dialog the r-uri has to be the contact from the
200ok that created the dialog. This is the general rule, I don't
remember any spec amending that for subscriptions.<br>
<br>
As long as there is a to-tag, the requests has to end up to the
entity that generated its value, that being specified by a contact
header in initial request or its reply.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 05/12/13 15:44, Richard Good wrote:<br>
</div>
<blockquote
cite="mid:CAOvD116Jbyi4WZiNHbxMegyk47kZ=oVXMDefTFjtqD9aKYwkgg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi<br>
<br>
</div>
I am re-using the pua_reginfo module to implement P-CSCF
subscription to Registration-State information at the
S-CSCF.<br>
<br>
</div>
For the first SUBSCRIBE everything works fine and as per
RFC 3680 the SUBSCRIBE has the presentity URI as
request-URI, e.g.<br>
<pre class="">SUBSCRIBE <a moz-do-not-send="true" href="mailto:sip%3Abob@biloxi.example.com">sip:bob@biloxi.example.com</a> SIP/2.0
</pre>
</div>
The S-CSCF returns 200 OK with contact-header e.g.:<br>
<pre class="">Contact: sip:<a moz-do-not-send="true" href="http://server19.example.com">server19.example.com</a></pre>
</div>
<div>From RFC 3261:<br>
<pre>12.1.2 UAC Behavior
...........
The remote target MUST be set to the URI
from the Contact header field of the response.</pre>
</div>
<div>So any subsequent SUBSCRIBE has its remote target (and
hence request-URI) changed to the contact returned in the
200 OK. <br>
<br>
So any subsequent SUBSCRIBE requests have request-URI:<br>
<pre class="">SUBSCRIBE <b>sip:<a moz-do-not-send="true" href="http://scscf.example.com:6060">scscf.example.com:6060</a></b> SIP/2.0</pre>
</div>
<div>Currently our S-CSCF implementation uses the request-URI
to look up the presentity URI so any subsequent SUBSCRIBE
requests fail.<br>
</div>
<div><br>
</div>
<div>From RFC 3265:<br>
<pre>3.1.4.2. Refreshing of Subscriptions
.....
The handling for such a request is the same as for
the initial creation of a subscription except as described below.
</pre>
<br>
</div>
<div>Does anyone know what subsequent SUBSCRIBE requests
should have in their request-URI? The contact returned in
the first 200 OK (the S-CSCF contact) as per RFC 3261 or the
same as the initial SUBSCRIBE as per RFC 3265 with the
presentity URI in the request-URI?<br>
<br>
Regards<br>
Richard.<br>
</div>
<div><br>
</div>
</div>
</div>
<pre>This email is subject to the disclaimer of Smile Communications at <a class="moz-txt-link-freetext" href="http://www.smilecoms.com/disclaimer">http://www.smilecoms.com/disclaimer</a>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre wrap="">_______________________________________________
sr-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a>
</pre>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
</body>
</html>