LAN to CLOUD failover possible?

[cms-itdept]

Hello Everyone,

New user here, trying to see if this scenario is possible, I'm testing an on-prem 3cx instance running on the 3cx Debian ISO v16.0.9. I want to know if I can setup failover to a cloud instance and have some kind of active-passive approach in case my main site is completely down (power outage, fiber cut, etc)? I currently have a custom DNS with GoDaddy with a low TTL, and I'm wondering if this would be the best approach or going directly to cloud would be advisable in this scenario?

 

[HRMNY]

You say main site, does that mean you have multiple locations? The enterprise license allows for failover and standby license. https://www.3cx.com/docs/failover/

 

[VasilisV_3CX]

Hi @cms-itdept,

Using a custom FQDN as you are, it is possible but you'd need to add a script to trigger the DNS update if your primary PBX fails. As per the guide above:

"For Failover use with custom FQDN and LAN-to-LAN or LAN-to-Cloud scenarios, to update your DNS and FQDNs when failover occurs, you need to use advanced scripting and services like Active Directory to run shell scripts with administrative privileges."

 

[charles]

In addition to the reply above, also note that this will only be possible when you do not have locally provisioned IP phones. When you have locally provisioned IP phones, on the same premise as the PBX, they can not be automatically switched to be remote, to connect to the cloud instance, and will need to be factory reset and reprovisioned as such.

 

[cms-itdept]

Hi @cms-itdept,

Using a custom FQDN as you are, it is possible but you'd need to add a script to trigger the DNS update if your primary PBX fails. As per the guide above:

"For Failover use with custom FQDN and LAN-to-LAN or LAN-to-Cloud scenarios, to update your DNS and FQDNs when failover occurs, you need to use advanced scripting and services like Active Directory to run shell scripts with administrative privileges."

Yeah I figured, I think the best way would be to start in the Cloud, I will run this by management as it would be simpler and cleaner

In addition to the reply above, also note that this will only be possible when you do not have locally provisioned IP phones. When you have locally provisioned IP phones, on the same premise as the PBX, they can not be automatically switched to be remote, to connect to the cloud instance, and will need to be factory reset and reprovisioned as such.

This brings out another question, what if I go to cloud directly and let's say my power is out in that location where I have phones, I'm guessing the agents can grab a cell phone or directly from their PC and start taking calls, can you have an IP Phone and the web interface/cell phone app work in some sort of redundant mode? like if the IP Phone is out, automatically route calls to cell phone app or web interface?

 

[SteveITS]

can you have an IP Phone and the web interface/cell phone app work in some sort of redundant mode? like if the IP Phone is out, automatically route calls to cell phone app or web interface

The cell phone app is the extension so if a call is received it will ring. In Settings/Accounts one can "uncheck" the extension to disconnect (so it doesn't ring), or check it again to reconnect. Or log in/out of the web client. So no need to route calls. The web client has a dropdown in the upper right to pick the preferred phone/device.