Most VoIP problems that get blamed on the phones are really network problems. Choppy audio, one-way calls and dropped transfers almost always trace back to bandwidth, prioritization or a router setting. The good news: you can check all of it before the first phone comes out of the box.

1. Measure upload bandwidth, not just download
Every call sends audio in both directions, so your upload speed is usually the limit. Plan on roughly 90–100 kbps per call in each direction for the common G.711 codec once network overhead is included, or about 30–40 kbps with a compressed codec such as G.729.
- 10 simultaneous calls on G.711 ≈ 1 Mbps up and 1 Mbps down, set aside just for voice.
- Add headroom for video meetings, cloud backups and file uploads that run during the day.
- Run speed tests at busy times, not at 7 a.m. when the office is empty.
2. Check the numbers that matter more than speed
A fast connection can still sound bad. Voice quality depends on three measurements you can see in most speed-test and router tools:
- Latency: under 150 ms one way keeps conversations natural.
- Jitter: under 30 ms; higher values cause robotic or clipped audio.
- Packet loss: under 1%; even 2–3% is clearly audible.

3. Turn on QoS so voice goes first
Quality of Service tells your router and switches to send voice packets ahead of everything else. Mark voice traffic (SIP signaling and RTP audio) with DSCP values — commonly EF (46) for audio and CS3 (24) for signaling — and make sure the switch and router both honor those markings. If your router supports bandwidth shaping, cap the total upload slightly below what your line delivers so the router, not your provider, decides what waits.
4. Put phones on their own voice VLAN
A separate voice VLAN keeps phones away from broadcast traffic from PCs and printers, makes QoS easier to apply, and lets you hand phones their own DHCP scope. Many IP desk phones can learn the voice VLAN automatically through LLDP-MED, and DHCP option 66 can point them to the provisioning server so they configure themselves.
5. Budget PoE power before you buy switches
Power over Ethernet removes a power brick from every desk, but each switch has a total power budget. Add up the wattage of every phone (color-screen and expansion-module models draw more) and leave at least 20% spare. Cable runs should be Cat5e or better and under 100 meters. Testers and crimp tools in our tools & equipment section make it easy to verify runs before go-live.

6. Disable SIP ALG and check your firewall
Many consumer and small-business routers ship with “SIP ALG” turned on. It tries to help SIP traffic through NAT and often breaks it instead, causing one-way audio or calls that drop at 30 seconds. Turn it off unless your provider specifically asks for it, and allow the signaling and media ports your phone system or SIP trunk provider lists.
7. Plan for the day the internet goes down
- Set call forwarding to mobile numbers when phones are unreachable.
- Consider a second internet connection with automatic failover.
- Keep your router, switch and on-site FreePBX server on a UPS battery backup.
- Confirm each location’s E911 address is registered correctly.
A quick pre-switch checklist
- Upload bandwidth covers peak calls plus 30% headroom.
- Latency, jitter and packet loss tested at busy hours.
- QoS markings set and honored end to end.
- Voice VLAN and DHCP options configured.
- PoE budget calculated with 20% spare.
- SIP ALG off and firewall ports open.
- Failover and battery backup in place.
Want a second set of eyes? Tell us how many users and locations you have, and we will help you match phones, switches and SIP service to the network you already own.




