<div class="gmail_quote">2012/7/30 Peter Dunkley <span dir="ltr"><<a href="mailto:peter.dunkley@crocodile-rcs.com" target="_blank">peter.dunkley@crocodile-rcs.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
With these changes (and a client that supports it) should I now be able to use WebSockets without the aliasing from nathelper?</blockquote></div><br>Hi, there should be no difference with the case of SIP over TCP or TLS. The main benefict of using Outobund and GRUU in clients (with reliable transport such as TCP/TLS/WS) is that when the UA is in an active dialog and its connection is closed, it can re-register (using a GRUU Contact), replace the previous binding in the registrar, and when an incoming request from the dialog peer arrives to the registrar it chooses the last created binding for that GRUU Contact, so the request arrives to the UA even through its new connection.<div>
<br></div><div>BTW I *hate* Contact mangling and Contact aliasing, that's an ugly mechanism. Outbound solves that perfectly.</div><div><br></div><div>Regards.<br clear="all"><div><br></div>-- <br>Iñaki Baz Castillo<br>
<<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
</div>