3CX mobile App failing over to secondary system only

[Mark Jones]

I've been seeing our mobile app failing over to the secondary server can anyone help me to figure out why this is happining, when i can hit the FQDN and it goes to the primary system. doesn't make any sense.

 

[ChrisC_3CX]

Just so that we first get a better understanding of the situation, since you mention a secondary server, I assume you are running a failover configuration. If yes, how was this set up, are you using the same License Key? Are we talking about a 3CX Failover configuration?

Also, what do you mean when you say that the mobile app fails over to the secondary system, does it actually register somewhere else? If yes, do bear in mind that a 3CX passive/secondary server must have certain services stopped, such as the SIP server. If no, how have you determined that it fails over?

 

[Mark Jones]

yes its a failover server with the same license key pro license, the second server is setup for passive both using the same FQDN, we received a call saying that the mobile app wasn't allowing users to make calls. so I hopped into the system from outside of our network and logged in and I saw the primary ip which lets me know that the system not failed over, however when i ping the fqdn it replies the secondary server IP. we are using 3cx FQDN. the reason users can make any calls is because the system is not fully failed over but doesn't make any sense why I'm able to hit the primary server using the FQDN and when i ping it I'm getting the secondary ip.

 

[NickD_3CX]

Could you send me your FQDN in a PM so I can try and check what happened? I'm assuming you're using a 3CX FQDN...

 

[Mark Jones]

just sent it.

 

[Mark Jones]

let me say this also when i was on vacation a few weeks ago the same thing happen as well so this is not the first time this has happen and we are seeing this more and more.

 

[Mark Jones]

have you found out anything yet?

 

[NickD_3CX]

Hi!

I checked the FQDN history and it seems that there are changes of the FQDN from both active and passive servers in the past weeks. The weird thing is that that requests of the active and passive servers to update the IP Address of the FQDN are usually close together.

Could it be that someone is restarting the server or 3CX Services? Or maybe you have some kind of cronjob or monitoring software the automatically installs Debian updates causing services to restart?

I will send you the last date/time I saw this change on both servers to maybe check the Linux syslog and/or 3CX Logs if you have them that maybe gives a clue why it's happening.

 

[Mark Jones]

ok thanks!