Back to all articles
QoSVoIPTraffic ManagementLayer 3

Understanding QoS: Why Your Zoom Call is More Important Than Your Download

Alex MorganJuly 12, 2024

Imagine a busy four-lane highway during rush hour. Cars are bumper to bumper, moving at a crawl. In this traffic jam are delivery trucks carrying lumber, minivans carrying families, and an ambulance with its sirens blaring.

If this highway treated every vehicle equally, the ambulance would be stuck behind the delivery trucks, moving at 5 miles per hour. Obviously, this is unacceptable. So, society implements a rule: when an ambulance approaches with sirens on, everyone else must pull over and yield. The ambulance gets a fast, unobstructed path through the congestion.

In computer networking, this exact scenario plays out millions of times a second. And the mechanism that allows the network "ambulances" to bypass the "delivery trucks" is called Quality of Service (QoS).

All Packets Are Not Created Equal

By default, network switches and routers operate on a strictly FIFO (First In, First Out) basis. They are perfectly egalitarian. If a packet arrives, it gets put at the back of the queue. It doesn't matter if the packet contains a mundane software update or a critical piece of live audio from a CEO's conference call.

When a network connection is idle, FIFO works perfectly. Data moves so fast that queues never build up.

But when a network connection becomes congested—meaning more data is arriving than the physical cable can transmit at that exact moment—a queue forms. The router has to hold packets in its memory buffer until there is room on the wire. If the buffer gets completely full, the router starts violently dropping new packets.

For some applications, this is totally fine.

  • **File Downloads (FTP/HTTP):** If you are downloading a 50GB video game update, and the packets get delayed by 2 seconds in a router queue, you literally will not notice. TCP will just patiently wait, reassemble the file, and your download takes slightly longer.

    • For real-time applications, this is catastrophic.

  • **Voice over IP (VoIP) and Video Conferencing:** If the packets carrying your voice get delayed in a queue for even 200 milliseconds, the person on the other end will hear an annoying echo or silence. If the packets get dropped completely, your voice will sound choppy and robotic. Real-time data cannot tolerate delay (latency) or variation in delay (jitter).

    • How QoS Solves the Problem

    Quality of Service allows network administrators to look at the traffic flowing through their routers and say, "This type of traffic is critical. This type of traffic is not."

    It works in two main steps: Classification/Marking and Queuing.

    Step 1: Classification and Marking (The Sirens)

    Before a router can prioritize traffic, it has to know what it's looking at.

    Usually, the very first switch or router a packet hits (often right at the edge of the network, or even the IP phone itself) will inspect the packet. It might say, "Ah, this packet is using UDP port 5060. That means it's VoIP voice traffic."

    Having identified the packet, the device marks it. In modern networks, this is usually done using a field in the IP header (Layer 3) called DSCP (Differentiated Services Code Point). The switch writes a specific numerical code into the header.

    For example, VoIP traffic is almost universally marked with a DSCP value of 46 (which translates to 'Expedited Forwarding'). The packet now has its "sirens" on.

    Step 2: Queuing (Pulling Over)

    Now the marked packet travels across the network. It arrives at the main gateway router connecting the office to the internet—a major bottleneck that is heavily congested by employees watching YouTube and downloading files.

    Instead of a single FIFO queue, this router is configured with multiple QoS queues.

  • **Queue 1 (Priority Queue):** Strict priority for Voice traffic.
  • **Queue 2 (Business Critical):** High bandwidth allocation for database applications.
  • **Queue 3 (Default):** Normal web browsing.
  • **Queue 4 (Scavenger):** Very low priority for background backups or BitTorrent.

    • When the router sees a packet arrive, it checks the DSCP mark in the IP header.

  • A YouTube video packet arrives. It has no special mark. It goes into the Default queue and waits its turn.
  • The VoIP packet arrives, marked with DSCP 46. The router immediately places it into the Priority Queue.

    • Even if there are a thousand web packets waiting to be sent, the router will stop processing them, instantly transmit the VoIP packet, and then resume normal operations. The voice packet experiences effectively zero latency, even though the network is congested.

    The Limits of QoS

    There is one major catch to QoS: You can only control the networks you own.

    An enterprise can implement strict QoS on its own campus switches and its own WAN links. But the moment those packets are handed off to the public internet, all bets are off.

    Major ISPs generally strip off or ignore QoS markings on the public internet. Why? Because if they honored them, everyone would just maliciously mark their Netflix traffic as "Expedited Forwarding" to get faster streams, rendering the entire system useless. The public internet relies on massive, raw bandwidth (oversupply) rather than intelligent queuing to keep real-time traffic smooth.

    But within the walls of a corporate network, or across private leased lines, QoS is the unsung hero keeping the modern digital workplace functioning without driving everyone crazy.