VoIP Bandwidth & Network Requirements

Each active VoIP call uses a small but consistent amount of bandwidth — typically around 80–100 Kbps in each direction (upload and download). While this may seem minor, it adds up quickly when multiple calls happen simultaneously.

What matters most isn't raw internet speed — it's consistency. A connection that delivers steady, uninterrupted throughput will always outperform a faster connection with fluctuations.

Three network metrics have a far greater impact on call quality than raw bandwidth:

Latency (Target: Under 150ms)

Latency is the time it takes for a data packet to travel from your phone to the other person's phone and back. Think of it as the delay between when you speak and when the other person hears you.

• Under 150ms — Calls feel natural and conversational
• 150–300ms — Noticeable delay, like a satellite phone call
• Over 300ms — Conversations become difficult with constant talking over each other

Jitter (Target: Under 30ms)

Jitter is the variation in latency over time. Even if your average latency is good, inconsistent delivery of voice packets causes choppy, robotic-sounding audio.

• Under 30ms — Smooth, clear audio
• 30–50ms — Occasional audio artifacts
• Over 50ms — Frequent choppy audio and garbled speech

Packet Loss (Target: 0%)

Packet loss occurs when data packets fail to reach their destination. Voice data is real-time — lost packets can't be resent in time, so they result in gaps in audio.

• 0% — Perfect audio quality
• 0.5–1% — Noticeable audio dropouts
• Over 1% — Severely degraded call quality

Before troubleshooting call quality issues, measure your network's actual performance:

Step 1: Use PingPlotter

PingPlotter is the recommended tool for measuring latency, jitter, and packet loss over time. It provides visual graphs that make it easy to identify problem areas in your network path.

• See: How to Use PingPlotter for VoIP Troubleshooting
• See: Reading PingPlotter Results

Step 2: Test During Peak Hours

Always run network tests during your busiest business hours — not evenings or weekends. Network conditions change dramatically based on usage, and you need to know how your connection performs when it matters most.

Step 3: Run Tests for at Least 30 Minutes

Short tests can miss intermittent issues. Run PingPlotter for at least 30 minutes during peak hours to capture a representative sample of your network performance.

Follow these best practices to ensure reliable VoIP performance:

1. Enable QoS (Quality of Service)

Configure your router to prioritize SIP and RTP traffic over other types of data. QoS ensures that voice packets are delivered first, even when your network is busy with file downloads, video streaming, or other traffic.

2. Use Wired Connections for Desk Phones

Wi-Fi introduces additional latency, jitter, and potential packet loss. Wherever possible, connect desk phones using Ethernet cables for the most reliable connection.

3. Consider a Dedicated Voice Circuit

If your business handles a high volume of simultaneous calls, consider setting up a dedicated internet circuit exclusively for voice traffic. This eliminates competition with other data and guarantees consistent bandwidth availability.

4. Separate Voice and Data VLANs

If a dedicated circuit isn't feasible, configure your network switch to place voice traffic on a separate VLAN. This provides logical separation and makes QoS policies more effective.

5. Monitor Continuously

Don't just test once and forget. Set up ongoing network monitoring to catch issues before they impact call quality. Many problems are intermittent and only appear during specific times of day.