3cx Failover Issues

[shawm90]

I am having issues with the 3cx failover system. I have two servers on the same LAN behind different public IPs. Phones are provisioned by FQDN. I have the active and passive servers set up correctly, but that is about all that works. For starters, the failover will not trigger when any of the services stop (see attached). I have stopped services on the main server as well as completely powered it off in an attempt to trigger the failover. Secondly, the scripts do not work when I attempt to run them on their own for testing purposes. They do run without any errors. They do not change the A record or stop services on the primary server. I have attached the scripts that I am using.

I know it is not ideal, but I did join the failover server to the domain when initially testing the setup. I thought using the domain admin account would be needed to change the DNS record. Any help would be appreciated.

• 3CX Version, Enterprise Annual 20.0.5.551
• Server OS: Windows 11 Pro
• Is the 3CX Server Hosted and where? On Premise
• Provisioning Method: Local
• Trunk Provider or VoIP Gateway Make/Model: Bandwidth
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[shawm90]

My scripts are working now. The only thing I am having issues with now is that failover does not run the scripts. Any ideas?

 

[fortech]

Hi,

Can you clarify, right now can you do a 'failover process' with manual intervention on your setup (ie, you manually execute the scripts) and the process is ~good (ie, you do a simulated fail on primary 3cx box by unplug the NIC on this box. you run scripts on secondary 3cx host to have DNS changes happen. Then 3cx services are active and calls are flowing again normally?)

Tim

 

[shawm90]

Yes, I am able to perform the failover manually. The passive server will successfully start its services when the selected tests fail after unplugging WAN 1 on the firewall. The only thing it wont do is automatically run the selected scripts that I have selected. Manually running the scripts at this point will update the DNS record and stop the services on the active server.