SIP Trunk Bandwidth Calculator

June 26, 2026

SIP Trunk Bandwidth Calculator

Estimate voice bandwidth for simultaneous calls, codec payload, packetization interval, RTP/UDP/IP/Ethernet headers, VLAN tags, VPN encapsulation, duplex traffic, and planning headroom.

☎SIP trunk presets

⚙Voice bandwidth inputs

Use the peak number of active two-way calls, not registered extensions.

Wire-rate mode includes the 20 byte preamble and inter-frame gap slot.

Keep a small allowance for SIP keepalives, re-INVITEs, registration, and call setup bursts.

Per-call one-way 0 kbps including RTP and link overhead
Trunk one-way 0 Mbps with signaling and headroom
Duplex bandwidth 0 Mbps send plus receive at peak calls
Estimated call capacity 0 calls on available upload after headroom
Codec payload and packet rate0
RTP/UDP/IP/Ethernet overhead per packet0
VLAN, SRTP, and VPN overhead0
Voice bearer before and after headroom0
SIP signaling and duplex accounting0
Planning interpretationReady

📞Codec and packet spec grid

12RTP header bytes
8UDP header bytes
20IPv4 header bytes
40IPv6 header bytes
18Ethernet plus FCS bytes
20preamble plus IFG bytes
50packets/sec at 20 ms
15%normal trunk headroom

📊Codec bandwidth reference

Codec Codec rate 20 ms payload Typical planning note
G.711 u-law / A-law64 kbps160 bytesCommon PSTN quality codec; simple CPU load but high WAN bandwidth.
G.722 wideband64 kbps160 bytesHD voice on many phones; bandwidth resembles G.711 before overhead.
G.7298 kbps20 bytesEfficient WAN codec; licensing and transcoding may affect platforms.
Opus voice16-24 kbps40-60 bytesFlexible modern codec; packet size depends on configured bitrate.
G.726 ADPCM32 kbps80 bytesMiddle ground for legacy gateways and compressed voice paths.
iLBC / GSM-FR13-15 kbps33-38 bytesLow-rate legacy choices; packet overhead becomes a large share.

🖧Header and encapsulation table

Layer or wrapper Bytes Applies per packet? SIP trunk planning note
RTP + UDP + IPv440YesThe classic RTP header stack before Layer 2 framing.
RTP + UDP + IPv660YesIPv6 adds 20 bytes more than IPv4 for every voice packet.
Ethernet II with FCS18YesUsually absent from captures but present on the wire.
Preamble and inter-frame gap20YesUse for physical wire-rate calculations and switch port sizing.
802.1Q voice VLAN4 eachYesOne tag is common; carrier handoffs may use double tagging.
SRTP auth tag4 or 10YesDepends on crypto profile and endpoint configuration.

🔒VPN overhead reference

Tunnel profile Typical overhead Effect on VoIP When to use in calculator
No VPN / direct trunk0 bytesLowest packet overheadSIP provider reachable directly or via SBC edge.
WireGuard over UDP/IPv460 bytesModerate overheadBranch or home PBX tunnel with modern VPN endpoints.
IPsec ESP NAT-T74 bytesHigher overheadCommon firewall-to-firewall SIP transport.
OpenVPN UDP69 bytesHigher overheadRemote PBX or softphone tunnel where OpenVPN is used.
GRE over IPsec98 bytesVery high overheadRouted voice VLANs across legacy enterprise tunnels.
Custom wrapperUser valueDepends on designUse packet captures or vendor documentation for bytes.

🏢Common SIP trunk sizing examples

Scenario Calls Codec / ptime Typical one-way bandwidth
Small office direct trunk4G.711 / 20 msAbout 0.4-0.5 Mbps with headroom.
Remote branch over WAN8G.729 / 20 msAbout 0.3 Mbps, but packet rate still matters.
Home PBX with Opus6Opus 24 / 20 msAbout 0.4 Mbps on a direct trunk.
Call center carrier handoff30G.711 / 20 msAbout 3.5-4 Mbps before other data traffic.
VPN branch voice VLAN12G.729 / 20 msVPN overhead can double low-rate codec load.
HD voice team phones16G.722 / 20 msPlan near G.711 bandwidth plus QoS margin.
QoS tip: Reserve the calculated one-way bandwidth on both WAN directions. Voice quality depends on upload headroom, jitter, and packet loss more than on the download speed advertised by the ISP.
Packet tip: Low-bitrate codecs save payload bandwidth, but each call still sends many RTP packets. With VPNs or short packetization intervals, header overhead can dominate the trunk size.

