University users complain about voice quality, while a network test of the same path shows it idle and free of loss. Which test matches the complaint?
Select an answer to reveal the explanation.
Short Explanation
An empty highway does not tell you why the phone call in the car sounds bad. You run a voice test, because the complaint is call quality and the path test is already idle. Another loss check, a name lookup, or a page waterfall measures something the users did not report.
Full Explanation
Users are complaining about voice quality, and a network test of the same path is already idle and free of loss. A voice test measures the call quality they reported, which a quiet data path does not stand in for. Running another network test for loss and latency on a path that just showed neither problem repeats a measurement that did not match the complaint. A DNS test of call-control names checks resolution, and the report did not say that names were failing. A web test loads a page and records a waterfall, which describes a web application rather than the voice quality on the calls. Call quality can still be poor while a data-path test looks idle, because the users are hearing the voice media, not the idle loss counters on that path. Exam caveat: an idle network test does not clear a voice complaint; it tells you the next test should be the one aimed at the calls. Operational check: place the voice test on the same calling path during a reported bad call and compare that result with the idle network test from the same interval.