Refer to the exhibit. An engineer configured an agent-to-agent RTP test with the DSCP option set to EF between the office and the HQ to monitor voice quality. Users report intermittent voice quality…

Question

Options

• AAdd more DSP resources for call flow.
• BChange to a voice codec suitable for high-latency networks.
• CShift the VoIP traffic to an alternate server.
• DAdd QoS marking of voice traffic with EF.

• A
  7% (3)
• B
  14% (6)
• C
  5% (2)
• D
  74% (32)

Explanation

Marking voice traffic with DSCP EF (Expedited Forwarding) on the actual production VoIP flows is the correct fix because the IP SLA synthetic test already uses EF marking - meaning the test probes receive priority queuing and report acceptable quality, while the real user voice packets may be unmarked and subject to best-effort treatment, causing the intermittent issues users experience. Option A is wrong because DSP resources handle transcoding and conferencing capacity, not packet prioritization on the WAN. Option B is wrong because the problem isn't inherent high latency - it's that real traffic is being dropped or delayed due to missing QoS markings, not a codec mismatch. Option C is wrong because shifting to an alternate server doesn't address why traffic lacks the EF marking that would grant it priority treatment on the path.

Memory tip: Think of the IP SLA test as a "VIP pass" clone - the test gets in the priority lane (EF marked), but real user traffic is stuck in the general admission line unless you give it the same VIP pass. When test results look fine but users complain, suspect that the test and the traffic are being treated differently.

No community discussion yet for this question.