Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
After the user attempts to upgrade a subscriber to CallManager 3.3, IP phones receive a reorder tone
In the middle of a critical subscriber upgrade, the upgrade fails. The publisher has been upgraded and currently the cluster is operating in a stand alone configuration.
These are several of the symptoms:
IP phones receive a reorder tone after being reset.
The subscriber thinks it is primary and has phones registered to it.
The publisher thinks it is primary and has phones registered to it.
Most phones think the subscriber is primary and the publisher is standby.
These symptoms come from the fact that the publisher needs to be rebooted. During the upgrade it is important to reboot all the machines in the cluster so they can be synchronized, start with fresh caches and have a common point of reference.
Also, the subscriber did not have a robust name resolution method, as the hosts and LMHOSTS were not converged and in conflict. It is important that both of these files are synchronized with each other. Although Network Basic Input/Output System (NetBIOS) procedures are falling out of favor, they have not reached the point where they can be dispensed. Important processes mostly related to database replication rely on the services of NetBIOS.
Note: The Microsoft Structured Query Language (SQL) server uses NetBIOS name resolution for some types of Remote Procedure Call (RPC) tasks. Because of this, the publisher and all subscribers should use the LMHOSTS file for NetBIOS name resolution. All servers in the cluster should also use hosts files for proper name resolution between the servers.
To resolve this issue, edit a text file and reboot.
For more information about the SQL server, NetBIOS and their role in the upgrade and everyday operation of Cisco CallManger, refer to these documents: