Introduction: VoIP Works—Until It Doesn’t
Voice over Internet Protocol (VoIP) has fundamentally changed how organisations communicate. From small businesses running Microsoft Teams Phone or Zoom Phone to enterprises relying on SIP trunks and hosted PBXs, VoIP is now mission-critical infrastructure.
Yet despite decades of maturity, poor VoIP call quality remains one of the most common complaints IT teams face. Users report robotic voices, one-way audio, delays, dropped calls, or choppy conversations—often without any obvious network outage.
The reality? VoIP is brutally honest about network health. Where web browsing hides latency and packet loss, real-time voice exposes every weakness.
This article breaks down the true causes of poor VoIP call quality, based on real-world IT experience, not vendor marketing. More importantly, it explains how to diagnose and fix VoIP issues properly, whether you’re supporting five users or five thousand.
1. Insufficient Bandwidth (and Why “Enough” Is Rarely Enough)
Bandwidth is the most commonly blamed factor—and often misunderstood.
A single VoIP call doesn’t use much bandwidth:
- G.711: ~87 kbps per call (each direction)
- G.729: ~31 kbps per call
However, VoIP doesn’t tolerate congestion. If your WAN link is saturated—even briefly—voice packets are delayed or dropped, resulting in immediate quality degradation.
Real-World Insight
In many offices, VoIP issues occur not because bandwidth is insufficient overall, but because:
- Cloud backups start mid-day
- OneDrive or Google Drive sync spikes
- Large Windows updates roll out silently
Best Practice Fix
- Implement Quality of Service (QoS) at the router and switch level
- Prioritise SIP and RTP traffic using DSCP markings
- Monitor peak utilisation, not average usage
- Avoid consumer-grade routers for business VoIP environments
2. Latency: The Silent Conversation Killer
Latency refers to the time it takes for voice packets to travel from sender to receiver.
Acceptable latency thresholds:
- Ideal: < 100 ms
- Acceptable: 100–150 ms
- Poor: > 150 ms
- Unusable: > 300 ms
High latency causes:
- Awkward pauses
- People talking over each other
- Delayed responses that feel “rude” to users
Causes IT Teams Often Miss
- ISP routing inefficiencies
- VoIP servers hosted overseas
- SD-WAN misconfigurations
- VPN tunnelling VoIP traffic unnecessarily
Expert Recommendation
- Ensure VoIP traffic breaks out locally, not via head office VPN
- Choose VoIP providers with local SBCs (Session Border Controllers)
- Test latency using MOS-aware VoIP testing tools, not just ping
3. Jitter: When Packets Arrive Out of Order
Jitter is the variation in packet delivery timing. Even if packets arrive, inconsistent arrival times break audio playback.
Symptoms of Jitter
- Choppy or robotic voices
- Audio cutting in and out
- “Underwater” sound quality
Why Jitter Happens
- Wi-Fi interference
- Oversubscribed switches
- Bufferbloat on routers
- Cheap ISP-provided hardware
Professional Mitigation Strategies
- Enable jitter buffers on VoIP endpoints
- Replace unmanaged switches with managed, QoS-aware switches
- Avoid daisy-chained network devices
- Disable SIP ALG on firewalls (a major jitter culprit)
4. Packet Loss: The Point of No Return
Packet loss is devastating to VoIP. Unlike data transfers, lost voice packets are never retransmitted.
Even 1–2% packet loss can make calls unusable.
Common Packet Loss Sources
- Failing network cables or patch panels
- Overloaded firewalls
- ISP congestion during peak hours
- Misconfigured VLANs
- Duplex mismatches on switch ports
Real-World Tip
Packet loss is often intermittent, making it difficult to diagnose. Continuous monitoring using:
- VoIP MOS scoring
- RTP stream analysis
- Long-duration packet captures
…is far more effective than short tests.
5. Wi-Fi and VoIP: A Risky Relationship
VoIP over Wi-Fi can work—but it’s inherently fragile.
Wi-Fi VoIP Problems Include
- Channel interference
- Roaming issues between access points
- Power-saving features dropping packets
- High client density
When Wi-Fi Is Acceptable
- Enterprise-grade APs
- Proper RF planning
- Voice-optimised SSIDs
- Fast roaming (802.11k/r/v)
Best Practice
For desks, wired Ethernet still wins. Reserve Wi-Fi VoIP for:
- Softphones on laptops
- Mobile handsets
- Temporary workspaces
6. Firewalls, NAT, and SIP ALG: The Hidden Saboteurs
Many VoIP issues trace back to well-meaning firewall features.
SIP ALG (Application Layer Gateway)
Despite its name, SIP ALG frequently:
- Modifies SIP packets incorrectly
- Breaks NAT traversal
- Causes one-way audio or dropped calls
Industry Consensus
Disable SIP ALG unless explicitly required by your VoIP provider.
Also ensure:
- Required SIP and RTP ports are open
- Stateful inspection isn’t timing out RTP streams
- Firewalls are sized for concurrent VoIP calls
7. Endpoint and Hardware Quality Matters More Than You Think
Cheap headsets and microphones introduce:
- Echo
- Static
- Low audio clarity
Outdated drivers can also cause:
- One-way audio
- Microphone dropouts
- Application crashes
IT Pro Recommendation
- Standardise on certified VoIP headsets
- Keep firmware and drivers updated
- Avoid mixing USB audio devices across vendors
8. Your VoIP Provider Does Matter
Not all VoIP platforms are equal.
Key Provider Differentiators
- Geographic server placement
- Network redundancy
- Peering agreements with ISPs
- SLA-backed uptime
- Support response times
Real-World Observation
Many VoIP “quality” issues blamed on internal networks are actually upstream provider routing problems—especially during peak business hours.
Always test:
- Multiple call paths
- Different times of day
- Direct-to-provider connectivity
Final Thoughts: VoIP Quality Is a Network Health Indicator
Poor VoIP call quality is rarely caused by a single issue. It’s usually death by a thousand cuts—small inefficiencies stacking up until users complain.
From years of real-world IT support experience, one truth stands out:
If VoIP sounds bad, your network has a problem—even if everything else seems fine.
Treat VoIP as a diagnostic tool, not just a service. With proper monitoring, prioritisation, and provider selection, VoIP can deliver crystal-clear calls that rival (or exceed) traditional telephony.
If your organisation continues to struggle, a VoIP-focused network audit is often the fastest way to uncover issues that generic monitoring tools miss.
From my early days on the helpdesk through roles as a service desk manager, systems administrator, and network engineer, I’ve spent more than 25 years in the IT world. As I transition into cyber security, my goal is to make tech a little less confusing by sharing what I’ve learned and helping others wherever I can.