QoS for VoIP: How to Prioritize Voice on Your Network
Calls that sound fine most of the day but break up when someone uploads a large file or a backup starts are the classic sign that your network needs QoS. Quality of service (QoS) tells your switches, access points and router which packets to send first when a link is full. This guide explains where QoS helps, which markings to use, how to configure queues and shaping, and how to check it works.
What QoS does, and what it can't do
Every network device has queues. When packets arrive faster than a link can send them, they wait, and voice suffers most: a speech packet that arrives late is as useless as one that never arrives. QoS sorts traffic into classes and sends the voice class ahead of downloads, backups and video streams.
- It only matters when a link is congested. On an idle link, every packet goes straight through anyway.
- It doesn't add bandwidth. If your calls alone need more than the link carries, QoS can't help. Check the numbers in our guide to VoIP bandwidth requirements.
- It only works on links you control. Once packets leave your router for the public internet, providers generally ignore or reset your markings. The exception is a managed service, such as MPLS or a provider's business VPN, where QoS is part of the contract.
That last point decides where to spend your effort: on your side of the internet link, and above all on the upload direction.
Where congestion happens
| Point | Why it congests | QoS tool |
|---|---|---|
| Internet upload | Cloud backups, file sync and video uploads fill it; usually much smaller than the download | Shaping plus a priority queue on your router |
| Internet download | Large downloads and streaming | Inbound shaping, which makes senders slow down |
| Wi-Fi | Shared airtime, weak signal, many clients | WMM priority, good coverage |
| Switch uplinks | Several busy ports feeding one uplink | Switch QoS trusting voice markings |
| Site-to-site VPN | Tunnel rides over the internet; inner markings may be hidden | Copy DSCP to the outer header, shape the tunnel |
In small offices, the internet upload is the bottleneck far more often than the LAN. A gigabit switch rarely queues voice; a 20 Mbps upload shared with a cloud backup does so every evening.
Step 1: Mark voice traffic
Marking labels each packet with its class, using the DSCP (Differentiated Services Code Point) field in the IP header. Every device along the path can then read the label instead of guessing. The IETF's recommended values are:
| Traffic | DSCP name | Decimal value | Defined in |
|---|---|---|---|
| Voice media (RTP) | EF (Expedited Forwarding) | 46 | RFC 3246, RFC 4594 |
| Call signaling (SIP) | CS5 | 40 | RFC 4594 |
| Video calls and conferencing | AF41 | 34 | RFC 4594 |
| Everything else | Default (best effort) | 0 | - |
For signaling, vendors don't all follow RFC 4594: Cisco has long marked call signaling as class 3, which corresponds to CS3 (24). Signaling is light, so the exact value matters less than using the same one everywhere and giving it a class of its own.
Set the markings at the source. IP phones and PBXs have QoS or DSCP fields for voice and SIP; many already mark RTP as EF, but check rather than assume. Softphones on PCs often don't mark at all, or need an operating system policy to do so. If an endpoint can't mark, RFC 4594 recommends that the router or switch nearest to it classify the traffic instead, for example by the PBX's IP address and RTP port range.
Step 2: Set up the LAN: voice VLAN and trust
Put phones on their own voice VLAN. It makes voice easy to identify, keeps phones apart from PCs and lets you apply rules per VLAN. Most business switches can hand phones their VLAN automatically using LLDP-MED, or CDP on Cisco.
VLAN-tagged frames also carry a 3-bit Layer 2 priority, the CoS (class of service) value defined by IEEE 802.1p. In Cisco's voice QoS examples, voice packets get CoS 5 and signaling CoS 3, a common convention.
Decide where you trust markings. Trust the phone ports and the PBX; don't trust ordinary PC ports, because any application can mark its own traffic as EF. RFC 4594 recommends verifying and policing markings from end-user devices for the same reason.
Step 3: Queue and shape at the internet router
Marking does nothing until a device acts on it. At the router, three settings matter.
- A priority queue for EF: voice packets leave first, always. Cap it at your peak calls times the per-call bandwidth, plus a margin, so a misbehaving device marking everything as EF can't starve the rest of the network.
- A small guaranteed class for signaling, so call setup and transfers don't stall on a full link.
- Shaping below the line rate: set the router's upload rate to about 85 to 95% of the speed you actually measure. Without shaping, packets queue in the ISP modem, whose buffer knows nothing about your priorities; with it, the queue forms in your router, where QoS applies.
Oversized modem buffers that can hold packets for hundreds of milliseconds are known as bufferbloat. Some routers, including many built on Linux, offer smart queue management such as FQ-CoDel, described in RFC 8290 as a way to fight bufferbloat. It keeps queues short and isolates small flows like voice from bulk transfers, and often gives good call quality with very little tuning. Combined with a priority rule for EF, it's a sound choice for a small office.
Download is harder, because you can't control what the internet sends you. Shaping inbound traffic slightly below the line rate makes TCP senders slow down before the ISP's queue fills, which protects incoming voice too.
Step 4: Check the Wi-Fi mapping
Wi-Fi has its own priority scheme, WMM, with four access categories: voice, video, best effort and background. Access points translate DSCP into these categories. Many use a simple rule based on the first three bits of the DSCP, which sends EF to user priority 5 and the video category. RFC 8325 recommends mapping EF to user priority 6, in the voice category. Check your access point's QoS or WMM settings, and remember that coverage and roaming affect Wi-Fi calls more than any marking.
A worked example
A 25-person office has a 100 Mbps download and 20 Mbps upload connection, an on-premise PBX and a peak of 10 simultaneous external calls on G.711. Cisco's planning figure for a G.711 call is about 87.2 kbps each way on Ethernet, so peak voice traffic is about 0.9 Mbps in each direction.
| Setting | Value | Why |
|---|---|---|
| Upload shaper | 18 Mbps | About 90% of the measured 20 Mbps |
| Download shaper | 90 Mbps | Keeps the ISP's queue from filling |
| EF priority queue | Up to 1.5 Mbps | 0.9 Mbps peak plus room for growth |
| Signaling class | Small guaranteed share | SIP needs little bandwidth but shouldn't wait |
| Everything else | Remaining capacity | Backups and browsing share what's left |
If this office used G.729 instead, voice would need about a third of that bandwidth, with some loss of audio quality. VoIP codecs compared covers the trade-offs.
How to test it
- Start a call to an outside number and keep it running.
- Fill the upload: copy a large file to cloud storage or start a backup. Then do the same with a large download.
- Listen for breakups, and read the jitter and packet loss figures in the phone's or PBX's call statistics.
- Capture packets at the router's LAN side to confirm voice arrives marked as DSCP 46. If it arrives as 0, the marking is missing at the phone or is being reset by a switch.
- Repeat with QoS disabled. The difference tells you whether the policy is doing its job.
If audio is still poor with an idle link, the problem isn't congestion. Our guide to fixing VoIP call quality covers jitter, latency and packet loss, and missing audio is a NAT issue covered in one-way audio and dropped calls.
Common mistakes
- Marking without queuing: DSCP labels alone change nothing.
- QoS on the LAN, none on the internet router, where the congestion actually is.
- Shaping at or above the line rate, which leaves the queue in the ISP modem.
- An uncapped priority queue that anything marked EF can take over.
- Trusting PC markings, so video uploads end up in the voice queue.
- Expecting office QoS to fix home workers. Their calls cross their own broadband; see VoIP for remote teams.
For the wider picture of planning a phone system and network together, see our business VoIP phone system guide.
How BtoBSkills can help
Our VoIP support and configuration service covers setting up your PBX, trunks and phones, and resolving call quality issues, including checking that voice markings, VLANs and QoS settings line up from the phone to the internet router. Tell us your connection speeds, router model and number of users, and request a quote.
Frequently asked questions
Does QoS work over the internet?
Do I need QoS if I have a fast connection?
Is SD-WAN a replacement for QoS?
Should phones and computers share a network cable?
Related services
-
VoIP Support Configuration $200.00
Related articles
- How Much Bandwidth Does VoIP Need? A Practical Calculation
Per-call bandwidth for G.711, G.729, G.722 and Opus, the header math behind it, what packet size and encryption add, and a worked example for a whole office.
- VoIP Codecs Compared: G.711, G.729, G.722 and Opus
How G.711, G.729, G.722 and Opus differ in sound quality, bitrate, loss handling and compatibility, and the codec order to use on phones, trunks and apps.
- Fixing VoIP Call Quality: Jitter, Latency and Packet Loss
Target values for latency, jitter and packet loss, a symptom-to-cause table, a step-by-step troubleshooting method and the fixes that solve most VoIP quality problems.
- One-Way Audio and Dropped Calls: NAT, SIP ALG and Firewall Fixes
Why NAT, SIP ALG and firewall rules cause one-way audio and calls that drop at 32 seconds, the settings that fix them and a step-by-step way to find the fault.
- Business VoIP Phone Systems: The Complete Guide for SMEs
How a business VoIP phone system works, the deployment and licensing choices you'll face, what your network needs, and how to switch without losing calls or numbers.
Sources
- IETF RFC 3246: An Expedited Forwarding PHB (EF, codepoint 101110 = 46) (accessed 2026-11-19)
- IETF RFC 4594: Configuration Guidelines for DiffServ Service Classes (accessed 2026-11-19)
- IETF RFC 8325: Mapping Diffserv to IEEE 802.11 (accessed 2026-11-19)
- IETF RFC 8290: The Flow Queue CoDel Packet Scheduler and Active Queue Management Algorithm (accessed 2026-11-19)
- Cisco: Voice Over IP - Per Call Bandwidth Consumption (accessed 2026-11-19)
- Cisco: Configure TOS and CoS for voice traffic (CoS 5 voice, CoS 3 signaling) (accessed 2026-11-19)

