VoIP bandwidth requirements depend on how many calls happen at the same time, not how many employees you have. A practical starting estimate is about 100 Kbps of upload and 100 Kbps of download capacity per simultaneous voice call. Use the team-size calculator below to estimate busy-hour demand, then run a 15-minute network test to check whether your connection can support calls reliably.
Key takeaways
- Plan for roughly 100 Kbps of upload and 100 Kbps of download capacity per simultaneous call as a starting estimate.
- Estimate busy-hour concurrency from actual call activity; employee count alone does not show how many calls overlap.
- Budget separately for video meetings, cloud apps, backups, and other traffic sharing the connection.
- Check latency, jitter, and packet loss as well as speed because a fast download result cannot guarantee clear calls.
- Test real calls from representative locations and devices before launch, then compare results with your phone provider’s guidance.
How much bandwidth does a VoIP call use?
A business VoIP call can be planned at about 100 Kbps in each direction: 100 Kbps upload and 100 Kbps download. This is a practical estimate, not a universal requirement, because actual usage changes with the codec, packetization, network overhead, and provider configuration. AT&T Business gives the same per-direction figure as a planning starting point.
A practical per-call estimate
For initial sizing, multiply simultaneous calls by 100 Kbps in each direction. For example, 10 concurrent calls need about 1,000 Kbps (1 Mbps) of upload capacity and 1,000 Kbps of download capacity for voice.
These are separate directional figures. A 10-call estimate is not 1 Mbps total split between upload and download: it is roughly 1 Mbps upstream and 1 Mbps downstream, before headroom and other network use.
Why codec and packet overhead change the number
A codec is the method used to encode and compress voice audio. Packetization is how much audio is put into each network packet before it is sent. Both affect bandwidth, as do transport headers and other network overhead.
For example, Cisco’s G.711 example with 20 ms speech packets calculates 87.2 Kbps in each direction, or 174.4 Kbps across both directions. That example shows why per-call figures depend on configuration; use your phone provider’s specifications when finalizing capacity.
Upload and download: plan for both directions
Your phone sends your voice to the other caller using upload capacity and receives their voice using download capacity. A connection with plenty of download speed but limited or congested upload can still deliver poor conversations. Check both directions, especially when employees make calls while sending files, backing up data, or joining video meetings.
VoIP bandwidth calculator by team size
Estimate voice bandwidth from simultaneous busy-hour calls, not from every employee being on the phone at once. The table uses an illustrative assumption that 25% of a team’s users are on voice calls at the same time, rounded up, and a planning rate of 100 Kbps in each direction per call.

| Team size | Assumed busy-hour concurrency | Simultaneous calls | Voice upload capacity | Voice download capacity |
|---|---|---|---|---|
| 10 | 25% | 3 | 300 Kbps | 300 Kbps |
| 20 | 25% | 5 | 500 Kbps | 500 Kbps |
| 50 | 25% | 13 | 1.3 Mbps | 1.3 Mbps |
| 100 | 25% | 25 | 2.5 Mbps | 2.5 Mbps |
| 200 | 25% | 50 | 5 Mbps | 5 Mbps |
These are voice-only estimates, not recommended total internet speeds. If your sales or support team makes frequent calls, change the concurrency assumption to match observed busy-hour overlap. For example, at 40% concurrency, a 50-person team would plan for 20 simultaneous calls, or about 2 Mbps each way.
Estimate concurrent calls, not total employees
Use call reports, a representative busy-hour observation, or a short pilot to find the highest normal number of overlapping calls. The formula is:
Team size × busy-hour concurrency rate = estimated simultaneous calls
Round up to a whole call, then multiply by your per-call rate for upload and download separately. A call center with scheduled shifts may have higher concurrency than a mixed office team, so use actual call patterns where available.
Add headroom for the rest of your network
Reserve extra capacity for video meetings, cloud software, file transfers, backups, and other users. The table does not prescribe one universal headroom percentage because non-voice traffic varies widely; compare your estimate with measured peak usage and your provider’s requirements.
If the connection is routinely near capacity, ask your ISP about a plan with enough upload as well as download capacity. For broader selection and setup considerations, see the VoIP phone system buyer’s guide.
What affects VoIP call quality besides bandwidth?
Bandwidth is the connection’s capacity; latency, jitter, and packet loss describe how reliably and promptly voice data arrives. A fast speed test cannot rule out congestion, uneven delivery, or missing packets, so check call quality metrics alongside upload and download speed.
Latency and conversational delay
Latency is the time it takes data to travel across the network. Excessive delay can make callers talk over each other or pause awkwardly. ITU-T G.114 says one-way transmission times of 0–150 ms are acceptable for most user applications, while noting that highly interactive applications may degrade at lower delays. Use that as context, not a guarantee for your provider or network path.
Jitter and uneven packet delivery
Jitter is variation in how long voice packets take to arrive. When packets arrive unevenly, the call can sound choppy or robotic. Microsoft’s Teams audio guidance uses less than 30 ms jitter as a good threshold; that is Teams-specific guidance, not a universal pass mark for every VoIP service.
Packet loss and missing audio
Packet loss occurs when voice packets fail to reach their destination. Lost packets may sound like clipped words, brief silence, or garbled audio. Microsoft’s network test guidance lists under 1% UDP packet loss as a pass target for its Teams connectivity test; use your phone provider’s targets when assessing your VoIP service.
Wi-Fi, congestion, and shared applications
A shared network can become congested when multiple devices upload or download heavily. Wi-Fi adds possible interference and contention, especially in busy offices or areas with weak signal. Test from the locations people will use, on the same network and connection type planned for launch.
VoIP router settings and network setup
Good network setup gives voice traffic a stable path and limits avoidable congestion. The right VoIP router settings vary by phone provider and equipment, so confirm supported settings, ports, traffic markings, and QoS behavior with the provider before changing configurations.
When QoS can help
Quality of Service (QoS) is a set of network rules that prioritizes selected traffic, such as voice, over less time-sensitive traffic during congestion. Microsoft explains that QoS can prioritize real-time traffic and needs consistent settings across an organization. QoS cannot create bandwidth or fix an unstable ISP connection; it can only manage how traffic competes within the network where it is configured.
Use wired connections where practical
Connect desk phones and call-critical computers to Ethernet where practical. Wired connections reduce exposure to Wi-Fi interference and contention. If staff use Wi-Fi headsets or softphones, check signal strength and test calls from their actual work areas.
Check VPNs, firewalls, and network equipment
VPNs can add delay or route voice traffic through a distant network point. Firewalls must allow the provider’s supported traffic, while routers and switches need enough capacity for the office’s combined activity. Do not apply a generic port list or traffic marking from another service; ask your provider for requirements that match your account and devices.
VoIP call quality issues: symptoms and likely causes
VoIP call quality issues often come from congestion, weak Wi-Fi, device problems, or blocked network traffic. Start with the symptom, compare a wired call with a Wi-Fi call, and check network metrics and provider status before changing multiple settings at once.
| Symptom | Likely causes | First check |
|---|---|---|
| Choppy or robotic audio | Wi-Fi interference, jitter, packet loss, congestion | Repeat the call on Ethernet; record jitter and loss during the issue |
| Clipped words or brief silence | Packet loss, weak Wi-Fi, upload saturation | Check upload use and test from a stronger Wi-Fi signal or wired connection |
| One-way audio | Firewall or router path, device or headset setting, provider path | Test another device and network; confirm firewall requirements with the provider |
| Dropped calls | Unstable connection, ISP interruption, router capacity, provider issue | Note the time and affected users; compare with ISP and provider status |
| Delay or callers talking over each other | High latency, VPN routing, distant network path | Compare a VPN-off test if permitted by policy; ask the provider to check call-path latency |
| Echo | Headset, speaker, or microphone configuration | Test a different headset and check device audio settings |
Change one factor at a time and repeat the same test call. If multiple users on different devices experience the same issue, share timestamps and test results with your ISP and phone provider; a shared network path may be involved.
How do you run a 15-minute VoIP network test?
A 15-minute test can uncover obvious capacity or quality issues before employees depend on the phone system. Test at representative desks and locations, record upload and download results plus latency, jitter, and packet loss, and repeat under normal competing network traffic whenever possible.

