I have one subscriber (three-node CallManager 3.2(2c) spH cluster) that does not appear to be creating CDRs. I have noticed that the temporary file normally created in the directory c:\program files\cisco\calldetail is not getting created every minute (actually it is not getting created at all) as it does on the other subscriber. In addition, I get an error in the Windows event log that a kDbconnectionfailed due to the system not being able to transfer data from that directory to the publisher.
I have turned up DBL tracing, etc. but have not been able to identify a specific issue. One item of note is that there is a difference in the registry entries at the localmachine\software\ciscosystems, inc. level. On the working subscriber the entry for "glassserver" is set to the publisher, but on the failing subscriber this is set to itself. I have tried changing this value and restarting DBL, but it did not seem to make a difference.
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...