- Joined
- May 18, 2023
- Messages
- 19
- Reaction score
- 4
Hello,
I have two 3CX servers one in the 3CX cloud (active) and the other in LightSail (passive). Both on Enterprise licenses.
I have it setup to monitor the SIP connection only and when I disable the service on the primary I see the passive becomes the primary. Issue is that the extension I have provisioned to the app on the primary on my cell phone shows green when clicking the hamburger menu but on the main app screen just sits at connecting.. and never connects even if I wait 10+ minutes.
However If I call the number the app rings and I can click answer and it looks as if i am on the call, but the desk phone (completely different PBX) continues to ring.
I don't see that scripts ARE required and step 8 fomr the belwo link reads:
"Press OK to save the configuration and start monitoring. When the active server (#1) fails, the passive detects this and takes over. With the backup already restored, the failover action triggers the 3CX DNS Servers to update the FQDN to the IP address of the new active server (#2). It is important that the previously active server (#1) is shutdown to avoid conflict with the server that just took "
https://www.3cx.com/docs/failover/
If I manually shut down all the services that it allows me to in the 3CX hosted server, and even restart ALL services on the passive server after it when it springs into action, the DNS still never resolves on the app never changes to "Ready for calls".
If scripts are required (which is not made clear) then how would I setup the failover with the SSH instructions in the ReadMe.txt provided with the Linux scrips it links to download in step 7 if I don't have SSH creds for the 3CX hosted server? From the sounds of that. 3CX handles that access?
I have two 3CX servers one in the 3CX cloud (active) and the other in LightSail (passive). Both on Enterprise licenses.
I have it setup to monitor the SIP connection only and when I disable the service on the primary I see the passive becomes the primary. Issue is that the extension I have provisioned to the app on the primary on my cell phone shows green when clicking the hamburger menu but on the main app screen just sits at connecting.. and never connects even if I wait 10+ minutes.
However If I call the number the app rings and I can click answer and it looks as if i am on the call, but the desk phone (completely different PBX) continues to ring.
I don't see that scripts ARE required and step 8 fomr the belwo link reads:
"Press OK to save the configuration and start monitoring. When the active server (#1) fails, the passive detects this and takes over. With the backup already restored, the failover action triggers the 3CX DNS Servers to update the FQDN to the IP address of the new active server (#2). It is important that the previously active server (#1) is shutdown to avoid conflict with the server that just took "
https://www.3cx.com/docs/failover/
If I manually shut down all the services that it allows me to in the 3CX hosted server, and even restart ALL services on the passive server after it when it springs into action, the DNS still never resolves on the app never changes to "Ready for calls".
If scripts are required (which is not made clear) then how would I setup the failover with the SSH instructions in the ReadMe.txt provided with the Linux scrips it links to download in step 7 if I don't have SSH creds for the 3CX hosted server? From the sounds of that. 3CX handles that access?