I ended up finding the issue seemed to be with the fact IPv6 had been shut off. Mod_event_socket was configured still to the default of "::" which should have bound to both IPv4 and IPv6 according to confluence. It seems that "::" was only binding to IPv6 based off some testing. I failed over to the standby server which still had IPv6 enabled, and once freeswitch was up I checked with netstat to see what ports were bound. I only ended up seeing 8021 for event_socket bound on IPv6 TCP: tcp6 0 0 :::8021 :::* LISTEN 12030/freeswitch Logs only showed the following line when I grepped for that port/event_socket: 2016-12-14 09:18:35.136806 [DEBUG] mod_event_socket.c:2943 Socket up listening on :::8021 While on the server which had IPv6 shut off, netstat showed nothing bound to that port, nor did the logs. Since it seems to be potentially a bug I will open up a report on JIRA. Just wanted to post the solution I found in case anyone else was having a similar trouble. -Zach -------- Original Message -------- Subject: Floating IPs and fs_cli Date: 2016-12-14 16:31 From: Zach Rothy <zrothy@monmouth.com> To: freeswitch-users@lists.freeswitch.org Good Evening, I recently set up a floating IP on freeswitch as I have 2 servers that will be running as active and standby in case one goes down. I have the sip profiles for internal and external ipv4 as well as verto communicator's conf file set to bind to this floating IP. I also added the required thing to sysctl as listed on the high availability page so that it won't have problems binding to that IP if it wasn't there for some reason. After I set this all up I noticed I could no longer connect to the CLI with fs_cli. Is there some special arguments that have to be passed or used to access the CLI when using a floating IP address? Some notes of my set up: Though I mention high availability, I only referenced it for any settings that may be needed for freeswitch to bind properly to a floating IP and do not actually plan on doing anything else besides this floating IP. Right before I set this up my coworker had shut IPv6 off on the server as it was not needed. I noticed this as the IPv6 profiles couldn't bind anymore, and I had temporarily removed the sip profiles to remove errors in case that was a problem. Thanks in advance, Zach R