QoS for VoIP: Stop Choppy Calls on Your Business Network

QoS for VoIP — Quality of Service configuration on the business network — is the difference between calls that sound great and calls that sound like the other party is underwater. The technology has been around for decades; what trips businesses up is configuring it correctly on a network that may not have been designed with voice traffic in mind. Here's a practical guide to what QoS does for VoIP and what the common configuration mistakes look like.

Why VoIP Needs QoS

Voice traffic is uniquely sensitive to network conditions. A web page that loads in 3 seconds instead of 1 second is mildly annoying. A voice call with 200ms of latency, 1% packet loss, or 30ms of jitter sounds broken. The underlying issue is that voice is real-time — packets arriving late or dropped can't be retransmitted in time to be useful. QoS exists to prioritize voice packets so they don't sit in queues behind bulk data transfers or get dropped during congestion.

On an uncongested network, QoS isn't strictly necessary. On any network that ever experiences congestion — and that's virtually every business network at some point — QoS is what keeps voice quality consistent.

How QoS Actually Works

QoS works through traffic classification and prioritization at network devices. The sequence:

• Voice packets get marked with a specific DSCP value (typically EF — Expedited Forwarding — for voice)
• Network devices (switches, routers, firewalls) recognize the marking and place voice packets in priority queues
• During congestion, priority queues get served first, so voice doesn't wait behind bulk data
• The classification and marking continues through every hop the voice traffic takes

For QoS to work, every device the voice traffic passes through needs to honor the marking. A single device that strips or ignores DSCP markings breaks the chain.

Where QoS Configuration Goes Wrong

Common configuration mistakes that produce choppy VoIP:

• QoS not configured at all — voice and data share the same queues; during congestion, voice suffers
• Markings stripped at firewall or edge — DSCP markings preserved on the LAN but stripped before reaching the carrier, so the carrier side doesn't honor priority
• Insufficient bandwidth allocation — QoS provides priority but not unlimited capacity; if voice exceeds the allocated portion, it still suffers
• Wireless QoS not configured — wired QoS in place but Wi-Fi clients running softphones don't get the same priority on the wireless side
• QoS misconfigured on remote sites — branch offices configured differently than the main office, with traffic crossing inconsistent QoS domains
• Bandwidth oversubscribed — even with QoS, if the circuit is severely undersized, voice quality degrades during peak usage

The QoS Checklist for VoIP

A working QoS configuration for VoIP includes:

• Voice traffic identified and marked with DSCP EF at the source (the IP phone or softphone)
• Switches configured to honor DSCP markings and place voice in priority queues
• Router configuration that prioritizes voice traffic at the WAN edge
• Adequate bandwidth allocation for voice (calculate based on concurrent call count and codec)
• Firewall configuration that preserves DSCP markings on traffic egress to the SIP provider
• WMM (Wi-Fi Multimedia) enabled on wireless infrastructure for wireless voice clients
• SIP and RTP traffic correctly identified by the firewall
• Monitoring of voice quality metrics (MOS scores, jitter, packet loss) to validate the configuration is working

When QoS Isn't Enough

QoS solves the priority problem but not the capacity problem. If the underlying network simply doesn't have enough bandwidth, no amount of QoS configuration produces good voice quality during peak usage. The other constraint QoS doesn't solve is jitter from variable network paths — when traffic takes inconsistent paths with varying latency, jitter increases even on well-prioritized voice traffic.

If QoS is correctly configured and voice quality is still poor, the next investigations are: bandwidth utilization during call-quality complaints, jitter measurements from the SIP provider's perspective, packet loss between sites for hybrid PBX scenarios, and Wi-Fi performance for softphone users. A conversation with our team can scope a VoIP quality assessment for your specific environment.