VoIP.infoThe independent guide to business communications.
VoIP.info Guide

SIP trunk channels and simultaneous calls

Size external capacity around busy-hour demand and the provider’s counting rules.

Reviewed 2026-10-18Foundational

A number is not a channel

A telephone number identifies a destination; a channel limit constrains simultaneous calling capacity under a service's rules. Many numbers may share one capacity pool. Extensions are another quantity entirely and should not be counted as permanently active external calls.

Users, numbers and active calls are different counts
Many users and phone numbers can share a smaller pool of simultaneous external calls. Capacity should follow measured demand and the provider’s leg-counting rules.

A simple staff × usage scenario is not an Erlang blocking model. Transfers and forwarding may use additional external legs.

Identify the counting model

Ask how the provider counts inbound calls, outbound calls, forwarded calls, conferences and transfers. A call forwarded through the PBX may involve more than one external leg. Confirm whether inbound and outbound limits are shared or separate.

Measure demand before expanding

Review busy-hour usage and blocked-call evidence. Separate genuine demand peaks from retries caused by a fault. The concurrency calculator provides a simple scenario estimate; it is not a queueing model that guarantees a chosen blocking probability.

Plan the full capacity chain

Check trunk limits alongside PBX resources and bandwidth. Increasing licensed channels cannot fix an overloaded uplink or a provider authentication failure. Define how callers are handled when capacity is reached: overflow, alternate destination or a clear busy response. Test the boundary with the provider through an agreed procedure and review usage after staffing or workflow changes.

Do not equate an Asterisk group with contracted channels

An Asterisk channel-group count is a local dialplan measurement. Contracted simultaneous calls, calls per second and provider admission remain separate evidence and controls.

Turn Broadvoice scaling language into an ordered limit

Broadvoice advertises on-demand channels, capacity and bursting. The Broadvoice provider record treats those statements as discovery evidence rather than a selected concurrency or call-start-rate entitlement. Preserve the signed order and an approved bounded result.

Turn SIPcity included-channel language into an account limit

SIPcity includes one channel and describes internet bandwidth as a practical constraint. The SIPcity provider record keeps the ordered concurrent-call entitlement, call-start controls, access capacity and measured PBX result separate.

Translate Toku country capacity into a signed entitlement

Toku says country-number concurrency is limited by purchased channel capacity and shared across assigned numbers in that country. The Toku provider record keeps ordered channels, call-start controls, route limits and measured load evidence separate.

Treat LoopUp channel limits as an ordered entitlement

LoopUp's self-service form accepts 1 through 100 channels and directs larger requests to support. The provider record keeps that setting separate from call-start rate, PBX capacity, bandwidth and measured concurrency.

CarrierX trunk capacity is not account capacity

Separate inbound and outbound Trunk-object limits from calls per second, PBX capacity and upstream limits. The CarrierX diagnostic keeps selection and capacity evidence distinct.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Continue your research

Hub

VoIP networking

Trace signaling and audio through your actual topology before changing ports or prioritization.

Explore topic →
Hub

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →
Hub

VoIP planning tools

Use calculations to make assumptions visible, then validate them against real workload and equipment.

Explore topic →
Guide · Asterisk Latest API GROUP, GROUP_COUNT, GROUP_LIST and GROUP_MATCH_COUNT references generated from branch 23, channel architecture, variable-inheritance and Local-channel optimization documentation reviewed October 12, 2026; a group count is local channel state rather than a provider entitlement or complete call count, and no PBX, dialplan, group, channel, bridge, trunk, account, call, limit or denial was inspected or tested

Asterisk channel groups: counting concurrency without counting calls twice

Assign channels to explicit group and category names, interpret counts against the chosen call leg and lifecycle, and keep a local dialplan guard separate from trunk entitlement or platform capacity.

Read guide →
Troubleshooting · Asterisk Latest API GROUP, GROUP_COUNT, GROUP_LIST and GROUP_MATCH_COUNT references generated from branch 23, channel architecture, variable-inheritance and Local-channel optimization documentation reviewed October 12, 2026; a group count is local channel state rather than a provider entitlement or complete call count, and no PBX, dialplan, group, channel, bridge, trunk, account, call, limit or denial was inspected or tested

