There is a possibility that the CCM service controls this trap and thus cannot send a trap until it is up. This is an issue seen in many devices not just CCM. CCM supports only certain traps.Refer the following URL for more information
We're in the same boat. A customer of ours has CCM 4.0.2 and 4.1.3...they're unable to send CCM-specific SNMP traps to our application. They configured Windows 2000 to send traps to the SNMP Manager server's IP address and they defined a READ-WRITE community as descrived in the CCM SNMP setup doc. Is there any other things left to do? Any editting need to be done on the CISCO-CCM-MIB file? Thanks.
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...