When a VoIP call sounds bad, the phone gets the blame. Nine times out of ten the phone is innocent. Call quality lives and dies in the network the call travels: your office wiring, your Wi-Fi, your router, your internet connection, and your provider's platform, in that order of likelihood. The good news is that voice is not mysterious. It needs four things from a network, all four are measurable, and all four have fixes.
This guide gives you those four numbers in plain English, explains where quality problems actually come from, and draws an honest line between what your network owes the call and what your provider owes it. It pairs with our network readiness guide, which covers the pre-deployment checkup; this is the version for a system that is already live and needs to sound its best every day.
The quick answer
A VoIP call needs about 100 kbps of bandwidth in each direction, one-way latency under 150 milliseconds, jitter under 30 milliseconds, and packet loss under 1 percent. Most quality problems trace to the upload side of the internet connection, congested Wi-Fi, or a router with no voice prioritization, not to the phone system. Wired desk phones, a router with QoS, and a provider that monitors the platform side cover the rest.
- Bandwidth
- The capacity of your connection. Each call uses roughly 100 kbps up and down; upload is usually the tighter side.
- Latency
- How long a voice packet takes to travel one way. Under 150 milliseconds sounds natural; beyond that, people talk over each other.
- Jitter
- Variation in packet arrival timing. Under 30 milliseconds is the target; more causes choppy audio and dropped syllables.
- Packet loss
- Packets that never arrive. Voice cannot resend them, so even 1 percent is audible as clipped words.
- QoS (Quality of Service)
- Router settings that let voice traffic go first when the connection is busy.
How much bandwidth do calls actually need?
Less than most people think, and in a different place than most people check. A standard-quality call uses roughly 100 kbps in each direction. Ten simultaneous calls need about 1 Mbps, with headroom, in each direction. On paper, almost any business connection clears that bar easily.
The catch is the phrase each direction. Many business internet plans are asymmetric: a connection sold as 300 Mbps may deliver only 10 or 20 Mbps upload. Your voice leaves the building on that upload side, and it shares the lane with cloud backups, video meetings, file syncs, and security cameras. When the upload lane fills, callers hear it as your voice breaking up while the other side sounds fine to you. The FCC's broadband speed guide and its companion on shared connections are useful plain-language references for what different activities consume.
So the bandwidth question is not "is my internet fast?" It is "how much upload is free at 10 o'clock on a Tuesday morning?" That distinction explains a large share of the mystery quality complaints we investigate.
What are the three numbers that decide how a call sounds?
Bandwidth is the pipe. These three numbers describe the traffic inside it.
Latency is travel time. Under 150 milliseconds one way, conversation feels natural. Between 150 and 300, people start stepping on each other's sentences, the way two news anchors do on a satellite link. Beyond 300, conversation genuinely breaks down. Distance and route matter here, which is one reason it helps when your provider's platform is close: calls from the Piedmont to a platform with a presence in North Carolina travel a short road.
Jitter is inconsistency in travel time. Voice packets are supposed to arrive like a steady drumbeat, one every 20 milliseconds. When some arrive early and some late, the phone's jitter buffer smooths what it can, but past about 30 milliseconds of variation the audio turns choppy and syllables vanish. Congested networks and Wi-Fi are the usual sources.
Packet loss is the unforgivable one. A web page can re-request a lost packet and you never notice. A live conversation cannot wait for a resend, so a lost packet is a clipped word, and a string of them is the "you're breaking up" call. Even 1 percent loss is audible. If loss climbs past a few percent, calls drop entirely, and our guide to why calls drop picks up that story.
Why is Wi-Fi the usual suspect?
Wi-Fi adds exactly the two things voice hates: jitter and loss. Radio interference, distance from the access point, walls, microwaves, and every other device competing for airtime make wireless delivery timing unpredictable in ways that streaming video absorbs and live voice does not.
The rule we give every customer is simple. Desk phones get wired Ethernet, always, no exceptions worth making. Softphones and mobile apps like Digital Voice Plus can absolutely run on Wi-Fi, but they deserve business-grade access points with enough coverage for the space, not the internet provider's combo box radiating from a closet at the far end of the building. If your conference room calls sound worse than your front desk calls, this paragraph is usually the reason.
What is QoS, and does your router respect it?
Quality of Service is the router setting that lets voice go first. Without it, your connection treats a voice packet and a cloud-backup packet as equals, and during busy moments the backup wins by volume. With QoS configured, the router holds the door for voice, and the backup finishes a few seconds later without anyone noticing.
Consumer-grade routers often have weak or missing QoS, and this is the piece of hardware where spending a few hundred dollars changes daily life for everyone on the phones. A business-class router or firewall with voice prioritization, configured once, quietly prevents the majority of busy-hour complaints. It is also the first thing a good provider checks during installation, which is a fair test of the provider: ask how they handle QoS, and listen for a specific answer.
Which parts belong to your provider, not your network?
Quality is a shared responsibility, and it is worth knowing where the line sits. Your side of the line: the wiring, the Wi-Fi, the router and its QoS, and the internet connection you buy. The provider's side: the codecs that encode your voice, the jitter buffers that smooth arrival timing, the carrier routes your calls ride, the geographic distance to the platform, and the monitoring that catches degradation before you call about it.
That provider side is not all equal. A platform built with geo-redundant facilities and multiple carriers can route around a degrading path; a reseller renting one wholesale connection cannot. The FCC's VoIP overview explains the layers involved, and our evaluation checklist turns them into questions you can ask any provider, ours included.
How do you test before you blame anyone?
A speed test alone will not settle it, because speed tests measure capacity for a few seconds, not voice behavior over a workday. Do these three things instead.
- Run a VoIP-specific quality test, one that reports latency, jitter, and packet loss, not just megabits. Run it at your busiest hour, not at 7 in the morning, because quality problems are busy-hour problems.
- Note the pattern. Bad on Wi-Fi but fine on wired phones points inside the building. Bad everywhere at 10 a.m. but fine at lunch points at upload congestion. Bad on calls to one region only points at carrier routing, which is the provider's job to fix.
- Write down three specifics before you call support: the time, the extension, and the number dialed. With those, a provider that monitors its platform can pull the actual call and see the numbers, which turns an argument into a diagnosis.
If the tests point at an aging phone closet rather than the network, that is a different conversation, and our guide to the signs a PBX needs replacement covers it.
What does a voice-healthy office look like?
Put the pieces together and the reference setup is not exotic. A business internet plan chosen for its upload speed, not its advertised download number, with enough headroom that voice never uses more than a modest share. A business-class router with QoS configured to prioritize voice, installed once and left alone. Desk phones on wired Ethernet, ideally on their own voice VLAN so phone traffic and computer traffic stay in separate lanes. Business-grade Wi-Fi access points, placed for coverage, carrying the softphones and mobile apps. And a provider whose platform sits close, rides multiple carriers, and gets monitored by people who can read a call's numbers.
Notice what is not on the list: the newest phones, the most expensive plan, or any exotic equipment. Most offices are one router upgrade and one afternoon of configuration away from this picture. The businesses that sound flawless on every call are rarely spending more. They set it up in the right order.
Why do Piedmont businesses call Carolina Digital Phone?
Because we treat call quality as an engineering claim, not a slogan. We own and operate our geo-redundant platform, with facilities in North Carolina, so Piedmont calls travel a short road, and we look at your actual network, your router, your Wi-Fi, your upload headroom, before installation instead of after complaints. When something does sound wrong, you reach an engineer in Greensboro who can pull the call and read the numbers with you. That accountability is why organizations choose us, and it has been the standard through our 25-plus years as a trusted communications partner for businesses, schools, and government across the Carolinas and Virginia. See the full picture at Carolina Digital Phone.
Frequently asked questions
How much internet speed do I need for VoIP?
Plan about 100 kbps per simultaneous call, in each direction, with headroom. Ten concurrent calls need roughly 1 Mbps up and down. For most businesses the download side is never the problem; check the upload side, and check it during your busiest hour.
Is Wi-Fi good enough for VoIP phones?
Desk phones should always be wired. Softphones and mobile apps work well on Wi-Fi when the wireless network is business-grade with proper coverage. The combo router-and-Wi-Fi box from the internet company, serving a whole office from one corner, is where wireless voice goes to struggle.
What is jitter in simple terms?
Voice packets should arrive like a steady drumbeat. Jitter is when the beat gets uneven, some packets early, some late. The phone can smooth a little of it, but past about 30 milliseconds of variation you hear choppiness and missing syllables.
Why do calls sound fine at 8 a.m. but rough at 10?
Because quality problems are congestion problems. At 10 a.m. your upload lane is sharing space with backups, video meetings, and file syncs. QoS on the router and enough upload headroom fix this pattern in most offices.
Will VoIP slow down the rest of my internet?
Not meaningfully. Voice is light: even a busy office's calls use a small fraction of a modern connection. The relationship runs the other way, since heavy data traffic can degrade voice, which is exactly what QoS prioritization exists to prevent.
My speed test looks great. Why are calls still choppy?
Speed tests measure capacity for a few seconds; voice cares about consistency over hours. A connection can score high on megabits while carrying jitter or a steady trickle of packet loss. Run a VoIP-specific test at your busiest hour and read the latency, jitter, and loss numbers instead of the speed number.
Get your network's real numbers
We will test latency, jitter, and packet loss on your actual connection at your actual busy hour, then tell you plainly what is yours to fix, what is ours to carry, and what it would take to make every call sound right.
Request a Network ReviewOr call us directly: (336) 544-4000