Call Tracing: What components did the call reach?

From DocWiki

Revision as of 17:43, 9 June 2009 by Cchetty (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Call Tracing: What components did the call reach?

Problem Summary You can track the call through the system by searching for a Cisco-GUID. The Cisco-GUID is the common denominator used in logging for every call across each component. Find the relationships in the Unified CVP logs.
Error Message The error message for this problem...
Possible Cause The Cisco-GUCID has the format:
DEAD91DD1000011A74D013BE0A5687DD

There are two exceptions to the common Cisco-GUCID:

  • When Unified CM is the caller source, use the LegID. The LegID format is:
    120111222148396083
  • If the call never makes it to Unified Expert Advisor from Unified CVP 4.x, then search for the GUID. The GUID format is:
    05A2AEC3-10000115-550959F1-0A568782
Recommended Action To determine which components the call reached, search for the Cisco-GUID/GUCID in the following logs:
  • Unified Expert Advisor MMCA logs
  • Unified ICM VRU PIM "VRU Capture" logs
  • Unified Expert Advisor PG PIM and OPC logs
  • All Unified CM and Unified Presence logs
  • Unified CVP logs
  • Ingress gateway logs (if your calls are arriving via TDM)
  • VXML gateway logs
Note Note: For IOS logs, turn on debug ccsip all.
Release Release 7.6(1)
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools