What VoIP needs from a network
A single VoIP call uses surprisingly little bandwidth, typically less than a tenth of a megabit in each direction with common codecs. Even twenty simultaneous calls fit easily on a modest fibre connection. What voice cannot tolerate is delay and inconsistency. Latency is the time a packet of audio takes to travel, jitter is how much that time varies, and packet loss is audio that never arrives at all.
Email or a web page can wait an extra half second without anyone noticing. A conversation cannot. When latency climbs or packets go missing, people talk over each other, words drop out and calls sound robotic. Most VoIP problems are really network problems, so the network deserves attention before the phones arrive.
Test the connection under load
Run tests at busy times, not just when the office is empty. Many VoIP providers offer an online test that simulates calls and reports latency, jitter and packet loss. Run it while staff are working normally, during a large upload and while a cloud backup is running. If the numbers deteriorate sharply under load, calls will suffer in exactly those moments.
Pay particular attention to upload. Every call sends audio out of the office as well as receiving it, and a saturated upload from file syncing or backups is the classic cause of one-way audio problems, where the caller can hear you but you sound broken up to them. Scheduling backups and large syncs outside business hours removes much of that risk before you touch any settings.
Give voice priority
Quality of service, or QoS, tells the firewall and switches to send voice packets ahead of everything else. On the firewall, voice traffic to the phone provider can be given priority on the internet connection, and other traffic can be shaped so it never quite fills the line. On the switches, phones can be marked so their traffic jumps the queue internally.
QoS only helps where you control the traffic, which is inside your network and on the way out. Once packets leave the building, the provider's network takes over, which is why choosing a reliable internet service and a good VoIP provider matters as much as the settings in your office.
Put phones on their own VLAN
A dedicated voice VLAN keeps phones separate from computers and guests. That makes QoS simpler to apply, reduces the noise phones have to deal with and stops a problem on the staff network, such as a misbehaving device flooding traffic, from affecting calls. It also adds a layer of security, because phone systems are a target for toll fraud.
Most business desk phones have a built-in two-port switch, so a computer can plug into the phone and share one data outlet. The switch port carries both the voice VLAN and the staff VLAN, and the phone separates them. That keeps cabling simple at each desk. Check that the phones you choose support this and that the switch is configured to match.
Power and resilience
Desk phones are usually powered by PoE from the switch. Check the switch has enough ports and enough PoE budget for every handset plus your access points and cameras. Put the switch and firewall on a UPS, so phones keep working through short power cuts, which is important now that the copper landline that once worked during outages is being withdrawn.
Think about what happens if the internet goes down. A backup connection with automatic failover keeps calls flowing, and most hosted phone systems can divert calls to mobiles when office phones are unreachable. Agree that diversion plan with the provider and test it before you need it. Include the main number, any direct dial numbers and the after-hours message in that plan.
Wi-Fi calling and softphones
Many staff now take calls on a laptop app or a mobile softphone rather than a desk handset. Those calls rely on Wi-Fi, so coverage, roaming and congestion all matter. If people walk around while on calls, access points need to hand them over smoothly; otherwise calls drop when someone moves between rooms.
Headsets make a big difference too. A decent wired or business-grade wireless headset removes background noise and echo that people often blame on the network. Before go-live, ask a few staff to make test calls from their usual spots, including the far corners and meeting rooms, and fix any weak areas then.
In short
- VoIP needs little bandwidth but low latency, jitter and packet loss.
- Test call quality at busy times and during heavy uploads.
- Set QoS on the firewall and switches to prioritise voice.
- Use a voice VLAN and PoE switches on a UPS.
- Plan a backup connection and call diversion for outages.