On this page
Before anyone asks us about price, they ask whether the internet at their building can actually carry phone calls. It is the right question. A hosted phone system puts your calls on the same connection as your email, your cloud accounting and whatever is streaming in the break room, and that connection decides what the calls sound like.
The good news is that VoIP is not hungry. It is fussy. It needs very little bandwidth, but it needs that bandwidth to arrive steadily — a 500 Mbps fibre line with congestion problems can sound worse than a 15 Mbps DSL line that behaves itself. Four numbers tell you where you stand, and you can measure all four in about thirty seconds.
Latency: how long a packet takes to get there
Latency is the travel time between your office and the phone system, normally reported as a round trip in milliseconds. It does not make audio choppy. It makes conversation awkward. At low latency you interrupt each other naturally, the way people do in a room; as it climbs you start talking over each other — the walkie-talkie effect. Microsoft classes an audio stream as poor quality once round-trip time passes 500 ms. The working limit for one-way delay comes from ITU-T Recommendation G.114, One-way transmission time; our readiness test targets under 150 ms and flags under 80 ms as excellent.
Jitter: whether packets arrive evenly
Jitter is the variation in those travel times. If packets leave evenly spaced and arrive bunched up and then late, the phone has to guess at what goes where.
This is the one people describe as robotic, underwater, or “like they’re in a tunnel”. It is also the symptom most likely to appear on a connection that looks fine on a speed test, because a speed test measures how much you can pull down, not whether the stream was smooth. A busy office network, a Wi-Fi handset at the far end of the building, or a cheap router inspecting every packet will all produce jitter on a line with bandwidth to spare. Microsoft’s poor-quality threshold is a 30 ms average, and so is ours.
Packet loss: whether packets arrive at all
Packet loss is the share of packets that never turn up. Voice gets no second chance at them — by the time a missing packet could be resent, the moment it belonged to has passed, so the phone fills the gap.
Scattered loss is close to inaudible. Loss arriving in bursts is what cuts out syllables and whole words. Microsoft classes a stream as poor once the loss rate exceeds 10%, but that is a floor, not a target: sustained loss of even a percent or two is worth chasing down. It is also the number that most often points at a physical fault — a failing modem, a water-damaged line, an overloaded tower, or a Wi-Fi link that should have been a cable.
Upload bandwidth: usually the real constraint
Bandwidth is the number everyone fixates on and the least interesting of the four. 3CX’s own arithmetic is simple: the G.711 codec carries 64 kbps of audio and network packaging adds a fixed 31.2 kbps of overhead, so about 95 kbps per call in each direction. Round it to 100 kbps, and eight people on the phone at once is under 1 Mbps each way. The catch is the word upload: most Northern Ontario plans are asymmetric, so a package advertising 100 Mbps down may give you 10 Mbps up, shared with every file sync and backup in the building. Upload is where capacity runs out.
| What we measure | Excellent | Target | Why it matters |
|---|---|---|---|
| Latency (round trip) | Under 80 ms | Under 150 ms | Awkward pauses, talking over each other |
| Jitter | Under 20 ms | Under 30 ms | Robotic, choppy audio |
| Packet loss | Near zero | As low as possible | Missing words and syllables |
| Upload / download | — | Over 0.5 / 1 Mbps | ~100 kbps per simultaneous call |
What Northern Ontario connections actually look like
Geography does the work here, and it varies by street, not by town. Fibre is the easy case: low latency, low jitter, symmetrical upload, and increasingly the default for commercial buildings in Thunder Bay. Cable and DSL usually pass, with asymmetry as the thing to watch — twelve phones on a 10 Mbps upload is fine on paper, and stops being fine when the nightly backup starts at 4 p.m. Fixed wireless needs measuring rather than assuming: it can be excellent, and it can also show jitter and loss that move with the weather and the tower load.
Satellite splits into two cases. Our test page notes that satellite typically measures 600–700 ms — the traditional geostationary picture, every packet travelling 36,000 km up and back. Low-earth-orbit services sit far below that, and we have sites running real phone traffic on them. We will not quote a figure for them, because the one that matters is what your building measures. On any satellite site, keep desk phones wired.
Run the test before you shop
The test is free, takes about thirty seconds and needs nothing installed: dvgvoip.com/voip-readiness-test/.
Run it from the building you are asking about, on the wired network if you have one, and during your busy hour rather than at 7 a.m. If you are connecting several sites — and multi-site is one of the main reasons businesses up here move to hosted — test each one. Results differ between a Thunder Bay office and a branch two hours up the highway.
If the result is good, you are done thinking about the network. Our pricing page lists Starter at $22 per user per month for teams of one to ten and Business at $19 per user per month for teams of eleven to fifty, month-to-month with no contract, plus a savings calculator if you would rather work from your current bill.
When a connection does not pass
A fail is not a verdict on your building. Most we see are fixed on site, not by buying a bigger plan:
- QoS on the router, so voice goes first when the line is busy. This settles more jitter complaints than any other single change.
- Wired handsets, because Wi-Fi is the most common source of jitter we find.
- A VoIP-aware router. The “SIP ALG” feature on many business routers quietly breaks call setup; a session border controller on site takes the router out of the conversation entirely.
- Rescheduling heavy traffic, since backups do not need business hours.
Send us your result or book a free assessment and we will tell you what your connection can carry — including if the answer is “not yet”. Call (807) 700-7111.
FAQ
How much internet speed do I need for VoIP?
Far less than most people expect. Each call uses roughly 100 kbps in each direction, so ten concurrent calls need about 1 Mbps up and down. Our test targets more than 1 Mbps download and more than 0.5 Mbps upload.
Why do my calls sound robotic when my speed test is fine?
That is almost always jitter, and a speed test does not measure it. Jitter is the variation in packet arrival times, and it comes from congestion, Wi-Fi, or a router inspecting every packet.
Can I run VoIP over satellite internet in Northern Ontario?
It depends which kind. Traditional geostationary satellite adds enough delay to make conversation difficult. Low-earth-orbit services are a different proposition and we have sites running on them, so measure yours.
What happens to my phones if the internet goes down?
Desk phones lose service until the connection returns. Calls to your numbers can be set to ring the 3CX app on staff mobiles or forward to a cell, so the business keeps answering.
Sources, verified 16 November 2026: DVGVoIP Network Readiness Test and Pricing; 3CX, Bandwidth Utilisation for VoIP Calls; Microsoft Learn, Use CQD to manage call and meeting quality; ITU-T Recommendation G.114. Not a contract; pricing is a guide.