VoIP Call Quality: What Actually Affects It (and What Your Provider Doesn't Want You to Ask)
Your calls should sound like calls. If they don’t, the problem is almost always fixable — and it’s almost never what you think.
First: Your Internet Is Probably Fine
Let’s get this out of the way. Most businesses that are considering hosted PBX already have internet that can handle it. Voice calls don’t use nearly as much bandwidth as people assume — a single call needs roughly 100 kbps in each direction. If your office can stream a YouTube video without buffering, you can make phone calls over the internet.
That said, “probably fine” isn’t a guarantee. A good provider will review your connection before you go live — not just check your speed test results, but look at the things that actually matter for voice. More on that in a moment.
If you genuinely have slow internet, that’s a real problem and no amount of configuration will fix it. But this is increasingly rare. The more common issues are subtler, and much more interesting.
The Three Things That Actually Ruin Call Quality
When a VoIP call sounds bad — choppy audio, delays, words getting swallowed — people blame “the internet.” That’s like blaming “the road” when your car rides rough. It might be the road. But it might be the suspension, the tires, or the fact that someone paved it with gravel.
Here’s what’s actually going on:
Latency is the time it takes for your voice to travel from your mouth to the other person’s ear. You experience it as a delay — you say something, and there’s a beat before the other person reacts. Under 150 milliseconds is unnoticeable. Over 300 and the conversation starts to feel like a satellite interview on the news. Latency is mostly determined by the physical distance between you and your provider’s infrastructure, and how many network hops are in between.
Jitter is variation in latency. If every packet of audio arrives with the same small delay, everything sounds fine. But if one packet takes 20ms, the next takes 150ms, and the next takes 40ms, your phone has to scramble to reassemble your voice in the right order. You hear this as choppy or garbled audio. Jitter is usually a symptom of a congested or poorly managed network.
Packet loss is exactly what it sounds like — some of the audio data simply doesn’t arrive. At 1% loss, you might not notice. At 3-5%, you start hearing gaps and distortion. At higher levels, the call becomes unusable. Packet loss happens when network equipment gets overwhelmed and starts dropping traffic.
None of these are exotic or mysterious. They’re all measurable, and they’re all fixable. A provider who can’t explain them to you in plain language probably can’t fix them either.
The Dirty Secret: Ask Where Your Provider’s Infrastructure Lives
Here’s the question that separates serious VoIP providers from everyone else: where does your voice traffic actually go?
A lot of providers — more than you’d expect — are running their platform on commodity cloud infrastructure like AWS, Azure, or Google Cloud. These are incredible platforms for web apps, databases, file storage. They were not designed for real-time voice.
Why does this matter? Voice is UDP traffic. It’s fundamentally different from loading a web page or syncing a file. It’s real-time, it’s latency-sensitive, and it doesn’t get a second chance — if a voice packet arrives late, it’s useless. Commodity cloud platforms are optimized for throughput and reliability of data, not for the precise timing that voice demands.
You can absolutely run VoIP on AWS. It’ll work most of the time. But “most of the time” isn’t good enough for your phones, and when it doesn’t work, your provider is at the mercy of someone else’s infrastructure decisions.
Here’s a simple test: ask your provider for an IP address of their platform and look it up. If it resolves to a major cloud provider, you know what you’re dealing with. That’s not necessarily a dealbreaker, but you deserve to know.
At Moose Networks, our infrastructure is purpose-built for voice. That means equipment and network paths specifically designed to handle UDP traffic with minimal latency and jitter. We’re not renting space in someone else’s cloud and hoping the audio gets there on time. It’s the difference between shipping a fragile package on a general freight truck and hand-delivering it yourself. Call us a bull moose about it, but we think your voice traffic deserves its own lane.
Your Office Network: Wired vs. Wireless
Okay, now let’s talk about the part you actually control: your local network.
We recommend wired connections for desk phones. Full stop. An Ethernet cable from your switch to your phone gives you a dedicated, consistent, low-latency connection. No contention from other devices, no signal strength issues, no interference from the microwave in the break room. Plug it in, it works, you never think about it.
Wireless can work, but it needs to be properly managed. If you’re going to run phones over WiFi — softphones on laptops, for example — the network needs to be set up with voice in mind. That means proper access point placement, adequate coverage without dead spots, QoS (Quality of Service) settings that prioritize voice traffic, and ideally a separate SSID for voice devices.
The difference: a wired phone on a properly configured network will be rock solid, every time. A wireless setup will be fine if the WiFi is well-managed — but “if” is doing a lot of work in that sentence. Most office WiFi networks were set up for email and web browsing, not real-time voice. They’ll need a look.
This is another reason a good provider reviews your setup before go-live. Not to upsell you on networking equipment, but to catch the things that will cause problems later — the switch that’s a decade old, the WiFi access point that’s barely reaching the back office, the network that has no QoS configured at all.
What a Good Provider Does Before Day One
A provider that cares about call quality doesn’t just ship you phones and wish you luck. Before your system goes live, they should:
Assess your internet connection — not just download/upload speed, but latency, jitter, and packet loss during peak hours. A speed test at 6 AM doesn’t tell you anything about what happens at 10 AM when the whole office is online.
Review your local network — switches, cabling, WiFi infrastructure. Identify anything that might cause issues and recommend fixes before you hear them on a call.
Configure QoS where possible — prioritizing voice traffic on your network so that a large file download doesn’t starve your phones of bandwidth.
Monitor after go-live — call quality isn’t a set-it-and-forget-it thing. A good provider watches for quality issues proactively and reaches out before you have to call them.
This is baseline stuff. If your provider isn’t doing this, you’re going to end up troubleshooting call quality problems after the fact instead of preventing them upfront.
Quick Checklist: Is Your Office Ready?
Before you switch to hosted PBX — or if you’re already on one and having quality issues — here’s a quick gut check:
Internet connection
- Do you know your actual speeds? (Run a test at fast.com during business hours, not at midnight.)
- Is your connection shared with anything bandwidth-heavy? (Large uploads, video streaming, cloud backups during the day?)
- Do you have a business-class connection with an SLA, or a residential plan?
Network hardware
- How old is your router/switch? (If you don’t know, it might be too old.)
- Is QoS enabled and configured for voice?
- Are your desk phones plugged in via Ethernet, or running over WiFi?
WiFi (if applicable)
- Do you have adequate coverage in all areas where people take calls?
- Is there a separate network or VLAN for voice devices?
- Are your access points enterprise-grade, or consumer gear from a big-box store?
If you’re unsure about any of these, that’s fine — it’s exactly the kind of thing a provider should help you evaluate. If your provider doesn’t ask about any of this before quoting you, that tells you something.
Not sure if your setup is ready for hosted PBX? Talk to us — we’ll review your network and internet connection and give you an honest read on what needs attention before you switch. No charge for the conversation, no pressure to sign anything.