10-30-2016 09:57 PM - edited 03-17-2019 08:31 AM
Hi,
I have a client who is using Cisco Unified Communications Manager version 6 with Publisher and Subscriber. All the phones are registered to the subscriber. Suddenly one day all the phones were unregistered and is showing "Registering". Both publisher and subscriber servers were accessible too. I restarted the subscriber server, then the phones registered to the publisher and when the subscriber came back up, the phones got registered to the subscriber server and is working fine till now without any problem. Any idea what is the problem?. I want to prevent this from happening again.
Thanks,
Ajin.
Solved! Go to Solution.
10-30-2016 11:56 PM
Hi Ajin,
There could be many possible reasons for the issue encountered.
It seems from the description though the best possible cause was that the phones were unable to maintain the connection with the Subscriber server and CCM service seems to have caused the issue.
Once , you rebooted the subscriber server, the phones fallback to the Publisher server as a redundancy mechanism based on the CCM group settings.
And once the Subscriber was back up and running, the phones went back and registered to the subscriber server as it was the primary server.
Since, you have recovered from the state, the only possible root cause can be to have a look at the CCM traces by TAC but considering your client is running CCM v6, TAC might not support as it is EOS.
Also, have a look for any possible cores on the Subscriber server using the following command "utils core active list" on the CLI during that time.
Regards,
Hitesh
10-30-2016 11:56 PM
Hi Ajin,
There could be many possible reasons for the issue encountered.
It seems from the description though the best possible cause was that the phones were unable to maintain the connection with the Subscriber server and CCM service seems to have caused the issue.
Once , you rebooted the subscriber server, the phones fallback to the Publisher server as a redundancy mechanism based on the CCM group settings.
And once the Subscriber was back up and running, the phones went back and registered to the subscriber server as it was the primary server.
Since, you have recovered from the state, the only possible root cause can be to have a look at the CCM traces by TAC but considering your client is running CCM v6, TAC might not support as it is EOS.
Also, have a look for any possible cores on the Subscriber server using the following command "utils core active list" on the CLI during that time.
Regards,
Hitesh
10-31-2016 12:22 AM
Thank you Hitesh. Yeah there is no support from Cisco as it is EOS but the customer is asking what caused the issue. Thanks for your support.
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