SIP Redundancy and 3CX Failover Query

[lmartin82]

Hi all,
We're thinking of moving away from our current Cisco VoIP solution and onto something like 3CX, I have a couple of 'newbie' questions that I hope someone could clear up.

1. Will 3CX support having a failover server set up at a secondary location to our main HQ. (Where our primary server would be) Our HQ and this secondary location are connected via private BT dedicated fibre circuits and would use different server IP subnets for each 3CX installation.(I know that we'd need the Enterprise licensing from 3CX to set up a failover) Each location already has the routing in place to send/receive data to/from our 60+ remote sites, so all of the desk phones could connect to either location. I'm assuming this is related to how the 3CX FQDN entry would work on our private DNS servers.
2. I'm trying to think of the best way to implement a back up solution should our HQ server room ever totally go down. If I had one SIP trunk coming into HQ and one from the same provider at the secondary location (Each one also handling around 200 different DDIs) could each SIP trunk correctly connect to the HQ Primary 3CX server for call handling but then also automatically connect to the failover one for all outgoing external calls should it go down? (This is more to do with how SIP trunks can be configured on something like Cisco CUBE)
3. Lastly, if I could have a SIP trunk at each location can 3CX intelligently route outgoing calls to each of them (round robin?) so that the Simultaneous Call channels are each gradually taken up. (Probably 50 channels will be allocated to each trunk)
   
   Any help with these queries, or pointers on good redundancy measures are super appreciated.
   Thanks a lot

 

[leejor]

For point 1, your assumption is correct, if a secondary server takes over, it will have to update the FQDN so sets continue to register with the working server.

https://www.3cx.com/docs/failover/

For point 2...it is all going to depend on how your provider is able to handle to routing of calls to each server, and what happens if one fails. Are they then able to re-direct all calls to the working server only.

For point 3... 3CX outbound rules will normally use all available channels on the first choice trunk. When all are busy, it will then route over the second choice. Some re-distribution can be done with the routing of different areacodes/prefixes/types of calls/extensions using different rules with the outbound trunk routes setup in a different order.

I'm sure that others will have some more suggestions.