Thanks for following up and explaining what was happening and how was
solved -- it helps to mark the report closed as well as gives guidelines
to other facing the same situation.
Cheers,
Daniel
On 11/11/15 12:27, Vasiliy Ganchev wrote:
the solution is found, the root of the issue was in
our proxy daemon, that
received sip from outside world, and proxy it to kamailio (kamailio received
sip via localhost)
My ws users, have such received in location:
Received:: sip:127.0.0.1:36986;transport=ws
I added in NOTIFY construction (with some conditions, but the focus is
here):
$uac_req(ouri) = "sip:127.0.0.1:" + $sp + ";transport=ws";
and this helped (kamailio send to proxy daemon via localhost, which when
receive on exact port, nows where to send it outside)
issue is no more relevant
cheers
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/issue-with-uac-req-send-to-websocke…
Sent from the Users mailing list archive at
Nabble.com.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio -
http://www.asipto.com
Kamailio Advanced Training, Nov 30-Dec 2, Berlin -
http://asipto.com/kat