I am having this issue when using kamailio-4.1.2 (after patching the segfault bug). The kamailio is configurated as a frontend for asterisk. When using UDP for SIP, this works correctly. However, I am now setting up websockets (no TLS yet), and I am getting a disconnect after an interval. I am getting this on the logs:
Apr 11 16:19:41 elx3 /usr/sbin/kamailio[4814]: WARNING: websocket [ws_frame.c:868]: ws_keepalive(): forcibly closing connection
Tweaking with keepalive_mechanism=1 and keepalive_timeout does not change the situation, and does not even modify the interval before the disconnection. Is this keepalive something that should be visible on a SIP trace? I am only seeing REGISTER and its response from the jsSIP trace. I do not want to have to disable keepalives just to work around this issue.
Hello,
On 12/04/14 01:16, Alex Villacís Lasso wrote:
I am having this issue when using kamailio-4.1.2 (after patching the segfault bug). The kamailio is configurated as a frontend for asterisk. When using UDP for SIP, this works correctly. However, I am now setting up websockets (no TLS yet), and I am getting a disconnect after an interval. I am getting this on the logs:
Apr 11 16:19:41 elx3 /usr/sbin/kamailio[4814]: WARNING: websocket [ws_frame.c:868]: ws_keepalive(): forcibly closing connection
Tweaking with keepalive_mechanism=1 and keepalive_timeout does not change the situation, and does not even modify the interval before the disconnection. Is this keepalive something that should be visible on a SIP trace? I am only seeing REGISTER and its response from the jsSIP trace. I do not want to have to disable keepalives just to work around this issue.
I guess these keepalive packets should be at TCP layer, perhaps you can see them with wireshark.
Are there more relevant log messages when you set debug=3 in kamailio.cfg?
Cheers, Daniel
-
Alex Villacís Lasso -
Daniel-Constantin Mierla