Is there some secret to getting syslog started on CallManager? I have tried to configure CallManager to send errors to a syslog server (not a Ciscoworks server, just a generic syslog). I used the Alarm Configuration menu and provided the syslog server IP address, enabled it, etc. but nothing shows up on the syslog despite the fact that I have errors in Windows event viewer. Other systems are able to log to this syslog. I noticed a few bugs (apparently unresolved) in CCO on older versions of CallManager re: syslog, but I'm not sure if these apply.
For CallManager 3.2, if the syslog is configured as a remote server, then this may not always work. There are some issues with the disk I/O of the CallManager in case of version 3.2 due to which , sending traces or syslog messages to remote server via a slow network or during periods of congestion will not always work. Cisco does not recommend this. You can use a local syslog server, which will solve the issue. It works for 3.3. For more information refer to:
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...