Hello, just to understand it correctly: You are restarting the Kamailio on the active node, and it does not close the existing Websocket TCP connections? Or you are restarting the Kamailio on the second passive node? Cheers, Henning From: sr-dev &lt;sr-dev-bounces(a)lists.kamailio.org&gt; On Behalf Of Shahid Hussain Sent: Thursday, June 17, 2021 1:54 PM To: sr-dev(a)lists.kamailio.org Subject: [sr-dev] Kamailio websocket state FINWAIT1 after switchover Hi !., Kamailio websocket state is going into FINWAIT1 without sending FIN message out when we do service kamailio restart. I have a Primary and Secondary node configured. When I perform switchover socket status is going into FINWAIT1 state without sending FIN to the client hence client status is showing established, This is happening 90+% of times but does work sometimes. AT Kamailio: [root@localhost ~]# netstat -tunelap | grep 41034 tcp 0 1 172.27.45.198:9040<http://172.27.45.198:9040> 172.27.6.98<http://172.27.6.98>:41034 FIN_WAIT1 0 0 - [root@localhost ~]# AT Nginx (client): root@meet:~# netstat -tunelap | grep 9040 tcp 0 0 172.27.6.98<http://172.27.6.98>:41034 172.27.45.198:9040<http://172.27.45.198:9040> ESTABLISHED 33 763106 1322/nginx: worker root@meet:~# Thanks, Shahid