Hi Evandro - Tough to say without show run or any information. Please make sure that IP CEF and IP routing is enabled in show run. Check as well for any tracebacks. During high CPU, please collect debug ccsip messages or debug ccsip all. We have to be careful when enabling the debugs so we do not cause the router to hung.
Please log the debugs in the router buffer. Disable logging monitor and logging console. Make sure that the router buffer size is set to 10000000. That should be able to tell you what kind of SIP messages migt be causing such high CPU
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...