How Many SIP Trunks Do I Need? Sizing Guide

This is one of the most common questions we get from operators migrating from PRI to SIP, and it reveals a fundamental misunderstanding about how SIP trunking works. On PRI, the question was essential — each T1 gave you exactly 23 channels, so you needed to calculate your peak concurrent calls and buy enough T1s to cover it. On SIP, the question is usually irrelevant, because the concept of “how many trunks” does not map to SIP the way it mapped to PRI.

This guide explains the actual capacity planning question for SIP trunking and gives you the math to size your operation correctly. SIPNEX is an FCC-licensed carrier with unlimited concurrent channels — the concept of buying “enough trunks” does not apply on our platform. But bandwidth planning, codec selection, and server capacity still matter, and that is what this guide covers.

Why “how many trunks” is the wrong question

On PRI, a trunk was a physical circuit with a fixed number of channels. One T1 = one PRI = 23 channels. The trunk was the unit of capacity. Buying more trunks meant buying more capacity.

On SIP, a trunk is a logical connection between your PBX and the carrier — defined by a SIP registration (or IP-based authentication) to the carrier’s proxy. That single logical connection can carry an unlimited number of simultaneous calls on carriers like SIPNEX. You do not need multiple trunks for more capacity. You need one trunk with enough bandwidth to carry your peak concurrent call volume.

The correct question is not “how many SIP trunks do I need?” It is “how many concurrent calls will my operation generate at peak, and do I have the bandwidth and server resources to handle them?”

Some carriers — particularly resellers — do impose per-trunk or per-account concurrent channel limits (10, 25, 50, or 100 channels). On those carriers, the PRI-era question is relevant: you need to buy enough channel capacity to cover your peak concurrency. This is an artificial scarcity created by the carrier’s business model, not a technical limitation of SIP. On SIPNEX, there is no channel limit. Your capacity is your infrastructure, not our pricing page.

The concurrent call calculation

The fundamental calculation is simple: how many phone calls will be active simultaneously at your busiest moment?

For inbound operations (customer service, support lines): count the maximum number of calls in queue plus calls being handled by agents at the busiest hour. If you have 30 agents and your queue holds up to 20 callers during peak hours, your peak concurrency is approximately 50 simultaneous calls.

For outbound manual/preview dialing: peak concurrency roughly equals the number of agents actively dialing. 50 agents on preview mode = approximately 50 concurrent calls.

For outbound predictive dialing: peak concurrency equals agents multiplied by the dial ratio. The dial ratio is the number of simultaneous outbound call attempts per available agent — it depends on your answer rate and your abandon rate target. Common ratios:

• Conservative (1-2% abandon target): 2:1 to 3:1 ratio
• Standard (2-3% abandon target): 3:1 to 4:1 ratio
• Aggressive (approaching 3% abandon limit): 4:1 to 5:1 ratio

50 agents × 4:1 ratio = 200 concurrent channels at peak. 100 agents × 3:1 = 300 concurrent channels. Add 20-30% headroom for burst periods (when answer rates suddenly drop and the dialer compensates with more aggressive pacing).

For VICIdial specifically: check your real-time campaign dashboard during peak hours. VICIdial shows active channels in the system status display. Your peak concurrent channel count from historical data is the number to plan around, plus 20-30% buffer.

The bandwidth calculation

Once you know your peak concurrent call count, calculate the bandwidth requirement based on your codec selection.

G.711u (ulaw): The highest quality codec and the default for most VoIP deployments. Each call uses approximately 85 kbps in each direction (64 kbps for audio + 21 kbps for IP/UDP/RTP headers). At 200 concurrent calls: 200 × 85 kbps = 17 Mbps upstream and 17 Mbps downstream. Total: 34 Mbps of voice traffic.

G.729: A compressed codec that reduces bandwidth consumption at the cost of slight audio quality reduction. Each call uses approximately 32 kbps in each direction. At 200 concurrent calls: 200 × 32 kbps = 6.4 Mbps each direction. Total: 12.8 Mbps. G.729 is appropriate when bandwidth is limited (satellite links, rural connections), but G.711 is preferred for call center operations where audio quality directly impacts agent effectiveness and customer experience.

Opus: A modern, adaptive codec that adjusts quality based on available bandwidth. Bitrate ranges from 6 kbps to 128 kbps. Opus is increasingly supported but not yet universal in carrier environments.

Rule of thumb: plan for 100 kbps per concurrent call when using G.711. This rounds up from the theoretical 85 kbps to account for signaling overhead (SIP messages), RTCP (control protocol), and network inefficiencies. 200 concurrent calls = 20 Mbps dedicated to voice. 500 concurrent calls = 50 Mbps.

Quality matters more than raw speed. A 100 Mbps connection with 5% packet loss and 200ms jitter will produce worse call quality than a 20 Mbps connection with 0.1% packet loss and 20ms jitter. For voice traffic, prioritize connection quality: low jitter (under 30ms), low packet loss (under 1%), and low latency (under 150ms one-way). If you share your internet connection with data traffic, implement QoS (Quality of Service) to prioritize voice packets. If your operation is large enough, dedicate a separate internet connection for voice.

