Enterprise Failover

[Fred2k]

Having just read this article, I had a few questions about the Enterprise level 3CX Fail-over.

There's a pre-requisite that extension's "Select Interface" settings are set to the FQDN. I'm assuming the theory is that this then updates settings on the IP phone? I ask because I'm currently using pretty old IP phones (Aastra 51i) which I haven't been able to provision via the PBX - I have to manually set the registration server IP on each phone.

Am I right in thinking that I would need to set the registration server on each phone to a FQDN? That makes sense, but I don't have a DNS Server on our VoIP network, everything is currently configured locally using IP addresses... does this pretty much stop me being able to utilise this feature?

 

[Evolute IT]

Having just read this article, I had a few questions about the Enterprise level 3CX Fail-over.

There's a pre-requisite that extension's "Select Interface" settings are set to the FQDN. I'm assuming the theory is that this then updates settings on the IP phone? I ask because I'm currently using pretty old IP phones (Aastra 51i) which I haven't been able to provision via the PBX - I have to manually set the registration server IP on each phone.

Am I right in thinking that I would need to set the registration server on each phone to a FQDN? That makes sense, but I don't have a DNS Server on our VoIP network, everything is currently configured locally using IP addresses... does this pretty much stop me being able to utilise this feature?

Simply use newer supported phones and you won't have issues. Legacy and EOL phones do not support SBC or STUN correctly, they only work locally (or via VPN).

It would help knowing where both the instances are hosted.

 

[Fred2k]

At present I only have 1 physical server, but I do have a spare machine which I was planning to use as a secondary / fail-over. So it would be 2 physical instances in the same office.

Also, at present my 3CX server is sitting behind a firewall which has the public IP assigned, and NATs the traffic on to the PBX. Obviously this setup wouldn't work if I have both servers sitting behind the same firewall/public IP.

 

[cobaltit]

Am I right in thinking that I would need to set the registration server on each phone to a FQDN? That makes sense, but I don't have a DNS Server on our VoIP network, everything is currently configured locally using IP addresses... does this pretty much stop me being able to utilise this feature?

Keeping in mind that you want to utilize ENTERPRISE level failover, yes you will need a DNS server. And frankly, setting up a DNS server is pretty easy compared to some other bits you'll need to get 3CX failover to work smoothly. Honestly, you'd be better off virtualizing 3CX and using your preferred clustering solution as it's more tried and true.