What Makes VoIP Call Quality Good or Bad

VoIP calls are streams of small packets, and quality is about whether those packets arrive on time, in order, and at all. Three measurements capture it. Latency: how long a packet takes to arrive; one-way latency under about 150 ms feels natural, and beyond that people start talking over each other. Jitter: variation in packet arrival timing; under about 30 ms is the common target, and above it audio turns choppy. Packet loss: packets that never arrive; even 1% is audible as dropouts.

Bandwidth is rarely the problem

A call uses roughly 100 kbps each way, so almost any business connection has room for dozens of calls. Quality problems almost always come from congestion and equipment, not total speed: an upload saturated by a cloud backup, a cheap router with bufferbloat, or phones on busy Wi-Fi instead of ethernet.

Fixes that actually work

Wire the phones: ethernet removes the single biggest jitter source. Turn on QoS (quality of service) on the router so voice packets jump the queue ahead of downloads. Replace aging routers that buffer heavily under load. And when the connection itself is the weak link, a circuit sourced for low-latency voice beats tuning around a bad one.

Diagnosing an existing problem? Our troubleshooting guide walks through the tools we use, including our test line that reads results back to you on the call.

How to actually measure it

Speed-test numbers barely matter; what you want is latency, jitter, and loss measured over time, especially during business hours when the network is loaded. Run a continuous ping to a stable host for an hour and watch for spikes; better, use a VoIP-specific test that reports MOS (Mean Opinion Score), the 1-to-5 scale where 4.0+ is business-grade. One clean test at 7 AM proves nothing; the 2 PM measurement, while the office backup runs, is the honest one.

Network setup that prevents problems

• Wire every desk phone; Wi-Fi handsets inherit every hiccup the airspace has.
• Enable QoS on the router with voice traffic prioritized, and confirm it actually engages under load.
• Put phones on their own VLAN in larger offices, isolating voice from bulk data at the switch level.
• Retire consumer-grade routers that buffer heavily; bufferbloat is the classic "internet is fast but calls are choppy" culprit.
• Schedule backups and big syncs outside calling hours, or cap their bandwidth.

When it really is the ISP

If wired phones with QoS still show jitter spikes and loss at the router's WAN side, the problem is upstream and no local tuning fixes it. Document the measurements, open a ticket, and if the circuit cannot carry voice reliably, that is the moment to consider a connection sourced for it: our managed business internet is tuned for low-latency voice and billed with the phones, which also ends the two-vendor finger-pointing when something degrades.