This usually means your WebSocket client is not closing its connections properly. As such
a WebSocket connection eventually fails to respond to a ping from the server and you get
this error. It is similar to the TCP errors you get when the far end of those connections
fails.
There was a problem with this error recurring continuously that was fixed some weeks ago -
so make sure you are using the latest 4.0.0 build from git master. However, even with
that fix in place you will still see this error if your WebSocket client behaves
incorrectly (and won't see it all - even without the fix - if the client behaves
correctly).
Regards,
Peter
On 19 Jan 2013, at 18:07, Ramaseshi reddy kolli <ramaseshireddy(a)gmail.com> wrote:
Hi,
I am using kamailio dev version and find some issue with websocket and it is happening
once in a day.
Jan 2 10:26:56 kamailio-registrar
/usr/local/kamailio/sbin/kamailio[1175]: ERROR: websocket
[ws_conn.c:321]: getting TCP/TLS connection
Jan 2 10:26:56 kamailio-registrar
/usr/local/kamailio/sbin/kamailio[1175]: WARNING: websocket
[ws_frame.c:785]: forcibly closing connection
logs are spammed with that until we restart, looks like an infinite
loop somewhere in the websocket code .
I checked with tcpdump and didnt see any traffic on TCP port 5065 or
5060 coming .
Could you please help me with this?
Thanks
Ram
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev