VoIP Call Quality: MOS Scores, Jitter, and Troubleshooting (2026)

Bad VoIP call quality — robotic voices, echo, dropped syllables, sudden disconnections — is one of the most frustrating problems a business can face. The good news: almost every VoIP quality issue has a measurable cause and a specific fix. This guide teaches you how to measure call quality, interpret the numbers, and resolve the most common problems without waiting for vendor support.

What Determines VoIP Call Quality?

VoIP calls are real-time data streams. Unlike downloading a file, where the network can buffer and retry, a voice call has a hard real-time constraint — every packet must arrive within 150ms or the conversation degrades. Four network metrics determine the quality of that stream:

• Latency — the one-way delay from speaker to listener (measured in milliseconds)
• Jitter — the variation in packet arrival time (measured in milliseconds)
• Packet loss — the percentage of audio packets that never arrive
• Bandwidth — the raw throughput available for voice traffic (rarely the actual problem)

MOS Score Explained

Mean Opinion Score (MOS) is the standard measurement of perceived voice quality, rated on a 1–5 scale:

• 5.0 — Perfect, studio-quality audio (theoretical maximum; no real-world network achieves this)
• 4.0–4.5 — Excellent. HD voice. Most enterprise VoIP targets this range.
• 3.5–4.0 — Good. Slight degradation audible but not annoying. Acceptable for business calls.
• 3.0–3.5 — Fair. Noticeable quality issues. Some callers will comment.
• 2.0–3.0 — Poor. Communication is difficult. Callers are frustrated.
• Below 2.0 — Unusable. Calls should not be made at this quality.

Target a MOS of 4.0 or above for business calls. A MOS below 3.5 will affect customer satisfaction and agent productivity. Most cloud VoIP providers publish their network MOS in their SLA — ask for it.

The 4 Main VoIP Quality Problems

Jitter

Jitter occurs when audio packets arrive at uneven intervals. The listener hears choppy, robotic, or stuttering audio. Acceptable jitter is under 30ms. Above 50ms and most callers will notice. Jitter is caused by network congestion, poor QoS configuration, and Wi-Fi interference. Fix: enable QoS to prioritize voice packets, switch to Ethernet, or upgrade your router.

Latency

Latency is end-to-end delay — the time it takes your voice to reach the listener. Under 150ms one-way is acceptable; under 80ms is ideal for natural conversation. Above 200ms callers talk over each other (this is the satellite phone effect). Causes: geographic distance to the VoIP server, congested networks, too many router hops. Fix: choose a provider with data centers close to your location, use a wired connection.

Packet Loss

Packet loss means audio data never arrives. The listener hears dropouts — clipped syllables, missing words, brief silences mid-sentence. Even 1% packet loss is perceptible in a conversation. Above 3% makes calls difficult. Above 5% calls become unusable. Causes: network congestion, bad cables, failing network hardware, ISP issues. Fix: check physical cables, run a packet loss test, contact your ISP if loss is upstream.

Echo

Echo is when the caller hears their own voice reflected back with a delay. This is caused by acoustic coupling (microphone picking up speaker output), electrical impedance mismatches, or misconfigured echo cancellation. Fix: use a headset instead of speakerphone, update VoIP app and firmware, ensure echo cancellation is enabled in softphone settings.

How to Test Your VoIP Call Quality

Before troubleshooting, measure the problem with real numbers. Use these tools:

• Provider network test: Most VoIP providers offer a browser-based test that measures latency, jitter, and packet loss to their specific servers
• PingPlotter or WinMTR: Traces the network path and shows packet loss at each hop — helps identify if the problem is in your local network, your ISP, or further upstream
• Speedtest.net: Basic bandwidth check — useful for confirming you have enough raw throughput
• VoIP provider admin portal: Check per-call quality scores if your provider offers this (Zonitel, RingCentral, and others show call-level MOS in analytics)
• Wireshark: Advanced packet capture for deep analysis of jitter and packet loss patterns

Network Requirements for Good VoIP Quality

• Bandwidth: 1 Mbps per concurrent call (actual consumption is ~100 kbps, but headroom prevents congestion)
• Latency: Under 150ms one-way (under 80ms for HD quality)
• Jitter: Under 30ms (under 10ms for optimal)
• Packet loss: Under 1% (under 0.5% for best quality)
• Router: Must support QoS (DSCP marking) to prioritize voice traffic
• Connection: Wired Ethernet preferred over Wi-Fi for any call center or heavy-use deployment

QoS Settings That Make a Real Difference

Quality of Service (QoS) tells your router to prioritize voice packets over everything else — file downloads, video streaming, software updates. Without QoS, a Netflix stream or a Windows update can fill your pipe and make every VoIP call choppy. Configure QoS on your router with these settings:

• DSCP (Differentiated Services Code Point) marking: Mark VoIP traffic as EF (Expedited Forwarding) — decimal 46, binary 101110
• Traffic shaping: Reserve 20–30% of your upload bandwidth specifically for voice traffic
• Application-based QoS: Some routers identify VoIP apps (Zoom, softphone) and prioritize them automatically
• Separate VLAN for voice: Enterprise approach — puts all phones on a dedicated network segment

Common Call Quality Problems and Their Fixes

Choppy or Robotic Audio

• Cause: High jitter (>30ms) or packet loss (>1%)
• Fix 1: Enable QoS on router to prioritize voice
• Fix 2: Switch from Wi-Fi to Ethernet
• Fix 3: Reduce concurrent internet activity (downloads, streaming) during calls
• Fix 4: Upgrade home/office internet plan if bandwidth is consistently maxed

One-Way Audio (You Can Hear Them, They Cannot Hear You)

• Cause: Firewall blocking outbound SIP/RTP or NAT traversal failure
• Fix 1: Confirm ports 5060 (SIP) and 10000–20000 UDP (RTP) are open on your firewall
• Fix 2: Enable STUN/TURN in your softphone or IP phone settings
• Fix 3: Disable SIP ALG on your router (often causes NAT issues with VoIP)

Calls Dropping Mid-Conversation

• Cause: SIP session timeout, network interruption, or ISP instability
• Fix 1: Enable SIP keepalive in your VoIP client settings
• Fix 2: Run a continuous ping to your provider's server to check for packet loss spikes
• Fix 3: Contact your ISP if drops correlate with peak usage hours

Echo During Calls

• Cause: Acoustic feedback from speaker to microphone, or disabled echo cancellation
• Fix 1: Use a headset instead of built-in speakers and microphone
• Fix 2: Ensure echo cancellation is enabled in softphone audio settings
• Fix 3: Lower speaker volume to reduce acoustic coupling

Codecs Explained: G.711, G.722, and Opus

A VoIP codec is the algorithm that compresses your voice into data packets. The codec you use affects both call quality and bandwidth consumption:

• G.711 (PCMU/PCMA): The PSTN-equivalent codec. 64 kbps per direction. High quality, high bandwidth. Standard in North America.
• G.729: Compressed codec. 8 kbps per direction. Lower quality, very low bandwidth. Good for poor connections but noticeable quality drop.
• G.722 (HD Voice): Wideband codec. 64 kbps per direction but double the frequency range of G.711. Noticeably clearer voice. Requires both ends to support it.
• Opus: Modern, adaptive codec. 6–510 kbps, automatically adjusts to network conditions. Used by WebRTC-based platforms (browser calls). Best codec for variable network quality.

For the best call quality on a stable connection, prefer G.722 (HD Voice) or Opus. For low-bandwidth or unreliable connections, G.729 maintains intelligibility at the cost of some fidelity.

When It's the Provider's Network, Not Yours

Not every call quality problem originates on your network. If your local tests show clean metrics but calls are still poor, the issue may be with your VoIP provider. Signs of a provider-side problem:

• Multiple users at different locations reporting the same problem simultaneously
• Quality degrades at specific times of day (provider network congestion)
• Your network test to a neutral server is clean, but the provider's test shows high jitter
• Provider status page shows an incident in progress
• Problem started after a provider software update

If you suspect the provider, run a simultaneous call on a different carrier to compare. If the second carrier is clean, escalate to your provider with your test results as evidence.

Frequently Asked Questions

What is a good MOS score for VoIP?

A MOS of 4.0 or above is considered excellent for business VoIP. Most enterprise providers target 4.0–4.3. Scores below 3.5 will noticeably affect call experience. If your provider shows MOS in their analytics portal, flag any calls below 3.5 for investigation.

How much bandwidth does a VoIP call use?

A single VoIP call uses approximately 85–100 kbps of bandwidth bidirectionally (with packet overhead). Ten simultaneous calls require roughly 1 Mbps. Bandwidth is rarely the bottleneck in 2026 — jitter and latency cause most quality problems, not raw throughput.

Why does my VoIP call sound fine internally but bad to outside callers?

Calls to other users on the same VoIP platform stay within the provider's network and bypass the public internet entirely — they are always high quality. Calls to external PSTN numbers must traverse the public internet and sometimes multiple carrier hand-offs, where quality can degrade. This is a strong argument for ensuring your provider has high-quality PSTN interconnects.

Does Wi-Fi affect VoIP call quality?

Yes, significantly. Wi-Fi introduces variable jitter due to radio interference, channel congestion, and the CSMA/CA access control mechanism. Wired Ethernet eliminates most jitter-related audio issues. If Ethernet is not possible, use 5 GHz Wi-Fi (less congestion than 2.4 GHz) and ensure the device is within strong signal range.

What does disabling SIP ALG do?

SIP ALG (Application Layer Gateway) is a router feature that attempts to modify SIP packets to help with NAT traversal — but it often does this incorrectly and breaks VoIP signaling. Most VoIP providers recommend disabling SIP ALG entirely and letting the softphone or IP phone handle NAT traversal through STUN/TURN. Check your router admin panel under "firewall" or "application" settings.