login | register
Wed 20 of Aug, 2008 [11:16 UTC]

voip-info.org

History

Bandwidth consumption

Created by: oej,Last modification on Tue 04 of Dec, 2007 [10:12 UTC] by evert
VOIP Bandwidth consumption naturally depends on the codec used.

When calculating bandwidth, one can't assume that every channel is used all the time. Normal conversation includes a lot of silence, which often means no packets are sent at all. So even if one voice call sets up two 64 Kbit RTP streams over UDP over IP over Ethernet (which adds overhead), the full bandwidth is not used at all times.

A codec that sends a 64kb stream results in a much larger IP network stream. The main cause of the extra bandwidth usage is IP and UDP headers. VoIP sends small packets and so, many times, the headers are actually much larger than the data part of the packet.

IAX2 trunking helps with the IP overhead, but only when you are sending more than 2 or so calls between the same Asterisk servers. John Todd has done some useful practical testing, named IAX2 trunking: codec bandwidth comparison notes and results.

The bandwidth used depends also on the datalink (layer2) protocols. Several things influence the bandwidth used, payload size, ATM cell headers, VPN headers, use of header compression and IAX2 Trunked. You can see the influence of some of this factors using the Asteriskguide bandwidth calculator.

http://www.terracall.com/FAQs_white_1.aspx has this table which shows how the codec's theoretical bandwidth usage expands with UDP/IP headers:

 Codec       BR       NEB
 G.711     64 Kbps  87.2 Kbps
 G.729      8 Kbps  31.2 Kbps
 G.723.1  6.4 Kbps  21.9 Kbps
 G.723.1  5.3 Kbps  20.8 Kbps
 G.726     32 Kbps  55.2 Kbps
 G.726     24 Kbps  47.2 Kbps
 G.728     16 Kbps  31.5 Kbps
 iLBC      15 Kbps  27.7 Kbps
 
BR = Bit rate
NEB = Nominal Ethernet Bandwidth (one direction)



Comments

Comments Filter
222

333New Release for VoIP Blocking solutions

by jenniferhan, Friday 11 of January, 2008 [09:16:47 UTC]
We have realeased our VoIP anti Blocking solutions which include:

VG Plugin software for Windows operation system,
VGSC software for Windows Operation system,
VGBC hardware for terminal side
VG SPE Gateways for terminal side.

Please contact me for more information. Thank you.

Andy Wong
Email: Xd.wong@speed-voip.com
MSN: andywong-01@hotmail.com
222

333VPN for VoIP Blocking

by jenniferhan, Wednesday 12 of December, 2007 [03:39:03 UTC]
Somebody use VPN to solve the VoIP Blocking issue. But it seems not a good way to solve the voip blocking issue. Because VPN will take more bandwidth and will take effection on the Voice Quality

Currently I am using the VGCP, a new solution to solve the VoIP Blocking issue. Following is theirs website:
http://www.speed-voip.com/index-36.html

If any of you have interested, you may try to use it to solve your VoIP Blocking problems. Thanks.

Andy
andywong-01@hotmail.com

222

333VoIP Bandwidth Calaculation

by daveg1k, Thursday 10 of June, 2004 [08:59:00 UTC]
For a White Paper on how to calculate VoIP bandwidth on Ethernet see: VoIP Bandwidth Calculation White Paper
Also see the on-line VoIP Bandwidth Calaculator
222

333test

by , Friday 02 of January, 2004 [07:40:45 UTC]
test
222

333Another link

by blackfire, Wednesday 03 of December, 2003 [15:09:07 UTC]
Here's a link to John Todd's analysis of bandwidth usage with IAX2.
http://lists.digium.com/pipermail/asterisk-users/2003-June/014788.html
Also, AFAIK, IAX2 trunking is used above 10 calls (due to 40-byte overhead vs 4-byte on single calls)