You’re evaluating VoIP providers, comparing features and pricing, and ready to sign a contract. But there’s a question that matters more than which provider you choose: can your network actually handle VoIP?
VoIP turns voice into data packets and sends them over your internet connection in real time. If your network can’t deliver those packets consistently—without delay, without gaps, without congestion—every call will suffer regardless of how good the VoIP service is.
Here’s how to test your network systematically and fix what needs fixing before you deploy.
VoIP is fundamentally different from other internet activity. Email tolerates delays. Video streaming buffers ahead. File downloads can pause and resume. Voice communication does none of these—it requires continuous, real-time data flow in both directions simultaneously.
When a network isn’t ready for VoIP:
Every one of these problems is preventable with proper testing and configuration.
Standard speed tests measure peak download speed—useful for streaming, but not for VoIP. You need a test that measures all four metrics that determine call quality:
| Metric | What It Measures | VoIP Requirement |
|---|---|---|
| Bandwidth | Upload and download capacity | 100 Kbps per concurrent call, each direction |
| Latency | Round-trip delay | Under 150ms one-way |
| Jitter | Variation in packet timing | Under 30ms |
| Packet loss | Packets that don’t arrive | Under 1% |
Run the test during peak business hours—mid-morning and early afternoon when your network is under real load. A test at 7 AM when the office is empty tells you nothing about 10 AM performance.
Test both upload and download. VoIP uses them equally. Cable internet plans often deliver upload speeds 10-20x slower than download, and upload is where VoIP bottlenecks happen.
Calculate your needs: maximum concurrent calls × 100 Kbps, plus 30% headroom. Ten simultaneous calls need at least 1.3 Mbps of dedicated upload bandwidth—on top of everything else your network handles.
Bandwidth alone doesn’t guarantee VoIP quality. Your network equipment and settings determine whether voice packets reach their destination cleanly.
Verify that your router allows SIP traffic (ports 5060/5061) and RTP traffic (your provider’s specified port range). These protocols handle call setup and voice transmission respectively.
Disable SIP ALG (Application Layer Gateway) on your router. Despite being designed to help VoIP, SIP ALG frequently interferes with call connections and causes one-way audio or dropped calls. Most VoIP providers recommend turning it off.
Check that your firewall isn’t blocking or throttling VoIP ports. A firewall that silently drops SIP packets causes calls to fail without any obvious error message—making it one of the hardest problems to diagnose without testing.
Ethernet cables deliver consistent, low-latency connections. Wi-Fi introduces variable delay and is susceptible to interference from walls, competing networks, and other devices. For any device that will make VoIP calls, plan for a wired connection.
If your team uses VPN connections, test VoIP quality through the VPN. VPNs add encryption overhead that increases latency. Some VPN configurations route VoIP traffic through distant servers, adding unnecessary delay.
QoS is the most impactful configuration change for VoIP quality. It tells your router to prioritize voice packets over everything else—file downloads, cloud backups, web browsing, video streaming.
Without QoS, your router treats a phone call the same as a software update download. When both compete for bandwidth during peak hours, neither gets priority and call quality suffers.
How to configure QoS:
Test it: Start a VoIP call, then begin a large file download. If audio stays clear, QoS is working. If the call degrades, adjust your QoS rules.
Business telephone services that include onboarding support can help configure QoS correctly during setup.
After configuration changes, re-test to confirm improvements.
If 15 people might be on calls simultaneously, test with 15 concurrent connections while the rest of the office uses the network normally. A test with one call on an empty network doesn’t reveal congestion problems.
Run tests mid-morning, after lunch, and mid-afternoon. If results vary significantly, you have time-dependent congestion—either internal (scheduled backups, team video calls) or ISP-side (shared bandwidth peaking during business hours).
Place actual calls between extensions and to external numbers. Listen for:
Technical metrics confirm the numbers. Test calls confirm the experience.
If testing reveals problems, fix the specific issue rather than replacing everything:
Insufficient bandwidth: Upgrade your internet plan, particularly upload speed. Business internet services with symmetrical speeds eliminate the upload bottleneck that causes most VoIP bandwidth problems.
High latency: Check if the issue is internal (old router, excessive network hops) or ISP-side (routing inefficiency, distance). Internal latency is fixable with hardware upgrades. ISP latency may require a provider change or connection type upgrade to fiber.
Jitter problems: Usually caused by network congestion or Wi-Fi instability. QoS configuration and wired connections resolve most jitter issues.
Packet loss: Could be a damaged cable, failing network equipment, or ISP infrastructure problems. Check physical connections first, then escalate to your ISP with test data.
Firewall blocking: Open the required ports for SIP and RTP traffic. Verify SIP ALG is disabled.
Network conditions change. New employees add devices, bandwidth usage grows, ISP performance fluctuates, and firmware updates sometimes reset configurations. What passed testing at deployment can fail six months later.
Monitor regularly:
1stConnect includes monitoring capabilities that track communication quality across your network, catching issues before they become complaints.
A basic check (speed test, latency measurement, configuration review) takes about an hour. A thorough assessment including stress testing, multi-time-of-day measurements, and hardware audit takes 2-4 hours. The investment prevents weeks of troubleshooting after deployment.
Plan for 100 Kbps per concurrent call in each direction, plus 30% headroom, plus bandwidth for all other business activities. For a 20-person office where 10 people might call simultaneously, you need at least 1.3 Mbps dedicated upload for VoIP—plus adequate bandwidth for email, cloud apps, and web browsing.
Consumer routers often lack granular QoS controls, VLAN support, and the processing power to handle business VoIP loads. If your router doesn’t support QoS for SIP/RTP traffic specifically, upgrade to a business-grade router before deploying VoIP.
For offices with more than 15-20 people, yes. A dedicated VLAN isolates voice traffic from data traffic, preventing large file transfers or cloud backups from affecting call quality. For smaller offices, QoS on a single network usually provides adequate separation.
The problem may be outside your network—at your ISP or VoIP provider. Run a traceroute to your provider’s servers to identify where latency or packet loss occurs. If the issue is at your ISP’s hops, contact them with the data. If it’s at the provider’s end, contact their support.
Ready to confirm your network can handle VoIP? Start with business internet built for real-time voice traffic, deploy business telephone services with confidence, and monitor everything with 1stConnect.