User:Sreenara

From DocWiki

Revision as of 05:15, 15 February 2013 by Sreenara (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

CUCM Trace Lookup Scenarios

We have a Multi-Services Voice Debug Lookup Tool for different troubleshooting scenarios located here: http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a0080207ec6.shtml


This document indicates the different combination of traces that are required by TAC in different scenarios so that customers can provide complete information to the CSE at the beginning of the case itself. This saves time and allows us to solve the cases faster as majority (if not all) of the right information is given to us, and we do not need to ask for it again.


I have specified a few scenarios below that are commonly faced by the customer. This can be used as a reference.


  1. CALL ROUTING ISSUES

         a. Detailed Cisco Call Manager Traces

             Please make sure that the SIP Call Processing Traces and SIP Stack traces are also checked in case you have any SIP devices/trunks involved in the call flow. SIP Stack traces should be enabled when the call volume is not very high as it takes up more CPU cycles, leaving less available for call processing.

             SoftKey traces are also important and can be turned on.

             We don't need to change the level of SDL traces, unless explicitly asked for.

             Scrshotj.jpg

         b. Event Viewer - Application and Event Viewer - System logs.

         c. Timestamps of call failures, Calling and Called numbers.

         d. Detailed Call Flow (Devices involved in the call flow & Protocols).



    2. HIGH CPU/MEMORY UTILIZATION

         a. Detailed Cisco Call Manager traces.

         b. Event Viewer - Application and Event Viewer - System logs.

         c. Cisco RISDC and Perfmon logs.

         d. Cisco AMC service

         e.

Personal tools