08-24-2023 01:19 AM
We're slowly changing the IP addresses of all the nodes in our cluster. We're following the Cisco procedure and, at first glance it works. Databases get in sync and phones register. But phones never ring. You can dial and get a ring tone, but nothing physicall rings.
After each subscriber changes its IP address, we have to do a full cluster reboot for phones to receive calls.
Anyone seen this before?
Thanks,
Gordon
08-24-2023 01:34 AM - edited 08-24-2023 01:36 AM
It probably works after the node is restartet, because then the phones are also forced to re-register and download the config-file with the new IPs of the CUCM-nodes in it.
It's mentioned in the post-change task list at step 14, to reset the phones.
And a reboot of the node resets the phone. Without reseting the phone, how should it get the new IPs of the nodes?
So I don't see a problem here.
08-24-2023 02:00 AM
We tried phone restarts and that had no effect. (As I said, phones are all registered fine)
Only a cluster reboot allowed calling to work.
My assumption is that the real-time database (That stores registrations) is not catching up with the change of IP address - but I don't know what service that is on a Subscriber.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide