see my previous response in this thread.
On May 30, 2018, at 12:46 PM, Miguel Jesús López Valverde <mjlopez@smartic.es> wrote:
Hello Geoff and Freeswitch-users:
Currently I have a Freeswitch server in development mode on Amazon EC2 instance and another, working in production, as a physical machine. Both are mounted on Linux Debian 8 - 64 bits and the Freeswitch version is 1.6.18 64bit in development and 1.6.19 64bit in production.
Also I’ve another Freeswitch servers in development and production, but this servers only work with TCP/UDP, no WSS and they haven’t this trouble.
These systems keep Sip and WSS-SipJs clients connected through their internal context. In both cases, they are connected to Proxies where they register and take calls with other external carriers.
All user accounts, connection information with proxies, etc. they are maintained through externals Mysql databases, (different for each system).
Everything works correctly but, on occasion, any of the Freeswitch systems working with WSS stops working without, apparently, offering information about the reason. This occurs every 2-3 weeks and it can happen to one of the two servers, the state that keep in this case the following: