Well just to update, there is not an easy way to fix this table replication problem, and TAC does not support any manual table configuring, I was able to fix the replication error by removing the references, but in the end, I had to completly remove the subscriber from the ccmadmin page, and rebuild the subscriber. This could be a long process if your publisher has been upgraded may times due to the ccm install process for a subscriber has to be build from CDs. After you build the subscriber form the CDs, you then have to proceed the upgrade path to get to the same level of the publisher. If you dont have CDs which are on the same main level of the publisher, this becomes challenging (ie: pub on 3.2, CDs are 3.0)
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...