Upgrade of publisher succeeded. However when the subscriber was added we immediately lost 80% of the phone registrations. There is only one Callmanager group with the subscriber first, then publisher. If I stopped the CM service on the sub, all phones register normally to the publisher. Issue appeared to be a DB replication error, but resyncing (utils dbreplication reset) didn't work, nor did rebuilding the subscriber entirely. Any ideas?
After you add a new subscriber to the cluster, the replication agreements and the actual replication are initiated only after the first reboot of each subscriber. So make sure you reboot the subscribers after you add them to the cluster. If you add many subscribers, reboot them one at a time in order to avoid overloading the publisher with the database replication.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...