ServicesHow we get paidResultsRefer a businessAboutContact614-224-2003
Home / Blog / Voice

VoIP call quality problems, diagnosed and fixed.

Choppy audio, one-sided calls, and dropped connections are almost always fixable. Here is a systematic approach to diagnosing and resolving VoIP quality issues.

Rings Jonathan and the team 24x7.

4 minRead. Filed under Voice.
2025Published June 8, 2025.
500+Clients served. 23 years in telecom.

400+ carriers and platforms, compared.

AT&TVerizonLumenSpectrumComcastCoxT-MobileFrontierZayoCogentRingCentralNextiva8x8ZoomMicrosoft TeamsWebex

Stop Replacing Phones Before You Diagnose the Network

Bad call quality is one of the most disruptive - and most misdiagnosed - problems in a business environment. Businesses replace phones, swap carriers, and call their ISP, often without addressing the actual root cause.

It is almost never the phones or the carrier. Here is a systematic approach that identifies the real problem the first time.

The Four Culprits

VoIP quality problems come from four sources. Each produces slightly different symptoms.

01

Jitter

Inconsistent timing between packets, which shows up as choppy or garbled audio.

02

Packet loss

Data that never arrives, which causes gaps, dropouts, or one-sided calls.

03

Latency

Delay in transmission, which produces talk-over and awkward pauses on a call.

04

Bandwidth saturation

Not enough capacity for voice alongside other traffic, which degrades quality for everyone on the phone at once.

The Fix, In Order

1

Run a VoIP-specific test

A standard speed test will not reveal jitter or packet loss. Use a VoIP-specific tool - most SIP providers have one, and tools like PingPlotter or VoIPmonitor show real-time jitter, packet loss, and MOS score. Run it during peak business hours, not at 2 AM when the network is idle.

2

Check your router for SIP ALG

SIP ALG is a router feature meant to help VoIP traffic pass through NAT, and it almost universally breaks it instead. Disable it if it is enabled. This single change resolves a significant share of VoIP problems businesses have been chasing for months.

3

Implement Quality of Service (QoS)

QoS tells your router to prioritize voice traffic over everything else. Without it, a large file download or a Windows update in the background can saturate your connection and degrade call quality for every call on the line.

4

Audit your bandwidth

Each simultaneous VoIP call needs roughly 85-100 Kbps in each direction on the G.711 codec. Add up your maximum expected concurrent calls and confirm your connection has headroom well beyond that. If utilization regularly runs 70%+ during business hours, bandwidth is contributing to the problem and needs an upgrade or better traffic prioritization.

5

Isolate voice traffic on its own VLAN

If quality issues persist after QoS and bandwidth are addressed, put voice on its own VLAN. This is standard practice on properly designed business networks and stops non-voice devices from ever competing with your phones for bandwidth.

Quick Diagnostic Checklist

  • Ran a real VoIP test during business hours, not off-peak.
  • Confirmed SIP ALG is disabled on the router.
  • QoS is configured to prioritize voice traffic.
  • Bandwidth headroom exceeds maximum concurrent call load, with utilization under 70% at peak.
  • Voice traffic runs on its own VLAN if problems persist after the steps above.

The Bottom Line

Most VoIP quality problems are solvable without replacing your phone system or switching carriers. They are network configuration issues that a qualified telecom engineer can identify and resolve in a single assessment.

Quick reference

Match what you hear to the likely cause

Each call quality problem has a usual suspect. Start with the one that matches what your staff describe.

  • Choppy or robotic voices usually point to packet loss on the internet circuit or Wi-Fi.
  • Talking over each other points to latency, often from traffic taking a long route or a busy link.
  • One-way audio is almost always a firewall or NAT setting, not the carrier.
  • Calls that drop at the same mark, often 15 or 30 minutes, point to a firewall session timeout.
  • Echo is usually a handset, headset or speakerphone problem at one desk, not the network.

Let's scope it together.

Talk to the Buckeye team - the owner is involved in every engagement, and there's no advisory fee.

Book a call