3cx fail over issues

[Mark Jones]

HI i have 2 Linux servers v18 setup to failover, with 2 gateways for a PRI and a Voice T1 that we tested last night and had a few issues.
1. system could not dial out after failover, but could get inbound calls.
2. the two sip trunks (gateways) never green up but i could receive inbound calls.
3. the mobile app did not connect
4. the passive sever did not pass the firewall checker as the primary did.

 

[SweetAction]

Likely your firewall port forwarding needs to be updated to use the internal IP of the failover server (instead of the primary server).

 

[Charles_3CX]

How are the gateways configured to communicate with the 3cx machines? Are the gateways local top both the instances? as we don't recommend the use of gateways in failover scenarios as these need to be provisioned to each of the individual 3cx instances.

https://www.3cx.com/docs/failover/
Note: Gateways (FXS/FXO) in a failover scenario are only supported when local to your PBX system, i.e. reachable via LAN. Even in cases where there is a site-to-site VPN between NATed Servers, we cannot support Gateway Registration and failover to the Failover server as it depends on manufacturer/model/gateway capabilities.

 

[Mark Jones]

How are the gateways configured to communicate with the 3cx machines? Are the gateways local top both the instances? as we don't recommend the use of gateways in failover scenarios as these need to be provisioned to each of the individual 3cx instances.

https://www.3cx.com/docs/failover/
Note: Gateways (FXS/FXO) in a failover scenario are only supported when local to your PBX system, i.e. reachable via LAN. Even in cases where there is a site-to-site VPN between NATed Servers, we cannot support Gateway Registration and failover to the Failover server as it depends on manufacturer/model/gateway capabilities.

They are local the gateways are config to follow the active server in case of a failover.

 

[Charles_3CX]

Ok, let's first touch on the firewall subject. As @SweetAction has mentioned, you need to forward the ports to the passive server from your firewall, the same as you have for the active, of course, it will be best to have a separate public IP address to have these ports mapped beforehand.

Going back to the getaways then, which gateways are these? Are they on our supported list? And if so, how do the gateways configured to follow the active server in case of failover? as gateways need to be provisioned for each 3cx system? Are you doing some sort of manual configuration?

 

[Mark Jones]

Ok, let's first touch on the firewall subject. As @SweetAction has mentioned, you need to forward the ports to the passive server from your firewall, the same as you have for the active, of course, it will be best to have a separate public IP address to have these ports mapped beforehand.

Going back to the getaways then, which gateways are these? Are they on our supported list? And if so, how do the gateways configured to follow the active server in case of failover? as gateways need to be provisioned for each 3cx system? Are you doing some sort of manual configuration?

The passive sever has its own public IP I will check the port mapping! The Gateways are Patton SN4970/1E15V in the config they are set up to follow the active server so this just answer my question! the startup config has the passive server IP address so the gatways must be restarted to function properly.