
Industry
Making sense of VoIP systems: live or die on the network path
VoIP systems live or die on the network path. What makes a call sound bad, hosted versus on your premises, and the three things to settle in writing before moving.
The phone system used to be a cabinet in a cupboard with wires to every desk. It is now a piece of software somewhere, a set of devices that talk to it, and the network in between. Two of those three are yours to look after, and the middle one is where nearly all the trouble lives.
What to take away
- Call quality is a property of the network path, not of the handset or the provider. Delay, variation in delay, and lost packets decide it, and they are all yours to fix inside the building.
- Settle three things in writing before movingwhat still rings in a power cut, whether you can take your numbers with you when you leave, and how emergency calls are handled.
- Move in stages. Pilot a team, run alongside the old service, and port the numbers last.
The three parts, and how each one fails
The endpoints. Desk phones, an app on a computer, an app on a mobile. A
The VoIP call path
- Handset to switch
- Switch to router
- Router to connection
- Connection to provider network
- Provider network to callee
The service. Either hosted by the provider, on a platform such as RingCentral, Zoom Phone or Microsoft Teams Phone, or a server on your premises running an IP PBX such as Asterisk or FreePBX. A failure here affects everyone at once, which is why the choice between the two is mostly about who you want to be responsible when it happens.
The path. Handset to switch, switch to your router, router to the connection, connection to the provider's network, and on to whoever you are calling. This is where poor quality comes from, and it is the part most contracts leave in your hands. The connection at the end of that chain is a decision of its own: fiber internet sends about as fast as it receives, which is the direction calls need.
Why a call sounds bad while the web works fine
A web page arrives whenever it arrives. A voice call has to arrive in order,
Fixes for poor call quality
- Wire phones and call computers
- Prioritize voice traffic on switch and router
- Check upload direction of connection
- Make sure router is not the bottleneck
- Test real calls at busiest hour
Web page vs voice call
Web page
- Arrival
- Whenever
- Order
- Any order
- Continuity
- Not needed
- Direction
- One way
Voice call
- Arrival
- On time
- Order
- In order
- Continuity
- Continuous
- Direction
- Both ways
on time, continuously, in both directions. Three things break that:
- Delay.Too much and people talk over each other. Voice engineering works to a one-way delay budget, and the ITU-T G.114 recommendation is the standard the industry plans against.
- Variation in delay.Packets arriving at uneven intervals, which the phone tries to hide with a buffer and fails when the variation gets large. This is the usual cause of choppy audio.
- Loss.Missing packets are gaps in the sound. A small percentage is audible. Ask the provider for the delay, jitter and loss targets its network is built to, and hold your own measurements against them.
None of these is measured by a speed test, and none improves when you buy a bigger connection. What does help:
- Wire the phones and computers used for calls. Wireless adds variation.
- Configure the switch and router for voice priority, using a method such as QoS with DSCP tagging — the voice class is EF, Expedited Forwarding, the standard marker for voice — so a large upload does not starve calls.
- Check the upload direction of your connection specifically. Calls send as much as they receive, and most connections are much narrower upward.
- Make sure the router is not the bottleneck. Cheap routers fall over under many simultaneous small flows long before they run out of throughput.
- Make real calls at your busiest hour before committing. Business internet covers what to look for in the connection underneath.
If calls are fine in the morning and poor mid-afternoon, the path is congested at that hour and prioritization inside the building is the first thing to fix.
Hosted or on your premises
A hosted service puts the switch in the provider's hands. You get a web
Hosted vs on-premises
Hosted
- Updates
- Provider
- Backups
- Provider
- Capacity
- Provider
- Security
- Provider
- Internal calls
- Leave building
- Connection matters
- More
On premises
- Updates
- You
- Backups
- You
- Capacity
- You
- Security
- You
- Internal calls
- Stay inside
- Connection matters
- Less
A server on your premises keeps internal calls inside the building. You are in charge of everything else: patching, backups, power, and reachability from outside for remote staff. That brings a security job with it. Some businesses have the people for that. Most do not.
There is no wrong answer. There is a wrong reason: choosing the on-premises option to save money, then budgeting nobody's time to run it.
Three things to settle before you move
Three things decide whether a move goes quietly: what still rings when the power goes, whether the numbers can leave with you, and how emergency calls are handled. Settle all three in writing before you sign.
What still rings when the power goes
An internet-based phone needs power at the desk, power at the switch, power
Settle before you move
- What rings when power goes
- Where calls go when building is dark
- Whether you can take numbers with you
- How emergency calls are handled
- Decide what a battery unit will cover and for how long. Usually the router and the switch; rarely every desk.
- Decide where calls go when the building is dark. Typically to mobiles, configured in the routing so that it happens without anyone logging in.
- Remember the street cabinet or the fiber equipment might be dark too. A cellular fallback is independent of that, and 5G business internet covers how to run one as a second path.
Whether you can take your numbers with you
Moving numbers in is the sales conversation. Moving them out is the one to have before you sign. In the United States, the FCC's porting rules at 47 CFR 52.35 require a simple port — a number moving on its own, with the account details matching — to be finished within one business day of a valid request, while complex ports covering several numbers or services take longer. So ask which of your numbers would qualify as simple, what porting them away at the end of the term involves, and what it costs in the contract's own words. A provider who makes leaving hard is telling you something.
How emergency calls are handled
On a traditional line the address of a call was the address of the wire. On an internet-based service the phone can be anywhere, and the address the emergency service sees is whatever the provider holds for it. In the United States, the FCC's rules for interconnected VoIP sit in 47 CFR Part 9: the provider has to obtain a registered location for each line, pass it to the 911 network, and report significant outages under the FCC's disruption-reporting rules in 47 CFR Part 4. The FCC's consumer guide on VoIP and 911 sets out the practical concerns for customers.
Outside the United States, ask your national regulator what it requires for emergency call routing, address updates and outage reporting on internet-based phone services.
Whatever your country, confirm with the provider, in writing. Ask how emergency calls are routed on their service, what address is passed, and how it is updated when someone works from home or another site.
Ask what happens when the connection or power is down. Then tell your staff, because the honest answer in many setups is that a mobile is the better phone to reach for in an emergency.
Security is the fourth thing worth settling. NIST SP 800-58, Security Considerations for Voice Over IP Systems, is the federal reference for voice over IP systems. Voice on a data network inherits that network's problems and adds a billing relationship on top. The account that can place calls needs limits as well as a password.
Rolling it out
Rollout order
- Pilot one team alongside old system
- Run both through busiest days
- Fix path problems the pilot surfaces
- Extend to everyone alongside old service
- Port numbers last
- Keep old service until port tested
A port runs through the account record rather than the phone system. The account holder signs a letter of authorization (LOA) naming the numbers and the receiving provider, and business phone numbers sets out who has to authorize one. The order matters because porting is the slowest step and the hardest to reverse.
Doing it first, to save a month of paying twice, is how businesses end up with a number that rings a system that is not ready.
What to keep on file
Three records make every future problem shorter:
Records to keep on file
- Routing configuration export, refreshed after changes
- Provider written answers on porting and emergency calls
- Pilot measurements as a quality baseline
- An export of the routing configuration, refreshed after any change. It is what lets the system be rebuilt somewhere else.
- The provider's written answers on porting and on emergency calls, kept with the contract rather than in somebody's mailbox.
- The measurements from your pilot, so a later complaint about call quality has a baseline to argue against.
Common questions
Do I need a special connection for it?
Not a special one, a suitable one. Stable, with adequate upload, low variation and a router that can prioritize. A second connection that fails independently, such as fixed wireless, matters more for phones than for almost anything else because a phone outage is visible to customers immediately.
Can staff use their own mobiles?
Usually, through an app that presents the business number. The number they show when calling out and the number the business keeps when they leave are the two things to configure and check.
How many simultaneous calls can I make?
That is set by your plan and by the path. As a typical figure, a call uses roughly 100 kbps in each direction once codec overhead is counted. Ask the provider for their per-call network requirement and hold it against the upload capacity you actually measured at the busy hour.
What if the provider goes out of business?
Your numbers are the exposure. Keep the account holder details correct and a current export of your routing configuration so it can be rebuilt elsewhere.
In this guide
- VoIP systems setup: cabling, priority, power, NATVoIP systems setup is network work, not phone work. Cabling, VLAN priority, PoE power and NAT decide call quality, and each one fails in a way you can hear.
- VoIP systems: the written trial that separates real contendersChoosing VoIP systems software works better as a written requirement and a scored trial than as a shortlist. Here is the requirement, scoring and exit clause.
- VoIP Systems Features for Small BusinessesVoIP systems features shape caller routing, reporting, compliance, and administration. See which settings affect callers and what to review before buying.
- VoIP Systems Security: Everyday Fraud DefensesVoIP systems security starts with limiting destinations, protecting credentials and monitoring call activity to reduce toll-fraud risk.
- VoIP systems migration: audit what the old system doesA VoIP systems migration starts with an audit: record extensions, queues, out-of-hours routing and non-phone devices, then use the list to test the pilot.







