Solved Deskphones don't register upon failover from production system

Status
Not open for further replies.

dashbrook

Premier Customer
Basic Certified
Joined
Feb 2, 2021
Messages
16
Reaction score
0
Our internal deskphones are not registering with the failover server after the failover process happens. The phones are set to register with the public DNS name of the 3CX system. The public DNS name has been put into our internal DNS structure and it resolves to the correct internal IP address. During the failover process, the public version of the internal IP address of the active system is changed to the IP address of the failover server.

The failover server comes up normally and becomes the active server. Everything seems to be fine except for the deskphones. I rebooted one deskphone as a test and the result was the same. It would not register with the failover server.

Once I switched back to the production server from the failover copy and switched the IP address in the DNS system, the deskphones registered again automatically.

Ideas?
 
Hi @dashbrook

How long would you say you left the phones after the failover event and DNS entry was updated?
 
5 minutes. The internal IP address was updated on one of many primary DNS servers within our network. Do you think I should try updating the internal address on all of our DNS servers thinking it is a DNS replication issue?
 
Yes, it might be a matter of DNS. The phones will also take some time to notice that the DNS entires have changed based on the TTL, assuming the DNS server query response they got contained the new IP.

The 5 mins may have not been enough in this case, or perhaps they were getting a query response that still contined the old IP.

I think its worth looking a bit further into it, especially if you can monitor their DNS requests to see what reply they got back during the event
 
It appears the issue was with the multiple DNS servers. After adjusting the IP addresses on all of them manually instead of waiting for DNS replication to occur, the phones registered as expected. I don't know exactly how long it took for them to register since I had other business to attend to during the failover process but they did register. The TTL may have been a factor but I did not adjust that portion of DNS.
 
glad to hear it was resolved!
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet