tcp_accept_no_cl=yes should always be used when Kamailio is receiving HTTP
traffic (the event_route[xhttp:request] is used) as HTTP/1.1 does not use
the Content-Length: header if there is no message body (as in the case of
the WebSocket handshake). Even when there is a body Content-Length: is
not
Hello Peter,
Thank you for the quick reply. Yes, that did the trick. Changing
"tcp_accept_no_cl" to value of no was the resolution.
It seems that the JsSIP Tryit sample code, which I was trying to hack,
doesn't use Content-Length in the header. I wonder if this should be
changed to set the Con
Hello,
Check that you have "tcp_accept_no_cl=yes" in your configuration.
This is required for Kamailio to parse messages over TCP which do not have
"Content-Length:" headers (including HTTP requests).
If that doesn't work try running Kamailio with debug output at its highest
level (you'll need t
Hi,
Wondering if anyone could please help me debug what is wrong with my
kamailio.cfg for Websockets support. I'm using JsSIP sample application,
and I've compiled Kamailio 4.0 for WS support. My config is borrowed from
link this link [1]. Wondering if anyone can help me debug this. Error is
b
