A customer states they are having voice quality issues when they make calls over a WAN link. You would like to see what the Quality of Service is for a call, as the customer makes the call. Which…

Question

Options

• Amonitor station qos xxxx, where XXXX is the station number
• Blist monitor qos
• Cstatus station qos xxxx, where XXXX is the station number
• Dlist trace station xxxx, where XXXX is the station number.

• A
  2% (1)
• B
  3% (2)
• C
  5% (3)
• D
  90% (55)

Explanation

list trace station xxxx is the correct command because it provides real-time monitoring of an active station's call activity, including VoIP quality metrics such as packet loss and jitter as the call is occurring - making it the right tool for live troubleshooting of voice quality issues over a WAN link.

Why the distractors are wrong:

• A (monitor station qos xxxx) - While monitor station is a valid CM SAT command for watching station events, the qos qualifier is not valid syntax and this form does not exist in Communication Manager.
• B (list monitor qos) - This is not a recognized CM SAT command; the syntax is fabricated and will not execute.
• C (status station qos xxxx) - status station is a real command that shows a station's current state (busy, idle, registered), but it does not accept a qos argument and does not display packet loss or jitter metrics.

Memory tip: Think "trace = traffic in real time." The word trace implies you're following something live, which aligns with watching a call in progress. Commands like status give you a snapshot of current state, while list trace follows the active flow - and QoS lives in the flow.

No community discussion yet for this question.