Common VoIP Installation Mistakes and How to Avoid Them
The most common VoIP installation mistakes are testing the internet connection too late, ignoring Quality of Service, leaving SIP ALG switched on, cancelling old lines before numbers have ported, buying too few licences, and going live without a backup plan. None of them is difficult to avoid. Almost all of them come from rushing the preparation, and almost all of them show up as the same complaint on day one: "the phones don't work properly."
Here are the thirteen we see most often, what each one looks like when it goes wrong, and the quick fix.
1. Testing the internet connection at the wrong time
A speed test at 7.30am tells you very little. The connection that looks fine on a quiet morning can struggle at 11am when everyone is on email, cloud software and video calls.
How to avoid it: Test at your busiest time of day, and record upload as well as download. Voice travels both ways at once. Our guide to what internet speed you need for VoIP gives targets by office size, and VoIP bandwidth requirements shows how to work out the figure for your own peak calls.
2. Assuming a fast connection means good call quality
Speed and quality are different things. A 500 Mbps line can still produce choppy calls if a large upload swamps the router or the connection suffers from jitter.
How to avoid it: Look at stability, not just headline speed. Our explainer on VoIP jitter and latency covers what to measure. If you're deciding between connection types, FTTP vs a leased line and the full leased line guide help you choose.
3. Skipping Quality of Service (QoS)
Without QoS, your router treats a phone call exactly like a software update. When something big starts downloading, calls break up.
How to avoid it: Set up voice prioritisation on the router before go-live, then test with the office busy. Our blog guide to optimising QoS for your VoIP system walks through it. If calls already sound rough, see why VoIP calls break up.
4. Leaving SIP ALG switched on
SIP ALG is a router feature meant to help voice traffic. In practice it often rewrites call data incorrectly, which causes one-way audio, calls dropping after 30 seconds, and handsets that lose registration.
How to avoid it: Check the router settings and switch SIP ALG off unless your provider says otherwise. If you've already got a call where one person can't hear the other, our guide to fixing one-way audio on VoIP covers it step by step.
5. Cancelling the old lines too early
This one causes real downtime. If the old line is cancelled before your numbers have ported, the number can be lost or stuck in limbo, and customers hear nothing.
How to avoid it: Keep the old service running until the port has completed and you've tested inbound calls on the new system. Our guides on how long porting takes and what happens to your number when you switch provider show what to expect, and if a request bounces, read why number porting gets rejected. The blog post on transferring a PSTN number to VoIP covers the wider process.
6. Forgetting what else is on the phone line
Alarms, door entry systems, card machines, lift phones and fax lines often sit on the old analogue or ISDN service, and nobody remembers until they stop working.
How to avoid it: Walk the building and list every device that uses a phone line before you order. Our PSTN switch-off checklist includes a section for exactly this, and the PSTN switch-off checker helps you see where you stand.
7. Buying the wrong number of licences or channels
Too few and calls are blocked at busy times. Too many and you pay for capacity you never use. With some platforms the licence is tied to simultaneous calls rather than headcount, and that limit also affects how many extensions you can run.
How to avoid it: Work out your peak simultaneous calls, then add a buffer. Our guides on how many SIP trunks you need and how many handsets you can have on one VoIP system explain the maths. If you're choosing between packages, Gamma Horizon: which package suits my business breaks down the tiers.
8. Designing a call flow that frustrates callers
A greeting with seven options and three layers of menu loses callers. So does a queue that rings out to nowhere after hours.
How to avoid it: Keep the first menu to four options or fewer, make sure every route ends at a person or a voicemail, and test each path with a real call. Our guide to what an auto attendant is and the comparison of call queues vs hunt groups help you choose the right tool, and the blog on call routing, auto attendants and IVR goes deeper. Don't forget a professional greeting: see these voicemail greeting examples for businesses.
9. Having no plan for a power cut or internet outage
VoIP needs power and a connection. If either fails and there's no fallback, the phones go quiet and nobody can be reached.
How to avoid it: Put the router and switch on a small UPS, add a backup connection if calls matter to your revenue, and set up a mobile fallback. Our guides cover what happens in a power cut, what happens if your internet goes down and setting up a failover connection. The blog on VoIP and business continuity puts it in context.
10. Forgetting the emergency address
Your 999 location details need to match where people actually work. After an install or move, they're easy to leave out of date.
How to avoid it: Confirm the registered address with your provider before go-live, and again after any move. Read 999 calls on VoIP for the rules.
11. Poor handset, headset and cordless planning
Cheap headsets make a good system sound bad. DECT handsets that lose signal at the back of a warehouse or upstairs in a Victorian building cause constant complaints.
How to avoid it: Match the equipment to the job, and survey cordless coverage before buying. Our guides on DECT repeaters and softphone vs desk phone help, and the blog on desk phones for 3CX is a good starting point if you're comparing models.
12. Weak security on day one
Default passwords, SIP ports left open to the world and no restrictions on international dialling are an open door to toll fraud. A single weekend of fraudulent calls can run to thousands of pounds.
How to avoid it: Change every default credential, restrict access by country and by user, and keep firmware up to date. The blog on securing 3CX against SIP attacks and toll fraud is written for 3CX but the principles apply to any system, and phone system security and compliance features covers what to look for.
13. Going live without testing or training
Switching over on a busy Monday morning, with no test calls and no staff briefing, guarantees a stressful week. People don't know how to transfer, park or check voicemail, and small problems become big ones.
How to avoid it: Go live mid-week if you can, make test calls from every handset, and give staff a one-page cheat sheet. Our 3CX transfer guide and how to make and receive calls on 3CX are handy to share. If you record calls, make sure consent and retention are sorted first: see call recording consent in the UK and the blog on call recording compliance.
A quick pre-install checklist
- ☐ Speed test run at peak time, upload and download recorded
- ☐ Peak simultaneous calls worked out, with a buffer
- ☐ QoS configured and SIP ALG checked
- ☐ Every device on the old lines listed
- ☐ Old lines kept live until ports complete
- ☐ Call flow drawn out and tested
- ☐ UPS and backup connection planned
- ☐ Emergency address confirmed
- ☐ Security settings changed from defaults
- ☐ Test calls made and staff briefed
For the full network checklist, see how to prepare your network for a VoIP phone system install.
Does it make a difference who does the install?
A lot. A supplier who surveys the site, checks the line and configures the network up front removes most of the mistakes above before they happen. It's one reason local installers are worth considering if you're in Bournemouth, Poole or Christchurch, or on the Hampshire side around Southampton, Totton and Portsmouth. A visit costs less than a week of missed calls. Our case study on fixing poor connectivity with Gamma Horizon shows what a proper diagnosis can do, and if you're moving from an older system, the checklist for migrating from a legacy PBX to 3CX is worth reading. For the broader picture, see how to switch to VoIP.
Frequently asked questions
What is the most common VoIP installation mistake? Not checking the network properly beforehand. Most call quality complaints after a new install trace back to the internet connection, router settings or missing QoS, not the phone system itself.
How long does a VoIP installation take? The system itself can often be configured in a day or two. The slow parts are usually the broadband or leased line and any number porting, which can take weeks. Order those first.
Can I install VoIP myself? For a small team on a simple cloud system, often yes. For multiple sites, cordless handsets, call recording or number porting, professional help saves time and avoids the mistakes above.
What should I test before going live? Inbound and outbound calls from every handset, transfers, voicemail, every auto attendant option, out-of-hours routing and call quality while the office is busy.
Why does my new VoIP system have one-way audio or dropped calls? Usually SIP ALG, a firewall blocking voice traffic or a congested connection. Our guides on one-way audio and calls breaking up cover the fixes.
Is VoIP harder to install than a traditional phone system? Not harder, just different. The work shifts from running phone cabling to getting the network and internet connection right. Done properly, it's quicker and cheaper to install and far easier to change later.
What if I've already installed it and it isn't working properly? Start with the network: run a speed test at peak time, check QoS and SIP ALG, and look at your cabling. If you can't find it, a support check from your provider will usually spot the cause quickly.
Most installation problems are preventable with an hour of checking before go-live. Request a quote if you'd like T2K to survey your site and plan the install, or use our phone system finder to compare systems before you decide.