When you order an SIP trunk, you have to consider more than just number of channels that the trunk should support. The bandwidth requirements for a SIP trunk are essential consideration, because if you dont consider factors like the codec that is used for calls, the packet interval for those calls, and whether you are using a VPN to access your telephony provider, your SIP trunk may experience poorly call quality during peak hour, or the trunk may experience dropped calls when other device are using the link. Because voice packets are small, a high volume of voice packets must travel on the link.

For instance, with a packet interval of twenty milliseconds, fifty packets will travel in each direction for each simultaneous call. This factor impact the bandwidth requirements for a SIP trunk more than the codec settings for the link. Small payload as a result of using a low bitrate codec reduce the amount of data that can pass through a link, but the headers for each packet remains the same size.

How Much Bandwidth Does a SIP Trunk Need

Furthermore, the headers will expand with the addition of a VLAN tag, encryption protocol, or a VPN tunnel. Thus, a low bitrate codec can actualy use more bandwidth with a VPN protocol then a higher bitrate codec would require without a VPN. The calculator included with this article can help you determine your bandwidth requirements by entering the number of simultaneous call, the codec for the calls, the packet interval for each call, and whether you will use any encapsulation protocol like a VPN.

Furthermore, the calculator can help you test various level of headroom. Headroom is the amount of bandwidth reserved for the network, and it ensure that jitter buffers are not emptied when other application on the network experience a spike in data needs. For the best performance, fifteen to twenty percent of bandwidth should be left to the network for this purpose.

Choosing the codec for your calls can be a three-way decision. G.711 codecs provides the best audio quality for calls, and require the least amount of CPU power from your phones endpoint. However, G.711 codecs use the most bandwidth for calls.

G.729 and Opus codecs saves a small amount of bandwidth for each call, but may require licensing for your PBX system. Furthermore, codecs like G.722 provide better call quality than G.711 without increase the amount of bandwidth that is used for calls. However, the bandwidth savings of the G.722 codec are only relative to G.711, since both use the same data header.

The packet interval will interact with every other element of your bandwidth calculation. Using a ten-millisecond packet interval will halve the amount of data for each packet, but will double the rate at which packet are sent across the link. Furthermore, the headers for packets will represent a larger portion of the total size of each packet.

Thirty- and forty-millisecond intervals will reduce the number of packets that must cross the link, but will increase the latency of the packets reaching listeners. Most voice phone system and softphone application use a twenty-millisecond interval as the default setting. Many people are unaware that using a VPN will impact the bandwidth requirement for their SIP trunk.

For instance, a sixty-byte WireGuard wrapper will be added to each packet that crosses the link. This sixty-byte amount is the same for each codec. Thus, a sixty-byte wrapper can represent more than half the size of a packet on a G.729 link, but will be a smaller portion of the size of each packet on a G.711 link.

You can use the calculator to compare different type of VPN protocols to ensure that your bandwidth remain within your upload limit. Another consideration for bandwidth is the traffic create by SIP signaling. Calls use signaling traffic for steps like registration to the system, OPTIONS requests to keep endpoints “alive,” and re-INVITEs when changing call parameter.

With many endpoint on the network, this type of traffic add up. Thus, it is recommended to include some headroom in your calculation for these signaling packet. With the results from the calculator, you must determine how the result compare to your actual circuit.

For example, the upload speed for your internet access may appear to be sufficient, but with headroom and other application on the network that use the upload speed, it may not be sufficient for your calls. Furthermore, you should ensure that your link have headroom for other data application. For example, you may not want any dropped file while using your SIP trunk.

Thus, the results will tell you the minimum amount of bandwidth that a link must have to support your calls. With this value, you can ensure that your link has the necessary bandwidth for your calls, so that adding one more call will not negative impact the quality of those calls.

SIP Trunk Bandwidth Calculator

Related posts

Leave a Comment