In a Cisco Unified Contact Center Enterprise deployment, which three traces would you apply for a Cisco Unified Communications Manager PIM in the Cisco Unified ICM PROCMON tool? (Choose three.)

Question

Options

• Atrace "low" /on
• Btrace calls* /on
• Ctrace "event"/on
• Dtrace closedcalls /on
• Etrace precall /on
• Ftrace routing /on

• A
  14% (8)
• B
  74% (42)
• D
  9% (5)
• F
  4% (2)

Explanation

When troubleshooting a CUCM PIM in the Cisco ICM PROCMON tool, trace calls /on* (B) captures all call-state activity using a wildcard to catch every call-related message, trace "event" /on (C) captures the event messages passed between the PIM and the ICM router to show the signaling flow, and trace precall /on (E) captures pre-call routing data showing how calls are handled before they are answered - together, these three give a complete picture of call lifecycle through the PIM.

Options A (trace "low" /on) and the concept of severity levels like "low" do not apply to PROCMON trace syntax - PROCMON uses functional category names, not severity tiers. Option D (trace closedcalls /on) is not a valid PROCMON trace keyword for CUCM PIM. Option F (trace routing /on) sounds plausible but is not one of the standard PIM-specific trace categories used in PROCMON for CUCM.

Memory tip: Think CPE - Calls, Precall, Event - the three traces that walk a call from arrival (precall) through signaling (event) to full call activity (calls*).

No community discussion yet for this question.