Quality of Service: Telling Your Network What Matters

VoIP From the Ground Up: Part 9 of 10

Everything we have covered so far points to one central truth: voice traffic needs consistent, low-latency delivery, and the default behavior of a network is to treat all traffic equally. Quality of Service is how you override that default and tell your network that voice packets matter more than file downloads.

This post explains what Quality of Service is, how it works at a conceptual level, and where its real boundaries are. QoS is a useful tool in specific situations, but the VoIP industry has a habit of presenting it as a universal fix. It is not. Understanding what it actually does -- and what it cannot do -- matters more than knowing how to configure it.

The problem Quality of Service solves

By default, a router or switch handles packets on a first-come, first-served basis. Every packet, regardless of what it contains, goes into the same queue and waits its turn. When the network is quiet, this is fine. Everything gets processed quickly and there is no meaningful delay.

When the network gets busy, the queue fills up. Packets start waiting longer. If the queue overflows, packets get dropped entirely. And the network has no way of knowing that the packet it just dropped was carrying someone's voice on an active phone call while the packet it kept was part of a software update downloading in the background.

Without Quality of Service, a single large file transfer or cloud backup can degrade every active voice call on the network. Not because there is not enough total bandwidth, but because the router treats a voice packet with a 20 millisecond deadline the same as a backup packet that nobody would notice if it arrived a full second later.

How Quality of Service works

Quality of Service is not a single technology. It is a collection of mechanisms that work together to give certain types of traffic preferential treatment. The core concept has three parts: identification, marking, and queuing.

Identification

First, the network has to recognize which packets contain voice traffic. This can be done several ways. Some systems look at the source or destination address to identify traffic coming from or going to known VoIP devices. Others examine the port numbers in the packet headers, since VoIP protocols tend to use specific port ranges. In more sophisticated setups, devices are placed on dedicated network segments so that any traffic on that segment is known to be voice.

Marking

Once voice traffic is identified, it gets marked. Marking means writing a value into a field in the packet header that other network devices can read. The most common system uses a field called Differentiated Services Code Point, which is a 6-bit value in the header of every packet.

The standard value for voice traffic is 46, which corresponds to Expedited Forwarding, the highest-priority forwarding class for user traffic. (Higher values like CS6 and CS7 exist but are reserved for network control traffic such as routing protocols, not for application data.) When a VoIP phone sends a packet, it typically marks it with this value automatically. When a router or switch sees this marking, it knows to treat the packet as high-priority.

The marking system only works if every device along the path respects it. On your local network, you control this. On the internet, you do not.

Most internet service providers strip DSCP markings at their network edge or ignore them entirely. This is not a bug or a misconfiguration. ISPs have no incentive to honor markings set by their customers -- if they did, everyone would mark all their traffic as high priority and the system would be meaningless. The only exceptions are dedicated enterprise circuits with contractual SLA commitments that specifically include end-to-end QoS, and those cost significantly more than standard business internet.

This means that for the vast majority of VoIP deployments, DSCP markings are relevant only within your own network. Once a packet leaves your router, the marking is gone and the packet travels the same best-effort path as everything else on the internet.

Queuing

Queuing is where the actual prioritization happens. Instead of a single first-come, first-served queue, the router or switch maintains multiple queues, each with a different priority level.

When a high-priority voice packet arrives, it goes into a dedicated queue that gets serviced first. When a low-priority file transfer packet arrives, it goes into a different queue that only gets serviced when the high-priority queue is empty or when its minimum guaranteed bandwidth allocation is met.

The result is that during periods of congestion, voice packets experience minimal delay while lower-priority traffic absorbs the wait. The voice call stays clear while the file download slows down slightly. This is almost always the right trade-off, since the file download does not care about an extra hundred milliseconds of delay, but the voice call absolutely does.

Types of queuing

Different queuing strategies offer different trade-offs, and understanding the basics helps when evaluating equipment or reading configuration guides.

Strict priority queuing always processes the high-priority queue first. Voice packets get sent immediately, no matter what. The risk is that if something floods the high-priority queue (either by accident or misconfiguration), it can starve everything else on the network. This is usually mitigated by putting a bandwidth cap on the priority queue.

Weighted fair queuing gives each queue a proportional share of available bandwidth. The voice queue might get 30% of bandwidth guaranteed, with the ability to use more when available. This prevents starvation of other traffic but does not provide the absolute lowest latency for voice.