Asterisk channel-group count is wrong or a call limit is bypassed

Trace one admission decision through the selected channel, exact group and category, count timing, created legs, Local-channel optimization, transfer and teardown before changing a threshold.

Read guide →
Provider research · Broadvoice current SIP Trunking product, master-service-agreement, Elastic SIP Trunking Addendum link, SIP portal, contact and support, and platform-status pages reviewed October 13, 2026; public pages do not prove the selected account, order, authentication, registration, inbound format, codec, DTMF, fax, encryption, failover mechanics, capacity limit, emergency entitlement, messaging eligibility, price or support response, and no account, portal, credential, number, PBX, SBC, packet, call, media stream, fax, failover event, load test, message or emergency call was inspected or tested

Broadvoice SIP Trunking: routing, capacity and acceptance boundaries

Keep the Broadvoice portal, PBX or cloud target, DIDs, routing, burst capacity, failover, support and signed service terms attached to the selected trunk order.

Read guide →
Provider research · SIPcity SIP Trunking, registration and peering, generic registration, 3CX, network ports and IPs, number-porting, channel, billing and master-service-agreement pages reviewed October 13, 2026; public material does not prove the selected account, order, number inventory, account-specific host, failover behavior, compatibility, negotiated media, fax entitlement, protected path, channel ceiling, call-start rate, price, support response or observed call result, and no account, portal, credential, number, PBX, packet, call, media stream, fax, failover event, load exercise, message or emergency call was inspected or tested

SIPcity SIP trunks: registration, peering and 000 boundaries

Keep SIPcity credential registration, static-IP peering, DID routing, published media parameters, channel entitlement and Australian 000 dependencies attached to the selected order.

Read guide →
Provider research · Toku Carrier Services, Microsoft Teams, Voice Connectivity, Singapore, Malaysia and Indonesia number, Singapore subscriber, portability, regulation and wholesale pages reviewed October 14, 2026; public material does not prove the selected account, universal SIP authentication or registration, DID inventory, customer failover contract, generic trunk encryption, fax, account capacity, price, compatibility, support response or observed call result, and no account, order, credential, trunk, number, PBX, SBC, packet, call, media stream, fax, failover event, load exercise, message or emergency call was inspected or tested

Toku carrier voice: APAC numbers, media and country boundaries

Keep Toku carrier coverage, selected-country numbering, E.164 delivery, media capabilities, purchased channel capacity and emergency rules attached to the exact market and order.

Read guide →
Provider research · LoopUp SIP Trunking Setup, public certificate-chain, supported-root and current AudioCodes and Ribbon configuration pages plus RFC 5246 and RFC 4568 reviewed October 14, 2026; the public material does not prove the selected account, number inventory, endpoint, certificate, DNS answer, route, DTMF method, emergency service, messaging, support entitlement, price, compatibility or observed call result, and no account, portal, credential, key, certificate, DNS answer, PBX, SBC, packet, call, media stream, fax, failover event, load exercise, message or emergency call was inspected or tested

LoopUp SIP Trunking: IP endpoints, regional routing and mutual-TLS boundaries

Keep LoopUp's no-REGISTER IP trunk, regional number assignment, endpoint distribution, channel limit, mutual TLS, SRTP, codecs and T.38 attached to the selected order and observed path.

Read guide →
Troubleshooting · Current first-party CarrierX trunk-group, trunk, SIP-trunk, call and phone-number documentation reviewed October 18, 2026. The pages distinguish DID assignment, trunk-group routing type, per-trunk priority and weight, soft and hard SIP failure handling, SIP OPTIONS monitoring, endpoint authorization, capacity and codecs. Documented defaults are configuration references, not observed account values. The reviewed pages do not establish SIP REGISTER as the inbound binding, one universal failover result for every response, access-path diversity, established-call survival or an account-wide calls-per-second limit. No CarrierX account, API response, DID, endpoint, trunk group, trunk, ACL, credential, token, PBX, packet, media stream, rate, emergency workflow or live call was inspected or tested

CarrierX trunk-group failover or round-robin selects the wrong trunk

Trace DID assignment, routing type, priority or weight, hard and soft failures, SIP OPTIONS state, endpoint delivery and PBX handling for one CarrierX call.

Read guide →