Why your VoIP calls are choppy, robotic or dropping, and how to fix it.

What choppy audio is actually telling you

A VoIP call is not one continuous sound. It is your voice chopped into thousands of tiny packets, sent across the network and reassembled at the other end many times a second. As long as every packet arrives on time and in order, the call sounds natural. The trouble starts when packets turn up late, out of order, or go missing altogether.

When that happens the handset has to fill in the blanks. It guesses, repeats or skips, and you hear that as choppy, robotic, warbly or half-swallowed words. So the symptom is audio, but the cause is nearly always the network underneath. Chasing new handsets or a new phone provider before you fix the network usually just moves the problem around.

Jitter, packet loss and latency, in plain terms

Three network gremlins cause most VoIP grief, and it helps to know which one you are fighting.

• Jitter. The gaps between packets keep changing instead of arriving evenly. Voice needs a steady beat, so uneven arrival comes through as stutter and warble. A jitter buffer smooths small wobbles, but not big ones.
• Packet loss. Some packets never arrive at all. Even a couple of per cent lost is enough to clip words and drop syllables, because there is no time to resend them on a live call.
• Latency. Everything arrives, but slightly late. Too much delay gives you that awkward talking-over-each-other feel, and encourages echo. On its own it is less damaging than jitter or loss, but it stacks up with them.

Robotic or broken-up audio is usually jitter or loss. That satellite-phone delay, where you keep interrupting each other, is latency. Knowing which you have points straight at the fix.

Simple checks you can do first

Before anyone touches a setting, a few quick observations narrow things down a lot, and they are worth noting so you can describe the problem clearly when you call for help.

• When does it happen? All day, or only when the office is busy? Choppiness that appears mid-morning and eases off at lunch usually points to a congested link and a missing quality-of-service setting.
• Who does it affect? Everyone, one desk, or only the cordless handsets? If it is just the wireless phones or laptop softphones, Wi-Fi is the prime suspect.
• Wired or wireless? Try a known-good call on a handset plugged straight into the network. If that call is clean, the phone system is fine and the trouble is in the path to the other handsets.
• One direction or both? If callers can hear you but you cannot hear them, or the reverse, that one-way audio usually points at the firewall or a SIP setting rather than raw congestion.

None of this fixes anything on its own, but it saves a lot of guesswork. The more precisely you can describe when and where it happens, the faster the real cause gets pinned down.

Why calls drop out completely

A call that cuts out mid-sentence is a different beast from one that just sounds rough. Dropouts are usually about the signalling that sets up and holds the call, called SIP, rather than the audio itself. A router that closes the connection too early, a firewall that is too aggressive, or a feature called SIP ALG meddling with the traffic can all sever a call that was otherwise fine.

A useful clue is timing. If calls die at roughly the same point every time, say around thirty minutes, a timeout or keep-alive setting is almost certainly the culprit, and it is a settings fix rather than a hardware one. If dropouts are random, we look harder at the internet link itself and at Wi-Fi handsets losing their connection.

The Wi-Fi trap

Cordless VoIP handsets and softphones on laptops are convenient, but Wi-Fi is shared and unpredictable, and voice hates unpredictability. A microwave, a neighbouring network, a thick wall or simply walking from one end of the office to the other can all introduce the jitter and dropouts that wreck a call. A desk phone on a network cable rarely has these problems.

Where we can, we put fixed handsets on wired connections and keep Wi-Fi for people who genuinely move around. If mobile calling matters, the answer is proper business-grade wireless with clean roaming between access points, not consumer gear stretched past its limits.

Echo and one-way audio

Two related complaints come up often and are worth calling out, because their causes differ from plain choppiness. Echo, where you hear your own voice back a fraction late, is usually a mix of latency and a device sending sound back into the call. It often traces to a particular handset, headset or speakerphone rather than the whole system, so swapping one device in and out quickly shows whether it is the source.

One-way audio, where one side can be heard and the other cannot, is a classic firewall or router symptom. The signalling that connects the call gets through, but the actual voice cannot find its way back in one direction. It is almost always a settings problem around SIP, ports or that SIP ALG feature, and once the network is configured to let voice flow both ways it clears up straight away.

Quality of service, the setting that matters most

By default, most networks treat every packet the same. A big email attachment, a cloud backup running in the background and your phone call all compete for the same space, and when the link gets busy, your voice packets wait in the queue with everything else. That is where the choppiness creeps in.

Quality of service, or QoS, tells the network to let voice jump the queue. Configured properly on the router, it keeps calls clear even when someone is uploading a huge file or the office is streaming a training video. This one change fixes more choppy-call complaints than almost anything else, and it costs nothing but the time to set it up correctly.

Will a faster internet plan fix it?

Usually not, and it is worth saying plainly so you do not waste money. A single VoIP call needs only a trickle of bandwidth, so a bigger plan rarely cures choppy audio on its own. The problem is almost never total capacity, it is how the network behaves when it is busy, and whether voice is being prioritised or left to fight for space.

Sorting out QoS, fixing Wi-Fi or cabling, and checking the router and firewall settings will do far more than an upgraded plan. There are cases where an unstable or overloaded link is the real issue, but we would rather measure that first than sell you speed you may not need.

How we diagnose and fix it

We work along the whole path a call takes: the internet link, the router and firewall, your network and Wi-Fi, and the phone system itself. We measure jitter, packet loss and latency so we are dealing with facts, not guesses, and find exactly where the audio is breaking down.

From there it is methodical. We set up quality of service so voice always takes priority, fix the SIP, timeout and firewall settings behind dropped calls, disable troublesome features like SIP ALG where needed, and get fixed handsets onto solid wired connections. If Wi-Fi calling is part of your day, we make the wireless genuinely up to it. You can see how this fits our wider phone work on the business phones and networks and Wi-Fi pages.