Voice to a cloud contact center is dropped. Bulk data on the same edge still flows. Every tunnel misses the voice loss target, the voice policy is strict, and firewall counters are zero. What is dropping the voice?
Select an answer to reveal the explanation.
Short Explanation
Bulk data is getting through, so the pipes are not gone. You told voice to drop when no tunnel is good enough, and every tunnel is missing the loss target, so that strict SLA is the drop. A firewall that left the counter at zero is not the one throwing the calls away.
Full Explanation
A strict application-aware routing action drops the matched application when no tunnel meets the SLA class. Every tunnel misses the voice loss target, so voice is dropped while bulk data, which does not match that strict policy, still follows an available path. Firewall counters at zero mean the zone-based policy is not the drop. A withdrawn OMP route for the contact center would also stop a route-following bulk flow to that same destination if they shared it. Bulk data still flowing shows the edge has working paths. An expired SIG credential would affect traffic steered at the SIG, not only the flows that carry a voice SLA. Exam caveat: if the clinic would rather have degraded voice than silence, remove strict or name a backup color. Strict is correct only when a bad call is worse than no call. Operational check: the voice SLA action should show strict, and voice should forward again when one tunnel returns inside the loss target or when strict is cleared.