Robotic voices, words that cut out and people talking over each other are the complaints that make teams lose faith in a new phone system. In most cases the PBX isn't the problem: the network is delaying or dropping voice packets on the way. This guide gives you the target numbers, a table that maps each symptom to its likely cause and a step-by-step method to find and fix the real problem.

The three numbers that decide call quality

Latency

Latency is the time your voice takes to travel from your mouth to the other person's ear, one way. It adds up from the codec and packet size, the distance the packets travel, time spent waiting in router queues and the receiver's jitter buffer. ITU-T Recommendation G.114 says that if one-way delay stays below 150 ms, most applications get essentially transparent interactivity, and that 400 ms should not be exceeded for general network planning. Above about 150 ms, people start to talk over each other and leave awkward pauses.

Jitter

Jitter is the variation in packet arrival times. Packets leave every 20 ms, but some arrive early and some late, so the receiving phone holds them briefly in a jitter buffer and plays them out evenly. A bigger buffer absorbs more jitter but adds delay: G.114 advises assuming, for planning, that a buffer adds half its peak delay, so a buffer sized for 50 ms of variation adds about 25 ms on average. Packets that arrive after their slot are thrown away, which sounds exactly like packet loss.

Packet loss

Packet loss is the share of voice packets that never arrive. Phones hide an occasional missing packet with packet loss concealment, which fills the gap with a plausible guess. Losses that come in bursts are much harder to hide and produce the clipped, robotic sound people complain about.

MetricCommon targetWhat users notice when it's exceeded
One-way latencyUnder 150 ms (ITU-T G.114); 400 ms is the planning ceilingTalking over each other, long pauses
JitterUnder 30 msChoppy or robotic audio as packets miss the jitter buffer
Packet lossUnder 1%Missing syllables, robotic sound; bursts are worse than scattered loss

The jitter and loss targets are widely used provider guidelines rather than a single standard; RingCentral, for example, publishes the same 150 ms, 30 ms and 1% thresholds for the end-to-end path. Remember that ping shows round-trip time, so 150 ms one way corresponds to about 300 ms on a ping. For local and regional calls, aim far lower than these ceilings.

MOS and R-factor

Many PBXs and monitoring tools summarize quality as a MOS (mean opinion score, from 1 to 5) or an R-factor from the ITU-T E-model. ITU-T G.109 maps R-factor to user satisfaction:

R-factorQuality categoryUser satisfaction
90 to 100BestVery satisfied
80 to 90HighSatisfied
70 to 80MediumSome users dissatisfied
60 to 70LowMany users dissatisfied
50 to 60PoorNearly all users dissatisfied

G.109 recommends against connections below 50. A score tells you a call was bad; the latency, jitter and loss figures behind it tell you why.

Match the symptom to the likely cause

SymptomLikely causeCheck first
Choppy, robotic audio or missing syllablesPacket loss, or jitter beyond the bufferUpload congestion, Wi-Fi, loss on the ISP link
Talking over each other, long pausesHigh latencyVPN, long network path, satellite or 4G links, oversized jitter buffer
Hearing your own voice backEcho from the far end, made more noticeable by delaySpeakerphones, cheap headsets, analog gateways
One-way audio or no audioNAT, firewall or SIP ALG, not qualitySee one-way audio and dropped calls
Calls drop after about 30 secondsSIP signaling lost through NATThe same NAT and firewall checks
Static, hum or crackleAnalog or hardware faultHeadset, cables, the FXS or FXO port
Problems only at certain timesCongestion from other trafficBackups, updates and video meetings in the router's traffic graphs

Echo deserves a note: VoIP doesn't create it. It comes from sound leaking from a speaker into a microphone, or from analog equipment at the far end, and higher delay makes it easier to hear. Echo cancellers on phones and gateways remove most of it, so persistent echo points to a specific device.

A step-by-step troubleshooting method

  1. Collect real examples. For each bad call, note the time, the numbers involved, the direction and who heard the problem. That lets you find the call in the PBX's call records instead of guessing.
  2. Narrow the scope. Is it one user, one site or everyone? Internal calls, external calls or both? One direction or both? If internal calls on the office network are clear but external calls aren't, look at the internet link or the provider. If one person is affected, look at their device, Wi-Fi or home network.
  3. Measure on the actual path. Check per-call statistics on the PBX or phones, which often show jitter, loss and MOS, and the RTCP reports that carry these figures between endpoints (RFC 3550). Run a continuous ping or MTR to your provider's SIP server for several hours, not a one-off speed test. For hard cases, capture traffic at the receiving end and use Wireshark's RTP stream analysis, which shows jitter, packet timing and lost packets per stream.
  4. Test under load. Make a call while uploading a large file. If latency climbs and audio breaks up, the router's queue is filling (often called bufferbloat), and that's your cause.
  5. Fix one thing at a time and repeat the same test, so you know what worked.

Fixes that work

Stop upload congestion

On business broadband, the cause we find most often is a full upload link: cloud backups, file sync and video meetings pushing voice packets into a long queue. The fixes:

  • Mark voice packets as Expedited Forwarding (DSCP 46), the marking RFC 4594 recommends for telephony, and give that class priority on the router's internet port.
  • Limit the router's upload rate slightly below the real line speed, so the queue builds in your router, where QoS applies, and not in the provider's modem.
  • Turn on smart queue management such as FQ-CoDel or CAKE if your router supports it, to keep queues short.
  • Schedule backups and large uploads outside business hours.

Our guide to QoS for VoIP walks through the settings, and VoIP bandwidth requirements shows how much capacity your calls need.

Move phones off Wi-Fi and VPNs where you can

Wired Ethernet gives the most consistent results for desk phones. Where Wi-Fi is unavoidable, use the 5 GHz band, enable WMM (Wi-Fi multimedia prioritization) and avoid crowded channels. Full-tunnel VPNs add latency and overhead; route voice outside the tunnel or straight to the PBX if your security policy allows it.

Fix the local network

Replace damaged patch cables, check switch ports for errors and speed or duplex mismatches, and confirm PoE switches have enough power budget for every phone. A separate voice VLAN makes prioritization and troubleshooting easier.

Tune the jitter buffer and codec

An adaptive jitter buffer grows when the network gets rough and shrinks when it calms down; enable it on phones and the PBX where available. For remote users on lossy connections, Opus with in-band forward error correction can rebuild lost packets, and keeping the standard 20 ms packet size limits how much audio each loss removes. Our VoIP codecs comparison explains the options.

Escalate with evidence

If loss or jitter starts beyond your router, contact your internet or SIP provider with the times, MTR results showing where loss begins, and per-call statistics. Specific evidence gets a faster answer than "calls sound bad".

Remote and home workers

  • Use a wired connection or 5 GHz Wi-Fi close to the router.
  • Use a good USB or DECT headset; laptop speakers and microphones cause echo. Our comparison of hardphones and softphones covers the options.
  • Pause cloud sync and large uploads during calls.
  • Turn off SIP ALG on the home router if one-way audio appears.

More setup tips are in VoIP for remote teams, and our business VoIP phone system guide covers the network checks to do before any rollout.

How BtoBSkills can help

We troubleshoot call quality on 3CX, Yeastar, FreePBX and other platforms, from PBX and trunk settings to codecs and router configuration. Our VoIP support and configuration service covers diagnosing and resolving technical issues like these. Request a quote with a few examples of bad calls and a description of your network.