31 Jul
2013
31 Jul
'13
3:37 p.m.
Hello,
On 7/31/13 2:27 PM, Vitaliy Aleksandrov wrote:
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:
listen=tcp:x.y.z.w:8080
listen=tls:x.y.z.w:8443
You can use restrictions like:
if(dst_port==8080 && !nat_uac_test("64")) {
send_reply("403", "Only WS allowed on port 8080");
exit;
}
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hello,
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).
Cheers,
Daniel
Hello,
That's it !
I've connected the phone using udp as transport and kamailio added two
record route headers.