Article

Getting Business VoIP Right First Time

·By Mathew Chewing

VoIP fails for network reasons, not phone reasons. Here is what to get right before you port a number — bandwidth, QoS, power, and the NBN outage nobody plans for.

7 VoIP Setup Tips for a More Productive Office

Nearly every complaint about a VoIP system is actually a complaint about a network. The handsets are rarely the problem. The problem is that a phone call is the least forgiving thing a small office network will ever carry, and most networks were never configured with that in mind.

A file download does not care about a 200-millisecond hiccup. It just arrives fractionally later. A voice call does — the audio for that moment is simply gone, and the person on the other end hears a dropout and loses confidence in your business.

1. Work out the bandwidth honestly

The good news is that voice needs very little. A single call on the usual codec consumes roughly 85 to 100 kbps in each direction once packet overhead is counted. Ten simultaneous calls is about 1 Mbps up and down.

Almost any NBN connection has that. The number that actually matters is upload, which is where cheaper plans and older technologies fall short, and where everyone forgets that video calls, cloud backup and file syncing are competing for the same capacity.

Check the upload speed, subtract what your backup and sync tools consume during business hours, then see whether the remainder covers your peak call volume with room to spare. If your backup runs at 9am, that is the moment your calls will break.

2. Configure QoS, or accept the dropouts

This is the single most important setting and the one most commonly skipped. Quality of Service tells the router that voice packets go first when the link is congested.

Without it, a staff member uploading a large file gets exactly the same priority as a call with a client, and the call is the one that audibly suffers. With it, the upload slows imperceptibly and the call stays clean.

Most business routers support QoS. Most consumer routers either do not, or implement it badly — which is one of several reasons a business phone system should not be running through the modem the ISP posted out for free.

3. Put the phones on their own VLAN

Separating voice traffic onto its own VLAN is standard practice for good reasons: it makes QoS far easier to apply reliably, it keeps broadcast traffic from the data network away from the handsets, and it means a compromised PC is not sitting on the same flat network as your phone system.

It also makes troubleshooting dramatically simpler, because voice problems can be isolated from general network problems instead of the two being tangled together.

4. Sort out power before you need it

Desk phones are normally powered over the network cable using PoE, which is neat until you count the budget. A switch advertising PoE has a total power figure, and twenty-four handsets plus a couple of access points can exceed it. When that happens, ports shut off in an order nobody chose.

The more important question is what happens in a blackout. An old analogue line kept working because the exchange supplied power. VoIP does not. No power means no switch, no router, and no phones.

A UPS on the router, the switch and the NBN equipment keeps the phones alive for the length of a typical outage. For a business where calls are revenue, that is inexpensive insurance — and it needs to be decided before the first storm, not after.

5. Have a plan for when the internet goes down

Every VoIP system needs an answer to this, because internet connections do fail. The usual options:

  • Automatic failover to mobile. Calls divert to nominated mobiles when the system cannot be reached. Simple, cheap, effective.
  • A 4G or 5G backup service on the router, so the connection fails over and calls continue without anyone noticing.
  • A softphone app on staff mobiles, so people keep their extensions over mobile data.

Whichever you choose, test it deliberately. Unplug the connection during a quiet hour and confirm the calls actually land where you expect. A failover nobody has tested is a theory.

6. Design the call flow before you buy anything

The technical setup is usually easier than the human one. Decide in advance what happens to a call at 12:30pm when the person who normally answers is at lunch, and at 5:15pm when everyone has gone.

Map it out: who rings first, how long before it moves on, where it goes after hours, what the voicemail says, and who is responsible for checking it. Keep menus shallow — two options at the top level is plenty, and callers dislike anything deeper.

The most common failure in small-business phone systems is not a dropout. It is a call that rings out at 4:55pm because nobody defined the after-hours rule.

7. Handle number porting carefully

Your existing numbers are a business asset, and porting them is the part of a migration with the most scope for pain. Two rules save most of it.

First, do not cancel the old service. Port the number away, and let the port close the old service — cancelling first can release the number permanently, and getting it back ranges from difficult to impossible.

Second, allow real time. Porting can take days to weeks depending on the carrier and the service type, so run both systems in parallel over the changeover rather than scheduling a hard cut on a Monday morning.

While you are at it, update the number everywhere it appears — Google Business Profile, your website, invoices, email signatures, directories. A perfect phone system is not much use if the number on the first search result is the old one.

What good looks like

A well-implemented system is one nobody thinks about: calls are clear, they reach the right person, they behave sensibly after hours, and an internet outage is an inconvenience rather than a day of lost business.

Getting there is mostly network work, which is why our cloud PBX and VoIP service is scoped alongside business internet rather than sold as a box of handsets.

Local IT and cyber security support across NSW

Chewing IT runs managed IT and cyber security for small and mid-sized businesses from our Wyong and Hornsby offices, covering the Central Coast, Newcastle, Lake Macquarie and Hornsby.

Thinking about moving off your old phone system? Ask us to check the network first — that is where the call quality is decided.

Want this handled for you?

Chewing IT looks after IT, cloud and cyber security for businesses across the Central Coast, Newcastle and Sydney. Free, no-pressure consultation — no contracts, no jargon.