<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
<div class="moz-cite-prefix">On 7/31/13 2:27 PM, Vitaliy Aleksandrov
wrote:<br>
</div>
<blockquote cite="mid:51F9029A.2000806@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix"><br>
</div>
<blockquote cite="mid:51F8F7F8.3080009@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hello,<br>
<br>
does it add two record route headers when calling to an UDP
destination? IIRC, the condition for double route is that
incoming socket is different than outgoing socket and I am not
sure if Peter updated it to detect a different sub-protocol type
(as ws/wss are on top of tcp/tls).<br>
<br>
Cheers,<br>
Daniel<br>
</blockquote>
Hello,<br>
<br>
That's it !<br>
I've connected the phone using udp as transport and kamailio added
two record route headers.<br>
</blockquote>
ok, so that condition with sockets for record routing has to be
revised for this case. What you can do for the moment (and what most
of us probably did that they didn't discover this issue) is to use a
different port just for websocket connections, for example 8080 for
ws and 8443 for wss:<br>
<br>
listen=tcp:x.y.z.w:8080<br>
listen=tls:x.y.z.w:8443<br>
<br>
You can use restrictions like:<br>
<br>
if(dst_port==8080 && !nat_uac_test("64")) {<br>
send_reply("403", "Only WS allowed on port 8080");<br>
exit;<br>
}<br>
<br>
Cheers,<br>
Daniel<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>