How Much Bandwidth Does VoIP Need? A Practical Calculation
Ask how much bandwidth VoIP needs and you'll get answers anywhere from 30 to 100 kbps per call. They can all be right, because the figure depends on the codec, the packet size and which headers you count. This guide shows the calculation step by step, checks it against Cisco's published numbers and turns it into a figure for a whole office.
The short answer: bandwidth per call
Each call sends audio in both directions, so these figures apply to upload and download at the same time. They assume the usual 20 ms packets over IPv4.
| Codec | Codec bitrate | Voice payload per packet | At the IP layer | On Ethernet |
|---|---|---|---|---|
| G.711 | 64 kbit/s | 160 bytes | 80 kbps | 87.2 kbps |
| G.722 | 64 kbit/s | 160 bytes | 80 kbps | 87.2 kbps |
| G.729 | 8 kbit/s | 20 bytes | 24 kbps | 31.2 kbps |
| Opus at 20 kbit/s | 20 kbit/s | 50 bytes | 36 kbps | 43.2 kbps |
Opus is variable, so treat its row as an example; 20 kbit/s sits at the top of the range the Opus specification recommends for wideband speech. If you're still choosing a codec, our VoIP codecs comparison covers quality and compatibility.
How to calculate it yourself
Every voice packet is a small piece of audio wrapped in several headers. The calculation for G.711 at 20 ms looks like this:
- Voice payload per packet = codec bitrate × packet interval ÷ 8. For G.711: 64,000 × 0.020 ÷ 8 = 160 bytes.
- Add the IP, UDP and RTP headers: 20 bytes for IPv4, 8 for UDP and 12 for RTP (RFC 3550), 40 bytes in total. 160 + 40 = 200 bytes.
- Add the layer 2 overhead for the link you're sizing. Ethernet adds 18 bytes (a 14-byte header and a 4-byte checksum), giving 218 bytes.
- Packets per second = 1 ÷ packet interval. At 20 ms that's 50 packets per second.
- Bandwidth = bytes per packet × 8 × packets per second. 218 × 8 × 50 = 87,200 bits per second, or 87.2 kbps in each direction.
For G.729, the payload is 8,000 × 0.020 ÷ 8 = 20 bytes. Adding 40 bytes of headers and 18 of Ethernet gives 78 bytes, and 78 × 8 × 50 = 31.2 kbps.
These results match Cisco's per-call bandwidth table, which lists 87.2 kbps for G.711 and 31.2 kbps for G.729 on Ethernet with the same 40-byte header and 18-byte Ethernet assumptions. Notice how much the headers weigh: in a G.729 packet, almost three quarters of every Ethernet frame is overhead, which is why G.729 saves less than its 8-to-1 bitrate ratio suggests.
How packet size changes the result
The packetization interval is how much audio goes into each packet. Bigger packets mean fewer headers per second, but more delay and more audio lost when a packet goes missing.
| Packet interval | Packets per second | G.711 on Ethernet | G.729 on Ethernet |
|---|---|---|---|
| 10 ms | 100 | 110.4 kbps | 54.4 kbps |
| 20 ms | 50 | 87.2 kbps | 31.2 kbps |
| 30 ms | 33.3 | 79.5 kbps | 23.5 kbps |
20 ms is the usual default and the right balance for most networks. Moving to 30 ms saves a little bandwidth but adds 10 ms to every packet's delay, which eats into the budget discussed in fixing VoIP call quality. Both ends must agree on the interval, so change it only for a specific reason.
What else adds overhead
At 50 packets per second, every extra byte per packet costs 0.4 kbps. That makes it easy to adjust the base figure:
| Extra | Bytes per packet | Extra bandwidth at 20 ms |
|---|---|---|
| SRTP encryption (default 80-bit authentication tag) | 10 | 4 kbps |
| IPv6 instead of IPv4 | 20 | 8 kbps |
| VLAN tag (802.1Q) | 4 | 1.6 kbps |
| VPN tunnel | Varies with the VPN, often tens of bytes | 4 kbps for every 10 bytes |
The SRTP figure comes from RFC 3711, which sets the default authentication tag at 80 bits; its standard encryption doesn't change the payload size. A few more details explain why published figures differ:
- Physical Ethernet framing: on the wire, each frame also has an 8-byte preamble and a 12-byte gap, so some calculators show about 95 kbps for G.711. Cisco's 87.2 kbps leaves these out.
- Signaling and RTCP: SIP messages are tiny, and RTP's control protocol is designed to use a small share of the session bandwidth, typically 5%.
- Silence suppression: it can cut traffic during pauses, but Cisco advises not counting on it when you design a network, especially for fewer than 24 calls.
- Header compression (cRTP): it shrinks the 40 bytes of headers to 2 or 4, but it works link by link and isn't available over Ethernet, so it doesn't help calls that cross the internet.
From one call to your whole office
Total voice bandwidth = per-call figure × peak simultaneous calls that cross the link. Work out the peak with our guide to how many simultaneous calls you need, then check which calls actually use your internet connection.
Worked example
A 30-person office uses a hosted PBX with G.711 and SRTP. At its busiest moment it has 10 external calls and 2 internal calls between desk phones.
- Per stream with SRTP: 87.2 + 4 = 91.2 kbps in each direction.
- External calls: 10 × 91.2 = 912 kbps each way.
- Internal calls: on a hosted PBX that relays audio, each internal call carries two streams up and two down, one for each phone. 2 calls × 2 × 91.2 = 364.8 kbps each way.
- Total: about 1.28 Mbps up and 1.28 Mbps down at peak.
On a connection with 2 Mbps of upload, voice alone would take about 64% at peak, and a single cloud backup or video meeting would push calls into trouble. With 10 Mbps of upload, it's under 13%, which leaves plenty of room as long as voice gets priority. Upload is almost always the tighter side on business broadband, so check it first. With an on-premise PBX, the internal calls in this example would stay on the LAN and need no internet bandwidth at all, one of the trade-offs covered in hosted vs on-premise PBX.
Checking your connection
- Run speed tests in both directions at your busiest time of day, not first thing in the morning.
- Look at traffic graphs on your router or firewall to see what else uses upload: backups, file sync, video meetings, cameras.
- Measure latency, jitter and packet loss over several hours, because a speed test shows capacity, not quality.
- Set up QoS so voice packets go first when the link is busy. Our guide to QoS for VoIP covers the settings.
- For home workers, check each person's upload speed and Wi-Fi; our guide to VoIP for remote teams has a checklist.
Common sizing mistakes
- Using the codec bitrate: 64 kbps for G.711 ignores headers; plan with about 87 kbps on Ethernet.
- Checking only download: calls use the same bandwidth in both directions, and upload runs out first.
- Sizing for the average: the busiest moment is what callers hear.
- Forgetting relayed internal calls on hosted systems.
- Ignoring VPN and encryption overhead for remote staff.
- Treating enough bandwidth as enough: without QoS, a burst of other traffic can still drop voice packets on a link that's big enough on average.
For how bandwidth fits into choosing and running a phone system, see our business VoIP phone system guide.
How BtoBSkills can help
Bandwidth and codec planning is part of every new system we build. With our VoIP installation and configuration service, we size your connection for your peak calls, choose codecs to suit it and configure trunks and call routing to match. Request a quote with your number of users, your busiest-hour call volume and your internet speeds.
Frequently asked questions
How much bandwidth does one VoIP call use?
Does VoIP use upload or download bandwidth?
How much data does a VoIP call use per hour?
Is 1 Mbps of upload enough for VoIP?
Does a faster connection improve call quality?
Related services
Related articles
- VoIP Codecs Compared: G.711, G.729, G.722 and Opus
How G.711, G.729, G.722 and Opus differ in sound quality, bitrate, loss handling and compatibility, and the codec order to use on phones, trunks and apps.
- Fixing VoIP Call Quality: Jitter, Latency and Packet Loss
Target values for latency, jitter and packet loss, a symptom-to-cause table, a step-by-step troubleshooting method and the fixes that solve most VoIP quality problems.
- How Many Simultaneous Calls Does Your Business Need?
What counts as a simultaneous call, how to measure your busiest hour, a worked Erlang B example and how to turn the result into a 3CX license or Yeastar capacity.
- Hosted PBX vs On-Premise PBX: Costs, Control and Which to Choose
Hosted and on-premise PBXs compared on cost, control and outage risk, with a break-even method for your own quotes and a guide to which model fits.
- QoS for VoIP: How to Prioritize Voice on Your Network
Where voice actually gets delayed, which DSCP markings to use, how to set priority queues and shaping on your router, and a simple test to prove it works.
- Business VoIP Phone Systems: The Complete Guide for SMEs
How a business VoIP phone system works, the deployment and licensing choices you'll face, what your network needs, and how to switch without losing calls or numbers.
Sources
- Cisco: Voice Over IP - Per Call Bandwidth Consumption (accessed 2026-11-19)
- IETF RFC 3550: RTP: A Transport Protocol for Real-Time Applications (accessed 2026-11-19)
- IETF RFC 3711: The Secure Real-time Transport Protocol (SRTP) (accessed 2026-11-19)
- IETF RFC 6716: Definition of the Opus Audio Codec (bitrate sweet spots) (accessed 2026-11-19)