Server capacity considerations

Your SIP trunk’s capacity is also limited by your PBX or dialer server’s processing power.

Asterisk/VICIdial on a modern server (8+ CPU cores, 16+ GB RAM) can typically handle 300 to 500 concurrent calls depending on configuration, features enabled (call recording, AMD, AGI scripts), and codec (G.711 requires less CPU than G.729 because it does not need to compress/decompress audio). If you are running AMD (Answering Machine Detection) on every outbound call — which most VICIdial predictive campaigns do — budget 30 to 50% more CPU overhead than calls without AMD.

Call recording adds disk I/O requirements. Each recorded G.711 call generates approximately 480 KB per minute (3.84 Mbps for 100 concurrent recorded calls). Ensure your storage can handle the sustained write throughput during peak hours and that you have adequate disk space for retention (a 100-agent operation recording 8 hours of calls per agent per day generates approximately 20 GB of audio files daily).

The server is rarely the bottleneck. In practice, bandwidth and carrier capacity are more commonly the limiting factors than server capacity. A mid-range dedicated server handles most call center workloads. If you are scaling beyond 500 concurrent channels, consider distributing the load across multiple VICIdial servers with a centralized database.

Capacity planning checklist

Use this to size your SIP trunking deployment:

Calculate peak concurrent channels: agents × dial ratio × 1.25 (25% burst buffer). Example: 75 agents × 3.5 ratio × 1.25 = 328 concurrent channels.

Calculate bandwidth requirement: concurrent channels × 100 kbps. Example: 328 × 100 kbps = 32.8 Mbps dedicated to voice.

Verify internet connection quality: run a VoIP-specific speed test that measures jitter, packet loss, and latency, not just download/upload speed. Target: jitter under 30ms, packet loss under 1%, latency under 150ms.

Verify server capacity: for VICIdial, a dedicated server with 8+ cores and 16+ GB RAM handles up to ~400 concurrent channels with AMD and recording enabled.

Verify carrier channel policy: confirm your carrier does not cap concurrent channels. On SIPNEX: unlimited. If your carrier caps at a number lower than your peak requirement, either buy additional capacity or switch carriers.

Plan for growth: if your operation is growing, size for projected peak, not current peak. Adding bandwidth and server capacity is straightforward. Adding carrier capacity is only an issue if your carrier imposes channel limits.

Frequently asked questions

How many SIP trunks do I need for my business?

On a carrier like SIPNEX with unlimited concurrent channels, you need one SIP trunk (one logical connection). That single trunk handles as many simultaneous calls as your bandwidth and server resources can support. The question you actually need to answer is how many concurrent calls your operation will generate at peak — agents times dial ratio for predictive dialing, or agent count for manual dialing — and whether your internet bandwidth can support that volume at approximately 100 kbps per concurrent G.711 call. On carriers that cap concurrent channels, you need to purchase enough channels to cover your peak concurrency plus a 25% burst buffer.

What bandwidth do I need for VoIP?

Plan for 100 kbps per concurrent call using G.711 codec (the standard for call center quality). 50 concurrent calls = 5 Mbps dedicated to voice. 200 concurrent calls = 20 Mbps. 500 concurrent calls = 50 Mbps. These are symmetric requirements — you need the same bandwidth in both upstream and downstream directions. More important than raw speed is connection quality: jitter under 30ms, packet loss under 1%, and latency under 150ms. A high-speed connection with poor quality metrics will produce worse call quality than a lower-speed connection with stable, low-jitter performance. Implement QoS on shared connections or use a dedicated connection for voice.

Can I start small and scale up?

Yes, and this is one of the primary advantages of SIP over PRI. On PRI, scaling up meant ordering and installing a new physical T1 circuit — a process that took weeks and committed you to the cost of 23 additional channels whether you used them or not. On SIP, scaling up means making more calls. If you start with 10 agents and grow to 100, you do not need to upgrade your trunk — you need to upgrade your bandwidth and possibly your server. On SIPNEX, there are no channel limits to adjust, no capacity upgrades to purchase, no scaling fees. Your single trunk handles 10 concurrent calls or 1,000 concurrent calls without any carrier-side changes.

What is the difference between SIP channels and SIP trunks?

A SIP trunk is the logical connection between your phone system and the carrier — defined by your SIP registration or IP authentication to the carrier’s proxy. A SIP channel is a single simultaneous call on that trunk. One trunk can carry many channels. On PRI, these concepts were equivalent: one trunk (T1) = 23 channels. On SIP, they are decoupled: one trunk = unlimited channels on carriers like SIPNEX. Carriers that sell “SIP channels” separately are imposing artificial limits that mimic the PRI model — you are buying scarcity that does not exist in the underlying technology.

---

SIPNEX SIP trunks have no concurrent channel limits. The only capacity question is your bandwidth and server resources, not our pricing tiers. Get a trunk that scales with you or see our published rates.