Is Your Internet Ready for VOIP? A Readiness Check

WordPress category: blog

Readiness

Internet speed alone does not determine whether a business is ready for VoIP.

Calls also depend on:

  • Available upload and download capacity
  • Latency, jitter, and packet loss
  • Network congestion and traffic prioritization
  • Firewall and Wi-Fi configuration
  • Power and internet failover

A connection may pass a speed test and still produce clipped audio, delays, or dropped calls during busy periods.

A readiness check should measure the network under realistic conditions, then verify the path from each phone to the voice provider.

1. Estimate bandwidth per call

Start with the maximum number of calls expected at the same time.

Do not use the total number of employees as the call count. Estimate concurrent calls during the busiest period, including conference rooms, reception, remote workers, and call queues.

Bandwidth varies by codec and network overhead. As a practical planning estimate, reserve about 100 Kbps per active call in each direction. This provides a usable starting point for many common business VoIP configurations. The actual figure depends on the provider, codec, packetization, and network overhead.

For example:

Simultaneous callsApproximate upload capacity to reserveApproximate download capacity to reserve
5500 Kbps500 Kbps
101 Mbps1 Mbps
202 Mbps2 Mbps

These figures cover voice traffic only. They do not include file transfers, cloud applications, video meetings, software updates, backups, or other network use.

Cisco’s codec calculations show why the codec matters. A G.711 call uses substantially more bandwidth than compressed codecs such as G.729 once packet overhead is included. Cisco lists approximately 87.2 Kbps per G.711 call and 31.2 Kbps per G.729 call over Ethernet, per direction. Actual requirements may differ based on configuration.

Use the codec and settings specified by the VoIP provider. Do not size a network based only on a codec’s payload rate.

Planning formula

Peak concurrent calls × estimated bandwidth per call = voice capacity needed in each direction

Then account for other peak network traffic and leave capacity for growth. Avoid planning to run the internet connection near full utilization. When the link becomes congested, voice packets compete with other traffic.

See Cisco’s voice bandwidth calculations.

VoIP calls represented as data streams with spare network capacity for business traffic

2. Check quality, not just speed

Voice traffic is sensitive to delay and packet loss. Record these measures during busy periods, not only when the office is quiet.

  • Latency: Delay between speaking and hearing the other person. High latency can cause pauses and people talking over each other.
  • Jitter: Variation in packet arrival time. High jitter can cause uneven audio or missing syllables.
  • Packet loss: Voice packets that do not arrive. Loss can make speech sound clipped, broken, or unintelligible.

Use the VoIP provider’s stated requirements as the acceptance criteria. As a practical target, aim for one-way latency below 100 milliseconds, jitter below roughly 20–30 milliseconds, and packet loss below 1 percent. Lower loss is preferable. The FCC’s broadband research identifies packet loss as a significant factor for interactive services, including VoIP.

Run repeated tests to the provider or service region where calls will be hosted. Capture upload and download performance, latency, jitter, and loss at multiple times of day. A quick quality test is a simple first step.

A single speed test does not measure all of these factors. A connection can show high throughput while still suffering from congestion, unstable routing, or bufferbloat.

Review the FCC’s broadband measurement report.

3. Confirm QoS across the network

Quality of Service, or QoS, assigns priority to selected traffic when network links are busy.

For VoIP, voice media should be prioritized over activities such as large file transfers, backups, guest Wi-Fi, and software downloads. QoS does not add bandwidth. It helps manage traffic when capacity is constrained.

A working configuration requires consistency across the full path:

  • IP phones or softphone devices
  • Switches and wireless access points
  • Router and firewall
  • WAN links between locations
  • Internet edge and provider settings, where supported

Check that voice traffic is marked and placed in the intended priority queue. Confirm that those markings are preserved through network equipment. A configuration on one router alone may not help if the rest of the path ignores or changes the markings.

For wireless phones, assess coverage, channel use, roaming, and interference. A strong signal does not guarantee a stable voice connection when the access point is congested.

Microsoft’s QoS guidance also emphasizes consistent configuration across network components. For Microsoft Teams, use its network planning guidance and service-specific requirements rather than assuming generic VoIP settings are sufficient.

Microsoft: Implement QoS in Teams
Microsoft: Prepare your network for Teams

Business network showing prioritized voice traffic through a router, switch, Wi-Fi access point, and cloud service

4. Plan for internet and power failures

Cloud VoIP depends on an internet connection and powered network equipment. A backup internet circuit can reduce downtime, but only if the failover path is configured and tested.

Check:

  • Whether the secondary connection uses a separate provider or access path
  • Whether the router or firewall can switch automatically
  • Whether the phone system reconnects after the switch
  • What happens to active calls during failover
  • How inbound calls are handled if the office connection is unavailable
  • Whether outbound and emergency calling still work
  • Whether the modem, router, firewall, switches, and access points have battery backup

A secondary circuit that shares the same local infrastructure may not protect against every outage. Ask the providers what parts of the path are shared.

Failover may interrupt calls already in progress. Confirm how the VoIP provider handles registration, call forwarding, and inbound call routing when the primary circuit is down. Test the process under controlled conditions and document the recovery time.

VoIP equipment also needs power. A UPS should support the network equipment that carries calls for the expected outage window. If the phone system is on-premises, include its server and related hardware. Review the FCC guidance on VoIP and 911 service, including the need to maintain access to emergency calling during an outage.

Primary and backup internet paths keeping business phones connected to cloud VoIP during a circuit outage

5. Complete a network readiness assessment

Before switching, assess the complete network path. Include wired and wireless devices, remote users, branch offices, and any on-premises phone equipment.

A readiness assessment should cover:

  1. Call demand
    Estimate peak simultaneous calls and identify where calls will be made from.

  2. Capacity
    Compare available upload and download capacity with projected voice use and other peak traffic.

  3. Performance
    Measure latency, jitter, and packet loss during business hours and periods of high network use.

  4. QoS
    Check markings, queues, and policy consistency across endpoints, switches, Wi-Fi, routers, and firewalls.

  5. Network path
    Review DNS, NAT, firewall rules, provider requirements, and any proxy or inspection settings that could affect voice traffic.

  6. Wireless and cabling
    Check Wi-Fi coverage and congestion. Confirm that wired phones and network equipment use suitable cabling and switch ports.

  7. Resilience
    Test secondary internet, UPS runtime, call forwarding, and provider recovery procedures.

  8. Emergency calling
    Confirm emergency address records and location details for each relevant phone or user configuration.

X-Tek provides network design, equipment, cabling, and network maintenance services. We can assess existing infrastructure and identify changes needed before a VoIP deployment. See X-Tek business services and our related guide, Do You Really Need a VoIP Phone System?.

Before switching

A network is ready when it supports expected call volume with room for normal business traffic, maintains acceptable call quality under peak load, prioritizes voice consistently, and has tested plans for power and connectivity outages.

Complete the assessment before porting numbers or replacing the existing phone system. Resolve capacity, QoS, Wi-Fi, or failover issues first. Then retest with the intended phones and provider configuration.

Contact Information
Business Solutions Information Request:
https://xtekit.com/business-solutions-information-request/
815-516-8075