Is Your Internet Ready for VoIP? A Plain-English Bandwidth and QoS Guide

Businesses switch to VoIP phone systems for obvious reasons: lower monthly costs, numbers that follow people instead of desks, and features that a traditional PBX could never offer. What gets less attention is the one thing the whole decision rests on. The internet connection.

VoIP turns every phone call into a stream of data competing with everything else on your network. File downloads, cloud backups, video meetings, someone streaming a training video in the break room. When the connection handles that competition well, calls sound better than the old phone line ever did. When it doesn’t, you get the audio quality problems that make people say VoIP is unreliable, even though the phone system was never the problem.

The good news is that you don’t need a networking certification to figure out whether your connection is ready. You need to understand four numbers, run one simple calculation, and know what to ask your provider. This guide covers all three.

The four numbers that decide your call quality

Bandwidth

Bandwidth is the total capacity of your connection, measured in megabits per second (Mbps). Think of it as the width of a pipe. VoIP calls don’t need much per call, typically between 30 and 100 kbps in each direction depending on the codec, which is the compression method the system uses to squeeze your voice into data packets.

That small per-call number misleads people. “My connection has 100 Mbps and each call needs 0.1, so I can run a thousand calls.” No. That bandwidth is shared with everything else, and the upload side is where most businesses get caught.

Here’s the detail that matters: most business internet plans are asymmetric, meaning the download speed is much larger than the upload speed. A “100/20” plan gives you 100 Mbps down but only 20 Mbps up. VoIP calls are conversations, so they use upload bandwidth too, and that smaller upload number is your real ceiling. A company running 15 simultaneous calls, daily cloud backups, and video meetings on a 20 Mbps upload link can saturate it without trying.

Latency

Latency is the time it takes for a packet of your voice to reach the other end, measured in milliseconds. Conversations feel natural when latency stays under about 150 ms one way. Past that, people start talking over each other, and past 300 ms it feels like a bad international call from decades ago.

Distance matters here. A call routed to a server across the country or overseas picks up latency at every hop. That’s one reason choosing a provider with a nearby point of presence, or using a provider whose infrastructure is reasonably close to your office, makes a measurable difference.

Jitter

Jitter is variation in latency. Your voice packets don’t all travel at the same speed. Some arrive quickly, some lag behind. If the variation is small, the phone system buffers it and you hear nothing. If it’s large, packets arrive out of order or too late to use, and you get the robotic, garbled audio that makes callers ask you to repeat yourself.

Jitter is usually caused by congestion inside your own network, not by your internet plan itself. A router struggling with traffic from twenty devices will deliver voice packets late even on a fast connection.

Packet loss

Packet loss is exactly what it sounds like: some of your voice data never arrives. A little loss, under 1%, is inaudible because the system compensates. Between 1% and 2.5%, calls sound choppy. Above that, words drop out entirely.

Loss usually points to a saturated connection, failing hardware, or a Wi-Fi problem. Yes, Wi-Fi. A call over a congested wireless network routinely loses more packets than the same call over a cable, which is why desk phones and computers used for calls should be on Ethernet whenever possible.

The calculation you can run this afternoon

Here’s a practical way to size your needs without hiring a consultant.

Step one: count your concurrent calls, not your total phones. A 40-person company rarely has more than a third of staff on calls at once. Twelve concurrent calls is a reasonable planning number.

Step two: multiply concurrent calls by 100 kbps for a comfortable margin. Twelve calls is 1.2 Mbps in each direction. That’s the easy part.

Step three: add your other real-time traffic. Each video meeting participant needs roughly 3 to 4 Mbps up. If three people are on video calls while twelve people are on phone calls, you’re at around 13 Mbps of upload before anyone uploads a file.

Step four: compare against your upload speed, and leave headroom. If your calculation lands within about 20% of your upload capacity, you will have problems during busy moments. Congestion doesn’t announce itself politely; it shows up as the choppy call with your biggest client.

If the math is tight, you have three options: increase the upload speed on your plan, move voice to a dedicated connection or VLAN so it can’t be crowded out, or reduce competing traffic during call-heavy hours. Sometimes the cheapest fix is simply scheduling the 200 GB cloud backup for 2 a.m. instead of mid-morning.

QoS: the setting that fixes most problems before they start

Quality of Service, usually abbreviated QoS, is a router feature that gives voice traffic priority over everything else. When a voice packet and a file download hit the router at the same moment, QoS makes sure the voice packet goes first. The download arrives a fraction of a second later and nobody notices, while the call stays clear.

Most business-grade routers support QoS, but it’s frequently disabled or misconfigured. The setup involves telling the router two things: which traffic is voice, and how much bandwidth to reserve for it. Some routers do this automatically when they detect VoIP protocols. Others need a rule marking voice traffic as high priority.

A few practical notes. QoS only helps at the point of congestion. If your router is the bottleneck, it works well. If your internet plan itself is too small, no router setting will save you. Also, QoS can’t fix problems upstream at your ISP, which is why the bandwidth calculation and the router configuration are both necessary.

Test before you commit

Don’t guess. Run a few tests during your busiest hour, not at 9 p.m. when the network is idle.

Speed tests give you raw bandwidth, but for VoIP you want a test that reports latency, jitter, and loss specifically. Several free tools measure exactly these four numbers and score the result for voice quality. Run the test multiple times across a few days, because a single good result proves nothing and a single bad result might have been a blip.

Also test from a wired connection. If the wired test is clean but calls still sound bad over Wi-Fi, your problem is the wireless network, and the fix is access points and cabling, not a bigger internet plan.

Questions worth asking before you switch

When you talk to providers, ask what upload speed they recommend for your expected call volume, and whether they offer a network assessment before installation. Ask whether their service works on a dedicated voice connection or a shared one. Ask what happens to your calls if your primary internet fails, because a good answer involves automatic failover to mobile apps or a backup circuit, and a vague answer is a warning sign.

None of this is complicated, but all of it is easier to handle before migration day than during it. Businesses that check these numbers up front tend to wonder why they kept paying for phone lines so long. Businesses that skip the check tend to spend their first month apologizing to callers. The difference is usually an hour of testing and one honest look at the upload column of your internet bill.