IPComms
PricingAboutBlog
Free Tool - No Sign Up Required

SIP Trunk Calculator

Determine how many SIP trunk channels your business needs using the Erlang B formula, then calculate exact bandwidth requirements for your chosen codec.

Works with Asterisk, FreePBX, 3CX, and any SIP-compatible PBX

1

Channel Calculator

Using the Erlang B formula to determine required SIP trunk channels

25
1500
30
1200
3
1 min15 min

Channel Requirements

Traffic Intensity
1.50 Erlangs
Required Channels (Erlang B)
5 channels
Recommended (+20% buffer)
6 channels
Estimated Monthly Cost (IPComms)
$27.00 / month
Based on $0.01/min, 2,700 estimated minutes
2

Bandwidth Calculator

Calculate the internet bandwidth required for your SIP trunk

Pre-filled from channel calculator above

Adds protocol header overhead for accurate real-world bandwidth

T.38 fax uses approximately 40 kbps per channel

Bandwidth Requirements

Bandwidth per Call
87.2 kbps
Total Bandwidth (both directions)
1.05 Mbps
With 20% QoS Buffer
1.26 Mbps
Minimum Internet Speed Recommended
5 Mbps (symmetrical)
Includes headroom for data traffic

How the Erlang B Formula Works

The Erlang B formula is the industry-standard method for calculating the number of trunk lines (channels) needed to handle a given amount of telephone traffic with a specified blocking probability. Named after Danish mathematician A.K. Erlang, this formula has been used in telecommunications engineering since the early 20th century.

The formula calculates the probability that a call will be blocked (rejected) given a specific number of channels and a known traffic load measured in Erlangs:

B(n, A) = (An / n!) / Σk=0..n (Ak / k!)

B = blocking probability (the chance a call is rejected)

n = number of channels (trunks)

A = traffic intensity in Erlangs

Traffic intensity in Erlangs is calculated by multiplying the number of calls per hour by the average call duration in hours. For example, 30 calls per hour with an average duration of 3 minutes gives: 30 x (3/60) = 1.5 Erlangs.

Example Calculation

A small office with 25 employees makes an average of 30 calls per hour during the busy period, with each call lasting 3 minutes:

  • Traffic = 30 calls/hour x 3 minutes / 60 = 1.5 Erlangs
  • For 1% blocking: 5 channels needed
  • With 20% buffer: 6 channels recommended

The Erlang B formula assumes that blocked calls are cleared (the caller does not retry immediately). This is the most common model for sizing SIP trunks because callers typically wait before retrying or call back later.

For more on capacity planning, read our guide on SIP Trunk Capacity Planning.

Codec Bandwidth Breakdown

Each voice codec compresses audio differently, resulting in different bandwidth requirements. The total bandwidth includes the codec payload plus IP, UDP, and RTP headers (40 bytes per packet).

Codec Payload Only With Overhead Quality Best For
G.711 ulaw/alaw 64 kbps 87.2 kbps Excellent Most SIP deployments, LAN
G.729 8 kbps 31.2 kbps Good Low bandwidth, WAN links
G.722 HD 64 kbps 87.2 kbps HD Quality HD voice, internal calls
Opus 6-510 kbps ~40 kbps Excellent WebRTC, modern endpoints
T.38 (Fax) Variable ~40 kbps N/A Fax over IP

Overhead calculation assumes 20ms packetization interval with 40 bytes of IP (20) + UDP (8) + RTP (12) headers per packet.

Common Sizing Scenarios

10-Person Office

  • Traffic: ~0.5 Erlangs
  • Channels needed: 3-4
  • Bandwidth (G.711): 0.35 Mbps
  • Monthly cost: ~$9/month

50-Seat Call Center

  • Traffic: ~25 Erlangs
  • Channels needed: 35-40
  • Bandwidth (G.711): 3.5 Mbps
  • Monthly cost: ~$450/month

200-Employee Enterprise

  • Traffic: ~10 Erlangs
  • Channels needed: 18-22
  • Bandwidth (G.711): 1.9 Mbps
  • Monthly cost: ~$180/month

Note: Call center assumes high utilization (50% of agents on calls simultaneously). Enterprise assumes lower utilization (~10% peak). Actual costs depend on call patterns. For a deeper comparison, see our SIP Trunking vs. PRI guide.

QoS Best Practices for SIP Trunking

DSCP Markings

Configure your network equipment to prioritize voice traffic using Differentiated Services Code Points:

SIP Signaling: DSCP 24 (CS3)

RTP Media: DSCP 46 (EF - Expedited Forwarding)

Network Requirements

  • Latency: Under 150ms one-way (ideally under 80ms)
  • Jitter: Under 30ms (use jitter buffer of 40-80ms)
  • Packet loss: Under 1% (ideally under 0.1%)
  • Dedicated bandwidth: Reserve voice bandwidth separately from data traffic

Jitter Buffer Configuration

Most IP phones and softphones support adaptive jitter buffers. Recommended settings:

  • Minimum buffer: 20-40ms
  • Maximum buffer: 80-160ms
  • Use adaptive (dynamic) mode rather than fixed
  • For high-jitter links: increase max to 200ms (adds latency)

Frequently Asked Questions

How many SIP channels do I need for 50 employees?

For a typical office with 50 employees, you'll need approximately 8-12 SIP trunk channels. This assumes average call volumes of 2-3 calls per employee per hour during peak times with an average call duration of 3 minutes. Using the Erlang B formula with a 1% blocking probability gives you the precise number. Use the calculator above with your specific call patterns for an accurate result. With IPComms, there are no channel limits - you pay only for minutes used.

What bandwidth does a SIP trunk need?

Each SIP trunk channel requires between 31.2 kbps (G.729 codec) and 87.2 kbps (G.711 codec) of bandwidth in each direction, including IP/UDP/RTP overhead. For 10 concurrent calls using G.711, you'd need approximately 1.74 Mbps of dedicated bandwidth. We recommend adding a 20% QoS buffer and ensuring your internet connection can handle voice traffic with low latency (under 150ms) and minimal jitter (under 30ms).

Does IPComms limit concurrent channels?

No, IPComms does not impose channel limits on SIP trunks. Unlike traditional providers that sell fixed channel bundles, IPComms uses a pay-per-minute model at $0.01/minute for US and Canada calls. Your concurrent call capacity is limited only by your PBX hardware and available bandwidth, not by arbitrary provider restrictions. This means you never pay for unused channels and can handle unexpected call spikes without service interruption.

What codec should I use for SIP trunking?

G.711 (ulaw for North America, alaw for international) is the most widely used codec for SIP trunking because it provides excellent voice quality with no compression artifacts. If bandwidth is limited, G.729 uses only about one-third the bandwidth but requires licensing on some platforms. For HD voice quality, G.722 provides wideband audio at the same bandwidth as G.711. Opus is a modern codec offering excellent quality at low bandwidth (around 40 kbps) but requires both endpoints to support it. IPComms supports all major codecs.

Ready to Get Started with SIP Trunking?

No channel limits, no contracts. Pay-as-you-go pricing starting at $0.01/min for US and Canada.