Skip to content
Omnikalc

VoIP bandwidth calculator

Pick the codec and the packetization interval, enter the number of calls and the link speed to get the packet size, the packets per second, the bandwidth per call and how many calls the link can carry.

Updated on
Your inputs
bytes

Value out of range

Value out of range

Mbps

Value out of range

%

Value out of range

Results

Bandwidth per call and per direction

95.2 kbps

Voice payload per packet
160 bytes
Size of a packet on the wire
238 bytes
Packets per second
50
Overhead share of the bandwidth
33 %
Total for all calls
4.76 Mbps
Calls the link can carry
52
Enough capacity for the planned calls

The VoIP bandwidth calculator gives the bandwidth of a voice call, including the RTP, UDP, IP and Ethernet headers, the packets per second and the number of calls a link can carry.

How the calculation works

  • Pick the codec bitrate and the packetization interval.
  • Enter the layer 2 overhead, the number of calls, the link speed and the share usable by voice.
  • The calculator gives the bandwidth per call, the packet size, the packets per second, the overhead share, the total and the calls the link can carry.

Example

With G.711 at 64 kbps and packets every 20 ms, each packet has 160 bytes of voice and 238 bytes on the wire, sent 50 times a second, so 95.2 kbps per call and per direction, of which 33 % is overhead. 50 calls need 4.76 Mbps. On a 10 Mbps link where voice may use 50 %, the limit is 52 calls.

Why it matters

The calculator helps network administrators, telecom installers and small businesses that plan an IP telephone system or check that an internet access can carry the calls.

Good to know

Real deployments add a few more things. A VPN or tunnel adds its own headers, and an encrypted stream (SRTP) adds a small authentication tag. Wi-Fi has a higher cost per packet than wired Ethernet, so the real capacity of a wireless network for voice is lower than the raw speed suggests. Quality of service should give voice priority, since delay and jitter hurt a call more than a moderate lack of bandwidth. Video calls need much more, from hundreds of kilobits to several megabits per second. Wideband codecs like Opus adapt their bitrate, so the 24 kbps value is only a typical figure. Always keep a margin for signaling and for bursts of data traffic.

The bandwidth-delay product calculator relates a link to its latency, the network latency calculator estimates delays, the Erlang C calculator sizes call centers and the TCP throughput calculator covers data transfers.

Frequently asked questions

Why is the bandwidth higher than the codec bitrate?

Each voice packet carries its own headers: 12 bytes of RTP, 8 of UDP and 20 of IPv4, 40 in total, plus the link layer. With the 20 ms interval, the 160 bytes of G.711 payload travel in a frame of 238 bytes on Ethernet, so the 64 kbps codec uses about 95 kbps.

How does the packetization interval change the result?

A longer interval puts more audio in each packet, so the headers are shared and the bandwidth falls, but each packet adds delay and a lost packet drops more speech. Intervals of 20 ms are the usual compromise. At 10 ms the headers weigh much more, above all with low bitrate codecs such as G.729.

Is the figure per direction?

Yes. A call sends voice both ways, so each direction uses the figure shown. On a symmetric link, the requirement is the same in each direction. Silence suppression, a rare feature, and the signaling traffic are not counted, so keep a margin.

Was this calculator helpful?

Thanks for your feedback!

Results are estimates provided for information purposes. They do not replace professional advice.