Minutes 0–3: record a baseline
Write down the test time, location, connection type (Ethernet or Wi-Fi), device, and headset. Run a speed and network-quality test, recording upload and download capacity along with latency, jitter, and packet loss if the tool provides them.
Minutes 3–7: check normal and busy-hour conditions
Repeat the measurements while the network is handling typical work traffic. If possible, run the check during a busy period or ask colleagues to use the cloud apps, file transfers, and video meetings expected during normal operations. Compare upload capacity and quality metrics, not download speed alone.
Minutes 7–12: place real test calls
Make test calls from a representative desk phone or softphone, headset, and browser or mobile device as applicable. Include at least one call from Wi-Fi and one from Ethernet if both will be used. Listen for clipping, robotic audio, one-way sound, delay, and dropped calls; record where and when each occurs.
Minutes 12–15: document and retest
Record the results and assign any follow-up to an owner. If you spot a problem, change one factor—such as moving to Ethernet or pausing a large upload—then repeat the same call and measurement. Compare results against your phone provider’s network targets and supported configuration before launch.
For more setup context, the VoIP call guide explains how calling works and which quality factors to consider. If your team is moving from legacy phones, the cloud-based VoIP phone system guide covers how to assess fit and setup needs.
VoIP network launch checklist
Before launch, confirm your busy-hour concurrency estimate, available upload and download capacity, and provider-specific network requirements. After the system goes live, monitor early calls and keep timestamps and symptoms for any issue that needs provider or ISP investigation.
- Estimate peak simultaneous calls from call patterns or a pilot.
- Compare per-direction voice demand with measured peak capacity and other traffic.
- Test representative devices, headsets, locations, and connection types.
- Confirm supported ports, QoS settings, and firewall requirements with your provider.
- Retest after network changes and monitor the first days of calls.
If calls remain poor after checking devices, Wi-Fi, and congestion, give your ISP or phone provider the test times, locations, connection types, and measured results. If you’re evaluating a business phone system alongside network readiness, compare Voicalyst’s business phone options against your team’s calling needs.
Frequently Asked Questions
How much bandwidth does one VoIP call use?
A practical planning estimate is about 100 Kbps in each direction per call: 100 Kbps upload and 100 Kbps download. Actual use depends on the codec, packet interval, transport overhead, and provider configuration. Check your phone provider’s specifications and leave capacity for other network traffic.
Does VoIP use upload or download bandwidth?
VoIP uses both upload and download bandwidth. Your device sends your voice upstream and receives the other caller’s voice downstream. Plan for estimated bandwidth in each direction for all simultaneous calls, and account for other services that share the connection.
What latency, jitter, and packet loss are acceptable for VoIP?
No single threshold guarantees good quality across every provider and network. ITU-T G.114 says one-way delays of 0–150 ms are acceptable for most applications; Microsoft uses under 30 ms jitter and under 1% UDP packet loss in specific guidance. Check your provider’s targets.
Does QoS improve VoIP call quality?
Quality of Service (QoS) can prioritize voice traffic over less time-sensitive traffic when congestion occurs, if relevant network devices are configured consistently. QoS cannot add bandwidth or repair an unstable ISP connection. Check your phone provider’s supported settings and your router and switch documentation before making changes.
