Voice still uses a path with high delay. The SLA class for voice watches loss only, and loss on that path is inside the class. Delay is the problem users report. What should the class include?
Select an answer to reveal the explanation.
Short Explanation
You’re seeing the difference between packet loss and the delay users feel. Add latency to the voice class so a high-delay path no longer qualifies; checking loss again still tells you nothing about delay. A zone-based deny or shorter BFD hello won’t make the class evaluate latency either.
Full Explanation
An SLA class marks a tunnel ineligible only for the measures it includes. Your voice class watches loss, and loss on the path is inside the class, so a high-delay path still qualifies and voice stays on it. Add latency to the class so a path with excessive delay no longer qualifies for voice. A second copy of the loss check still measures loss, not delay. A zone-based deny drops sessions by policy; it does not become a latency SLA. A shorter BFD hello detects failure faster, but it does not change the delay the class ignores. Exam caveat: once latency is included, decide whether strict should drop voice or a backup color should take it. Adding the measure without an action still leaves voice on the best remaining path, which may be the slow one if it is all you have. Practical check: confirm the voice class lists latency and that voice leaves the high-delay path when another path is inside the class.