When a CM 3.2(2c) is joined to a domain (is currently a workgroup member) and reloaded, the DC Directory service will not start, however the CM continues to function ok. The only resolution at this time is to revert to a backup disk.
sorry, I was a bit vague. When the CM is joined to the domain, it says it has to be rebooted. The the CM has restarted, the DC directory reports an error in the event log stating that the directory was shutdown abnormally without journalling enabled, and that it should be restored from a backup.
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...