Low-latency queuing combines both approaches. Voice traffic gets a strict priority queue with a bandwidth cap, and all other traffic is handled by weighted fair queuing. This is the most common approach for networks that carry voice traffic because it gives voice the lowest possible latency while still preventing the priority queue from consuming all resources.

Where to apply Quality of Service

Quality of Service needs to be configured at specific points in the network to be effective. The most critical locations are:

Your router's outbound interface. This is where traffic leaves your network and enters your internet connection. Because your internet link is almost certainly slower than your internal network, this is where congestion is most likely to occur. Prioritizing voice traffic at this point ensures that voice packets are the first to be sent across your internet link during busy periods.

Managed switches. If your voice devices and data devices share the same switches, configuring the switches to prioritize voice traffic prevents internal congestion from affecting calls. This matters most in environments where internal traffic volumes are high.

Access points. If any VoIP devices are on wireless (which, as we discussed in Part 6, should be avoided when possible), enabling wireless multimedia extensions on the access point gives voice traffic priority over the air interface.

What Quality of Service cannot do

Quality of Service has important limitations that the VoIP industry tends to gloss over.

It stops at your network edge. Once your packets enter your ISP's network, your DSCP markings are stripped or ignored. The prioritization you configured applies only within your own equipment. The internet leg of a VoIP call -- which is typically where quality problems originate -- gets no benefit from your QoS configuration at all.

It cannot create bandwidth. If your internet connection is 50 megabits per second and you have 60 megabits per second of traffic trying to leave, Quality of Service determines which traffic gets priority, but it cannot make the link faster. If total demand consistently exceeds capacity, you need a bigger pipe.

It buries the canary. This is the most underappreciated problem with QoS. Congestion is a signal. When voice quality degrades during busy periods, that degradation is telling you something: your network cannot handle the load. QoS masks that signal by keeping voice clean while everything else suffers. The calls sound fine, so nobody investigates, but the underlying congestion remains. The file transfers slow down, the cloud apps lag, and eventually the congestion grows beyond what QoS can hide. By the time voice quality degrades on a QoS-enabled network, the problem is usually far worse than it would have been if you had caught it early.

It cannot fix a bad network. Quality of Service prioritizes traffic within a functioning network. It does not compensate for faulty hardware, misconfigured routing, or physical layer problems. If your switch is dropping packets due to a hardware defect, Quality of Service will not help.

It requires correct configuration. Misconfigured Quality of Service can make things worse. If the wrong traffic is marked as high priority, or if the priority queue's bandwidth cap is set too high, the system can create the very problems it was meant to solve.

The practical recommendation

For most small and medium businesses, the single most important thing for VoIP quality is a properly sized router with adequate bandwidth. Not QoS. A router that can handle your traffic volume without breaking a sweat, on a connection that has headroom above your peak usage, will deliver clean voice quality without any QoS configuration at all.

QoS has its place. Large networks with genuinely unavoidable congestion -- contact centers with hundreds of concurrent calls, campuses with thousands of devices -- benefit from traffic prioritization because the scale makes some congestion inevitable. If your network falls into that category, configure QoS.

But if you are a 20-person office and your calls sound bad in the afternoon, the answer is almost certainly not QoS. The answer is figuring out why your network is congested and fixing that. Maybe it is an undersized internet connection. Maybe it is a cloud backup running during business hours. Maybe it is a consumer-grade router that cannot keep up. QoS would hide the symptom. Fixing the root cause solves it.

If you do configure QoS, the essentials are straightforward: verify your phones are marking packets with DSCP 46 (most do by default), configure your router's outbound interface to prioritize that marking, and enable QoS on your managed switches. After configuring, run a VoIP quality test during peak hours to verify that voice traffic is actually getting the priority treatment you expect, and use the bandwidth calculator to confirm your connection has enough total capacity for your call volume. But treat QoS as insurance for traffic spikes, not as a substitute for a network that is properly sized for its workload.

What comes next

In the final post of the series, we bring everything together. You now understand how networks work, how voice travels over them, what can go wrong, and how to protect your local network. The last step is learning how to figure out where the problem actually is when things go wrong, which is exactly what VoIP Test is being built to do.

This is Part 9 of the VoIP From the Ground Up series. Part 10: How to Tell Where the Problem Actually Is is the capstone, tying everything together into a practical diagnostic framework.