Enterprise Failover, SIP configured with different IPs at DR site

[hood]

Hi Team,

I'm currently working through how I can setup a failover PBX for a client to ensure maximum availability. They do have Enterprise licensing.

Currently their SIP service is delivered on-NET, being a dedicated port on the NTU that is not accessible over the public internet. The SIP carrier now has an option to Dual Home the SIP service via an Over the top trunk. This can be delivered to any public IP address. The SIP carrier can then handle where the SIP is directed, primary site (on-NET) or secondary site (OTT).

The issue is looking at the failover documentation I need to have IDENTICAL PBX settings (including SIP), which I wouldn't be able to do in this instance because my SIP settings at the DR site (OTT trunks) would be different to the private IP SIP registration used for the on-NET SIP trunk.

Has anyone else faced a similar situation or got a solution?

Thanks.

 

[ChrisC_3CX]

I need to have IDENTICAL PBX settings (including SIP),

This is true due to the fact that you will need to keep the secondary 3CX Server up to date by constantly restoring a backup taken from your primary 3CX Server. However, if from the time of setup the PBX will not be going any configuration changes, you might want to consider not using the backup/restore function at all and manually change the SIP Trunk settings on the secondary PBX. This of course would mean that the secondary PBX will not be updated configuration wise, nor will contain any call logs, recordings, voicemails, or anything else from the primary server other than the initial configuration it was setup with. It will however allow telephony services to stay operational until you manage to restore the Primary PBX server.

The SIP carrier now has an option to Dual Home the SIP service via an Over the top trunk. This can be delivered to any public IP address.

Since this is possible, why not use it on both Primary and Secondary servers to rid yourself of this conundrum?