<div><span style="color:rgb(48,48,48);font-family:sans-serif;font-size:13px;background-color:rgb(255,255,255)">Thank you.</span></div><div><span style="color:rgb(48,48,48);font-family:sans-serif;font-size:13px;background-color:rgb(255,255,255)"><br>
</span></div><span style="color:rgb(48,48,48);font-family:sans-serif;font-size:13px;background-color:rgb(255,255,255)">10.3 Processing REGISTER Requests:</span><div><pre style="margin-right:1em;margin-left:1.6em;padding:2px 2px 2px 0px;background-color:rgb(250,250,250);border:1px solid rgb(218,218,218);width:auto;overflow-x:auto;overflow-y:hidden;color:rgb(48,48,48);font-size:13px">
8. The registrar returns a 200 (OK) response. The response MUST
contain Contact header field values enumerating all current
bindings. Each Contact value MUST feature an "expires"
parameter indicating its expiration interval chosen by the
registrar. The response SHOULD include a Date header field.</pre><div><br></div>--<br>Nick<br><br><div class="gmail_quote">2012/10/18 Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<div><div class="h5"><br>
On Oct 18, 2012, at 11:26 AM, Nick Altmann wrote:<br>
<br>
> Hello!</div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
><br>
> Opensips 1.8<br>
><br>
> When one client registered two times in 200 OK after REGISTER I see this contact:<br>
> Contact: <<a href="http://sip:abonent1@192.168.1.63:5062" target="_blank">sip:abonent1@192.168.1.63:5062</a>>;q=0;expires=1484;received="sip:<a href="http://8.8.8.8:5060" target="_blank">8.8.8.8:5060</a>", <sip:abonent1@192.168.1.10:57393;ob>;q=0;expires=300;received="sip:<a href="http://8.8.8.8:5060" target="_blank">8.8.8.8:5060</a>"<br>
><br>
> RFC 3261, <a href="http://8.1.1.8" target="_blank">8.1.1.8</a>:<br>
><br>
> The Contact header field provides a SIP or SIPS URI that can be used<br>
> to contact that specific instance of the UA for subsequent requests.<br>
> The Contact header field MUST be present and contain exactly one SIP<br>
> or SIPS URI in any request that can result in the establishment of a<br>
> dialog. For the methods defined in this specification, that includes<br>
> only the INVITE request. For these requests, the scope of the<br>
> Contact is global. That is, the Contact header field value contains<br>
> the URI at which the UA would like to receive requests, and this URI<br>
> MUST be valid even if used in subsequent requests outside of any<br>
> dialogs.<br>
><br>
> Is it correct to receive two URIs in contact in my case?<br>
> I use path to get receiver address because I use balancer before registrar.<br>
> The command is save("location", "p0").<br>
><br>
<br>
</div></div>That is correct. Those are not 2 contact URIs, they are 2 contact headers in a single line, comma separated.<br>
<br>
<br>
Regards,<br>
<br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
</blockquote></div><br></div>