VoIP Bandwidth Calculator
Also known as VoIP Bandwidth Planner
Work out the bandwidth of a VoIP call header by header, then check every link that carries the calls.
Free to use. Sign up free to save, download and print.
Worked example: G.711 at 20 ms over Ethernet
Bandwidth per call, one way: 95.2 kbps
Loading the VoIP Bandwidth Calculator…
How it works
VoIP bandwidth calculation: codec payload plus headers
A VoIP call needs more bandwidth than its codec rate. G.711 codes speech at 64 kbps (ITU-T G.711) and G.729 at 8 kbps in 10 ms frames of 10 bytes (ITU-T G.729), but the speech travels in packets, each holding one packetisation interval of audio, and every packet carries a 12-byte RTP header (RFC 3550), an 8-byte UDP header (RFC 768) and a 20-byte IPv4 header (RFC 791), or a 40-byte IPv6 header (RFC 8200).
Ethernet adds 18 bytes of header and frame check sequence, and the link also spends 20 bytes of preamble, start of frame delimiter and inter-frame gap on every frame (IEEE 802.3). The headers are paid once per packet whatever the audio inside, so a longer packetisation interval sends fewer packets and needs less bandwidth. VLAN tags, tunnels, IPsec and SRTP add their own bytes to every packet. The figure is for one direction, and a call uses it in each direction.
P = R × t / 8, or P = n × B for a codec with fixed frames, n = t / T
F = P + H + L₂
BW = (F + W) × 8 / t
- P
- audio payload in each packet, in bytes; AMR, and EVS with more than one frame a packet, add a small payload header
- R
- codec bit rate, in kbps
- t
- packetisation interval, the audio carried in each packet, in ms
- n, T, B
- frames in each packet, the codec frame length in ms and its bytes per frame (G.729: 10 ms and 10 bytes)
- H
- RTP, UDP and IPv4 headers, 12 + 8 + 20 = 40 bytes, or 60 bytes with IPv6
- L₂
- layer 2 header and trailer, 18 bytes for untagged Ethernet
- W
- link time per frame that a packet capture does not show, 20 bytes on Ethernet, or 0 for header-only figures
- F, BW
- frame size in bytes, and the bandwidth of one call in one direction, in kbps
Standards
- RFC 3550 (RTP), RFC 768 (UDP), RFC 791 and RFC 8200 (IPv4 and IPv6)
- RFC 2508 and RFC 3545 (cRTP header compression)
- RFC 4303 (IPsec ESP), RFC 4106 (AES-GCM in ESP) and RFC 2784 (GRE)
- RFC 3711 (SRTP)
- RFC 4594 (DiffServ service classes: telephony EF, signalling CS5)
- RFC 1662, RFC 1990 and RFC 2427 (PPP, multilink PPP and Frame Relay framing)
- IEEE 802.11 QoS data frames with CCMP
- IEEE 802.3 Ethernet framing and IEEE 802.1Q VLAN tagging
- ITU-T G.711, G.722, G.723.1, G.726 and G.729; 3GPP AMR-NB, AMR-WB and EVS; RFC 6716 (Opus)
- RFC 3551, RFC 4867, RFC 7587 and 3GPP TS 26.445 (RTP payload formats)
Worked example
Worked example: G.711 at 20 ms over Ethernet
One G.711 call with 20 ms packetisation, carried over IPv4 on untagged Ethernet with no tunnel, counted at wire rate.
| Step | Working | Result |
|---|---|---|
| Audio payload | 64 × 20 / 8 | 160 bytes |
| RTP, UDP and IPv4 headers | 12 + 8 + 20 | 40 bytes |
| Ethernet frame | 160 + 40 + 18 | 218 bytes |
| On the wire | 218 + 20 | 238 bytes |
| Bandwidth per call, one way | 238 × 8 / 20 | 95.2 kbps |
Leave out the preamble and inter-frame gap and the same call is 87.2 kbps, the figure most published tables give, but the link still spends that time. Packing 30 ms of audio into each packet brings the call down to 84.8 kbps at wire rate, and G.729 at 20 ms needs 39.2 kbps for its 8 kbps of speech.
Why is a G.711 call more than 64 kbps?
The 64 kbps is only the audio. At 20 ms packetisation each packet also carries 40 bytes of RTP, UDP and IP headers plus 18 bytes of Ethernet header and frame check sequence, which brings a G.711 call to about 87 kbps one way. Counting the preamble and inter-frame gap that the link also spends brings it to about 95 kbps.
How much bandwidth does a G.729 call use?
G.729 codes speech at 8 kbps in 10 ms frames of 10 bytes. At 20 ms packetisation each packet carries two frames, 20 bytes of audio, behind the same 40 bytes of RTP, UDP and IPv4 headers as G.711. Over Ethernet that is 31.2 kbps one way counting the header and frame check sequence, or 39.2 kbps at wire rate. At 30 ms it falls to 28.8 kbps at wire rate.
How many VoIP calls can a 10 Mbps link carry?
Divide the link capacity, in the smaller direction on an asymmetric service, by the bandwidth of one call. A 10 Mbps link carries 105 G.711 calls at 20 ms over Ethernet at 95.2 kbps each, or 255 G.729 calls at 39.2 kbps, before signalling and any other traffic. If your QoS policy limits the priority queue to a share of the link, voice also has to fit inside that share, and the planner checks both.
How does the planner turn headcount into concurrent calls?
It uses Erlang B. From the users, busy hour call attempts per user and average hold time, it works out the offered traffic and the number of simultaneous calls needed to keep blocking at or below your target grade of service. It then reports the blocking actually achieved.
Does silence suppression halve my bandwidth?
Not for sizing. Silence suppression lowers the average, but a link has to carry the peak, and an average activity factor does not give the peak. The planner always sizes at the full rate. If you enter an activity factor, it shows the average with silence suppression beside the result for information.
Does the planner assess call quality?
No. It is a capacity tool that works out how much bandwidth the deployment needs and whether the links carry it. Voice quality scoring, DSCP marking and queue design, delay and jitter budgets and fax are outside its scope.
Sign up free to keep your work.
Free to use. Saving, downloading and printing need a free account.