Skip to content
CLIRoutes

Free tool

SIP channel and bandwidth calculator

Work out how many concurrent channels to order and how much bandwidth they need. Size from dialer agents and dial ratio, or from busy-hour traffic with Erlang B.

Size by
× agents

Lines per agent. Preview 1, predictive 2–4.

%

Spare channels for peaks and retries.

Results

Channels180150 needed + 20% headroom
Bandwidth each way16 MbpsUpload and download are symmetric
Per call, each way
87.2 kbps
Voice payload
160 bytes / packet
Headers
58 bytes / packet
Packet rate
50 pps per direction
Total packets
18,000 pps both ways

Signalling adds a few kbps per call and is not included. Order channel capacity from your carrier to match the channel figure, and check that your firewall handles the packet rate.

Start with channels

A SIP channel is one concurrent call. Your carrier limits channels and calls per second (CPS) separately, and running out of either causes failed calls that look like a bad route. There are two ways to size channels.

  • Dialer agents. For outbound dialing, channels are agents times dial ratio. Fifty agents on a predictive dialer at 3 lines each need 150 channels at peak. Preview and progressive dialing run close to 1 line per agent.
  • Busy-hour traffic. For inbound or mixed traffic, multiply calls in the busiest hour by average call length in minutes and divide by 60. That is traffic in Erlangs. Erlang B then tells you how many channels keep blocking at or under your target, such as 1%.

Add headroom on top for retries, short peaks and campaign changes. 20% is a sensible start. The channels and CPS sizing guide covers CPS, which this calculator does not.

How bandwidth per call is calculated

Each call sends a steady stream of RTP packets in both directions. The codec sets the voice payload and the packetisation time (ptime) sets how often a packet goes out. Every packet also carries 40 bytes of IP, UDP and RTP headers, plus 18 bytes of Ethernet framing on a LAN. SRTP adds a 10-byte authentication tag.

Per call, one direction
payload  = codec kbps × ptime ÷ 8
packets  = 1000 ÷ ptime  (per second)
kbps     = (payload + headers) × 8 × packets ÷ 1000

G.711, 20 ms:  (160 + 40) × 8 × 50 = 80 kbps   (87.2 with Ethernet)
G.729, 20 ms:  ( 20 + 40) × 8 × 50 = 24 kbps   (31.2 with Ethernet)

The headers are fixed per packet, which is why G.729 at 8 kbps still needs 24 kbps on the wire. Longer ptime means fewer packets and less overhead, at the cost of slightly more delay and bigger gaps when a packet is lost.

Choosing a codec

CodecWire rate at 20 msWhen to use it
G.71180 kbpsDefault for call centers. Best quality, no transcoding, works with fax and DTMF in-band.
G.72924 kbpsLow-bandwidth sites. Quality is lower and some carriers transcode it.
G.72280 kbpsWideband between your own endpoints. PSTN legs still end up narrowband.

Our trunks accept G.711 A-law and µ-law and G.729. Offer one codec first in your SDP to avoid transcoding. Answering-machine detection is more accurate on G.711, which matters for predictive campaigns.

Beyond raw bandwidth

Packet rate often limits capacity before bandwidth does. 150 calls at 20 ms is 15,000 packets per second in total, and small firewalls and consumer routers can drop packets well below their rated throughput. Check the packet figure against your firewall spec.

Last reviewed by the CLIRoutes routing team. Spotted a numbering change? Tell us.

FAQ

SIP channel and bandwidth calculator questions

Can’t find what you need? Our routing team answers within the hour, around the clock.

How many SIP channels do I need per agent?

One for preview and progressive dialing. Predictive dialers usually run 2 to 4 lines per agent, depending on answer rate and the abandon rate you allow.

Does the calculator include SIP signalling?

No. Signalling is a few kbps per call and comes in bursts. The headroom setting covers it for most deployments.

What is Erlang B?

A formula that gives the chance a call finds all channels busy, for a given traffic load and number of channels. It assumes blocked calls are dropped, not queued.

Should I include Ethernet overhead?

Yes for LAN and switch sizing. For an internet or MPLS link, providers usually quote IP throughput, so leave it out.

Do channels limit calls per second?

No, they are separate limits. A dialer can stay under its channel limit and still exceed CPS when it launches a burst of calls.