Fwd: websocket devices keepalive not working - sr-users

1 Jul 2015

As I read at README to Nathelper it may not work with usrloc table, Is it
write?

now I use NAT traversal module and Websocket module to keepalive
mechanisms, that uses UDP or WS.

with UDP it is wery simple method - OPTIONS replies.

With WebSocket module keepalive mechanism uses thomething else. Not a SIP
methods, I see at TCPDUMP packets that marks with modparam("websocket",
"ping_application_data", "WebSockets rock")

I need to handle replies of keepaliwe mechanism. How I may handle replies
form this mechanism?

2015-06-30 18:37 GMT+03:00 Yuriy Gorlichenko &lt;ovoshlook(a)gmail.com&gt;om>:

...
  thnks for response. I thing - nathelper is what I
need. If I resolve issue
 above (why it not work with setbflag(7)  ) I thing this questions will be
 closed.

 P.S may be it help - my kamailio version is

 version: kamailio 4.4.0-dev1 (x86_64/linux) 1dbd53
 flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
 DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
 F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
 USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
 ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
 id: 1dbd53
 compiled on 06:24:22 Jun 23 2015 with gcc 4.8.4

 2015-06-30 18:18 GMT+03:00 Camille Oudot &lt;camille.oudot(a)orange.com&gt;om>:

  Le Tue, 30 Jun 2015 15:49:26 +0300,
 Yuriy Gorlichenko &lt;ovoshlook(a)gmail.com&gt; a écrit :

  4) I tried to do it with tcpops

 Only for ws and tcp (WS is use TCP as i know)
 tcp_keepalive_enable("15", "5", "15");

 same result... 
 Hi Yuriy,

 the tcp_keepalive_enable() function will send keepalive packets at TCP
 level, not at application level (SIP OPTIONS). It can be used to check
 if the remote peer connection is still valid, and close the TCP
 connection on the server side if it is no more valid. If you enable the
 TCP keepalives, you should see these packets using tcpdump or wireshark.

 Along with "handle_lost_tcp" option on usrloc, this can be used to
 maintain the usrloc table as consistent as possible.

 --
 Camille