<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>6 dec 2012 kl. 15:59 skrev Peter Dunkley <<a href="mailto:peter.dunkley@crocodile-rcs.com">peter.dunkley@crocodile-rcs.com</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; CHARSET=UTF-8">
<meta name="GENERATOR" content="GtkHTML/4.4.4">
<div text="#000000" bgcolor="#ffffff">
On Thu, 2012-12-06 at 13:20 +0100, Daniel-Constantin Mierla wrote:<br>
<blockquote type="CITE">
Address in firth path will be used to set $du anyhow, not sure what the flow token implies, but might be just done from config.<br>
<br>
</blockquote>
<br>
The flow token is the user part of the Path-URI and is an encrypted string that indicates the source IP address, port, and protocol of the REGISTER request. So for NAT traversal purposes you want to send to the place the flow token indicates, not what is actually in the host part of the Path-URI (but only if the Path-URI has an ;ob parameter). The idea is that even on a single server system with clients that do not support outbound it should be possible to "force outbound" so as to get this into the location table.<br></div></blockquote>The flow token points to a flow saying that Kamailio should NOT parse the Contact URI and find a destination. It should find the proper connection.</div><div><br><blockquote type="cite"><div text="#000000" bgcolor="#ffffff">
<br>
Basically, when using outbound like this, the aliasing stuff in nathelper and the received AVP/parameter/column in registrar and usrloc are obsoleted.<br>
<br>
The useful parts remaining in nathelper will be nat_uac_test() and nat pinging. Although, for outbound capable clients nat pinging on the server is not needed as the clients will send STUN requests to the SIP server anyway. This means the when outbound support is complete, STUN should be enabled by default on the Kamailio builds.<br></div></blockquote>Yep.</div><div><br></div><div>Have sent e-mail to sip-implementors on the Q issue. It seems to me that Juha is right, it must be a mistake. </div><div><br></div><div>/O<br><blockquote type="cite"><div text="#000000" bgcolor="#ffffff">
<br>
Regards,<br>
<br>
Peter<br>
<table cellspacing="0" cellpadding="0" width="100%">
<tbody><tr>
<td>
<pre>--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
</pre>
</td>
</tr>
</tbody></table>
</div>
_______________________________________________<br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev<br></blockquote></div><br></body></html>