Skip to content
BrightPBX

Network considerations for VoIP

Most networking hardware should work with little to no modifications over and above establishing internet service. Below are some general recommendations.

1. Make 64 kbps upload and download bandwidth available per phone, at all times

Section titled “1. Make 64 kbps upload and download bandwidth available per phone, at all times”

This is for HD audio — more may be needed for video.

Bandwidth management and/or QoS can help you ensure this at the router and switch levels. Alternately, some clients just purchase so much bandwidth that their clients can’t reasonably consume it. And others simply buy a completely separate internet connection just for VoIP use.

2. Ensure the phones aren’t affected by issues from the LAN

Section titled “2. Ensure the phones aren’t affected by issues from the LAN”

Problems such as ARP poisoning and broadcast storms can disrupt phones.

VLANs are highly effective for this and recommended whenever possible. Some clients also use fully separate switches for this, while others simply have good anti-virus, intrusion prevention and network monitoring on their network.

3. Have some methodology for checking packet loss and jitter over time

Section titled “3. Have some methodology for checking packet loss and jitter over time”

Solarwinds NPM and Ping Plotter can be great tools for this, as well as routers such as Meraki and Ubiquiti. Or just use simple traceroute, continuous pings, or MTR as needed.

4. Ensure your router is sized correctly to handle the load from the network

Section titled “4. Ensure your router is sized correctly to handle the load from the network”

How exactly you choose to do this is completely up to you. There are many ways to do so, more even than are listed here — and even more vendors you could potentially use.

5. Specific recommendations

Section titled “5. Specific recommendations”
  1. Look for and ensure the router/firewall does not have any SIP Helpers, SIP ALG, or SIP/VoIP “anything” enabled.
  2. Avoid SonicWalls made prior to 2015.
  3. If you use open-source router software, ensure the hardware you are using is supported by the project.
  4. Do not use residential routers in businesses, as they can easily be overwhelmed by the traffic.
Section titled “Related”