Your call quality problem is not a voice problem

The call-quality complaint arrives pointed at the phone system. It is almost never the phone system.

A voice platform is the most sensitive traffic on a network and the least tolerant of a problem anywhere along the path. Data traffic absorbs jitter, retransmits a lost packet and nobody notices. A conversation does not get that luxury: twenty milliseconds of variation is audible, and a hundred milliseconds of one-way delay changes how people take turns speaking.

So when the complaint comes in, the phone system is the wrong place to start looking.

Where it usually is

The trust boundary that was never applied

A handset marks its own traffic. If the access switch does not trust that marking, or worse trusts it from every port including the ones with laptops on them, the marking is meaningless by the second hop. Queuing further along then does exactly what it was told to do with traffic that is now best effort.

Queuing configured on the wrong links

QoS applied at the WAN edge, correctly, and nowhere else. Then a site is added with an uplink that was never part of the original policy, and every call across it competes with a backup job.

A path that changed

Routing converged onto a backup link during an incident months ago and never converged back, because nothing was watching. The voice path is now two hops longer and crosses a link that was never sized for it.

Duplex and errors

Unglamorous, and still present in real networks. A mismatched port produces errors that barely register in throughput terms and destroy a call.

How to look

1. Establish the actual path. Not the documented one. Trace it, hop by hop, in the direction the complaint describes.
2. Check marking at each hop, not just at the ends. Find the place where the marking stops surviving.
3. Look at interface counters along that path — errors, drops and queue depth, not utilisation averages that hide microbursts.
4. Get the call detail. Jitter, loss and MOS from the platform tell you which direction and which leg, which halves the search immediately.
5. Only then look at the voice configuration.

The underlying point

Voice deployments fail when the network and the voice platform are treated as two separate projects with two separate owners. The dial plan can be perfect and the call still unusable. If you are commissioning a UC platform, insist that whoever designs it is allowed to look at the switches.