Skip to main content
June 10, 2026 · By Piyush Sahoo · Updated November 3, 2026 SIP trunking connects a PBX, contact centre platform, or voice application to the public telephone network (PSTN) over IP instead of physical circuits. A SIP trunk sets up each call with SIP signalling, carries the audio separately over RTP, and limits capacity by concurrent channels rather than by wires. This guide traces one call from INVITE to BYE, works through the channel math with real numbers, compares the authentication models, and lists the Indian rules that apply to a trunk, each linked to its source.
Key takeaways
  • A trunk is a configuration and a trust relationship with a carrier. It holds an address, an authentication method, and capacity limits, and no audio moves until a call starts.
  • Signalling and media take separate paths. A call can connect perfectly and still carry no audio, because a firewall treats the two flows differently.
  • Size channels on the busiest hour, not the average. In our worked example, 60 erlangs of traffic needs 75 channels to keep blocking under 1%.
  • Registration, digest, and IP allowlisting solve different problems. Registration says where you are, while digest and IP allowlists establish who you are.
  • In India, trunks fall inside TRAI’s commercial calling rules. Repeat violations can disconnect every SIP trunk a sender holds, across all access providers, for one year.

What is a SIP trunk?

A SIP trunk is an arrangement between your phone system and a carrier that lets the two exchange calls over IP. The word “trunk” survives from circuit-switched telephony, where it meant a shared bundle of lines between switches. The modern version has no wire to point at, which trips up many first-time deployments. Think of a trunk as three settings rather than a connection:
  • An address. This is where each side sends call requests.
  • A proof of identity. This is how the carrier knows the traffic is yours.
  • A set of limits. These cap how many calls can run at once and how fast new ones can start.
Calls run in two directions, and each has its own name. Termination is your system placing a call out to the PSTN. Origination is the carrier delivering an inbound PSTN call to your system. Some providers model both on one trunk, and others keep them as separate resources. Three counts get confused constantly, so separate them before you buy anything: A single trunk can carry many DID numbers, and a thousand DIDs don’t imply a thousand channels. If SIP itself is new to you, start with that primer and come back.

How does SIP trunking work?

Every call on a trunk is two conversations. SIP, defined in RFC 3261, negotiates the call. RTP, defined in RFC 3550, carries the sound. The diagram follows one outbound call on a trunk that uses credentials. Sequence diagram of an outbound SIP trunk call: the PBX sends an INVITE, receives a 407 challenge, resends with a digest, the provider sets up the call, 180 and 200 responses return, then RTP or SRTP audio flows in a separate band before BYE ends the call. Sequence diagram of an outbound SIP trunk call: the PBX sends an INVITE, receives a 407 challenge, resends with a digest, the provider sets up the call, 180 and 200 responses return, then RTP or SRTP audio flows in a separate band before BYE ends the call.

The signalling plane

Your system opens with an INVITE, which names the called number and includes an SDP description of the audio it can handle. The carrier may challenge that first request, and your system then repeats it with a digest response. Once the far end answers, a 200 OK returns with the chosen codec and the address that expects audio, following the offer/answer model in RFC 3264. A final ACK closes the handshake, and a later BYE ends the call. RFC 3261 sets the default ports at 5060 for UDP and TCP, and 5061 for TLS.

The media plane

Audio then flows directly between the addresses named in the SDP, on ports chosen for that call. With G.711 at the usual 20 ms packet interval, each direction sends 50 packets per second, each holding 160 bytes of audio. SIP never touches these packets.

Why the split matters when you debug

The separation explains most trunk failures, because each symptom points at one plane: Many deployments also place a session border controller at the network edge. RFC 5853 catalogues what these devices do in practice, including topology hiding, NAT traversal, and protocol repair. You need one when your PBX can’t safely face the internet or when two SIP stacks disagree about details.

Registration vs IP authentication: which should you use?

These options are often presented as one choice, but they answer different questions. Registration answers “where are you?”. Digest and IP allowlisting answer “who are you?”. A few practical rules follow from that table:
  • Prefer IP authentication when your egress addresses are stable. Keep the list as narrow as you can, because anything behind that NAT inherits the trust.
  • Use digest when your egress moves. Autoscaled and cloud-hosted systems rarely keep one address for long.
  • Use registration when the carrier must find you. It suits a site with no reachable public address. A PBX that registers many numbers at once can use the mechanism in RFC 6140.

How many channels does a SIP trunk need?

A channel is one call in progress, and a trunk needs enough of them for your busiest moment. Inbound and outbound traffic behave differently, so size them separately and then add them.

Inbound: the Erlang B method

Traffic intensity is measured in erlangs: calls per hour multiplied by the hours each call holds a channel. Assume a support line with these figures in its busiest hour:
  1. Calls: 1,200 in the hour.
  2. Hold time: 3 minutes on average. Count IVR and queue time, because those legs occupy a channel too.
  3. Load: 1,200 × 3 ÷ 60 = 60 erlangs.
Sixty erlangs does not mean sixty channels. Calls arrive randomly, so some moments run well above the average. The Erlang B formula gives the share of calls that find every channel occupied: Line chart of blocked calls against channel count at 60 erlangs. Blocking falls from about 15 percent at 55 channels to 9.6 percent at 60, then to 0.83 percent at 75, which is inside a 1 percent target. Line chart of blocked calls against channel count at 60 erlangs. Blocking falls from about 15 percent at 55 channels to 9.6 percent at 60, then to 0.83 percent at 75, which is inside a 1 percent target. At exactly 60 channels, about 116 of the 1,200 callers would hear busy. At 75 channels, that drops to about 10. Here is what each blocking target costs at this load: We calculated these figures with the Erlang B recursion. The formula assumes random arrivals and callers who give up when blocked. Treat its result as a floor when a TV spot, an outage, or an SMS blast can make callers arrive together and redial. Pooling also matters. At a 1% target, 10 erlangs needs 18 channels, or 80% headroom, while 100 erlangs needs 117, or 17%. Large shared pools run far more efficiently than several small ones, so splitting capacity across small silos wastes channels.

Outbound: rate times hold time

Outbound load is under your control, so it needs simpler math. Concurrency equals attempts per second multiplied by the average time each attempt holds a channel. Take 24,000 attempts in an 8-hour window, with 30% answered, 90 seconds of talk on answered calls, and 20 seconds of ringing on the rest:
  • Rate: 24,000 ÷ 28,800 seconds = 0.83 calls per second.
  • Channel time: (7,200 × 90) + (16,800 × 20) = 984,000 seconds.
  • Concurrency: 984,000 ÷ 28,800 = about 34 channels.
That result assumes a steady pace. Each attempt holds a channel for 41 seconds on average, so a dialler that bursts at 2 calls per second needs about 82 channels while the burst lasts. Unanswered attempts account for a third of the channel time here, so they belong in the sum.

Bandwidth

TRAI’s February 2025 numbering recommendations put a SIP call at about 87 kbps with G.711 and 32 kbps with G.729. The G.711 figure checks out from first principles: 64 kbps of audio, 16 kbps of IP, UDP, and RTP headers, and about 7 kbps of Ethernet framing. If the inbound and outbound examples peak together, round the outbound 34.2 up and you need 75 + 35 = 110 channels. That is about 9.6 Mbps in each direction with G.711. SRTP’s default 80-bit authentication tag adds about 4 kbps per call.

How many trunks do you need?

Usually fewer than you think. Create a new trunk when something about the configuration must differ, such as the environment, tenant, recording policy, or target for webhooks (callbacks). Capacity is rarely the reason, because channels are usually a plan setting rather than a property of the trunk.

How does a SIP trunk differ from PRI and VoIP?

A PRI circuit delivers a fixed block of channels: 23 on a North American T1 and 30 on the E1 used in India. A SIP trunk removes that block size, along with the physical tie to one site. VoIP is the wider category of voice over IP, and a SIP trunk is one way to use it. SIP vs VoIP covers that distinction in full. A hosted PBX differs in a separate way: the provider runs the phone system, whereas with a trunk you run it and buy only the connectivity. If you have no PBX and want to control calls from code, compare SIP with WebSocket streaming before you choose.

How do you secure a SIP trunk?

An exposed trunk can spend your money, because anyone who gets through can place calls on your account. Work through these layers:
  1. Encrypt signalling. Use TLS transport so that numbers and headers don’t cross the network in clear text.
  2. Encrypt media. Use SRTP, defined in RFC 3711, and confirm that both sides agree on it.
  3. Narrow who can connect. Keep allowlists to specific hosts, and use one credential per environment.
  4. Narrow where calls can go. Enable only the destinations you need, especially international routes.
  5. Watch for odd traffic. Alert on unusual destinations, off-hours spikes, and sudden rises in attempts.
  6. Rotate secrets when people leave. Treat SIP passwords like any other production credential.

What rules apply to SIP trunks in India?

India regulates what you send over a trunk as closely as how you connect it. The rules below come from TRAI and DoT documents, each linked to its source. They change often, so confirm the current text and take legal advice for your own case. The toll bypass text dates from 2021. Khaitan & Co reports that DoT notified new authorisation rules under the Telecommunications Act, 2023 in June 2026, and we could not confirm whether they change the OSP position. Three of these deserve a closer look. Enforcement reaches trunks directly. TRAI’s August 2024 direction named SIP and PRI when it ordered providers to stop promotional calls from unregistered senders. Within weeks, providers reported blacklisting more than 50 entities and disconnecting over 2.75 lakh resources, including SIP DIDs. Voice AI needs attention under the Third Amendment. The regulation defines an A2P call as one started by an application or automated platform without direct human dialling, including artificial voice. An outbound voice agent appears to match that wording, so raise it with your provider before launch. The text also lets terminating operators charge originating operators up to ₹0.05 per minute on A2P calls, and exempts the 140xx, 1600xx, and 1601xx series. TRAI announced these changes on 18 September 2026. The notification sets the A2P declaration and charge to start 60 days after Gazette publication. We could not confirm the publication date, so check whether they apply on your launch date. The 1600 deadlines have passed for many banks. TRAI’s November 2025 direction set adoption dates for RBI-regulated entities between 1 January and 1 March 2026. If you carry calls for a bank or NBFC, confirm its series before you route traffic. TRAI has also recommended that DoT write allocation guidelines for numbers on SIP and PRI, monitor enterprise allocations above 15 numbers per Mbps, and bring in calling name presentation for SIP and PRI calls reaching mobile networks. These are recommendations rather than rules, and we could not confirm their current status, so watch for DoT’s follow-up.

How Vobiz handles SIP trunks

Vobiz SIP trunking gives you outbound and inbound trunks as separate resources in the console and over the Trunks API. Map of Vobiz trunk resources. Outbound: your PBX or app, then an IP ACL or SIP credential, then an outbound trunk with its own SIP domain, then the called number. Inbound: a PSTN caller, then your DID, then an inbound trunk, then an origination URI. Concurrency and CPS limits are shared at account level. Map of Vobiz trunk resources. Outbound: your PBX or app, then an IP ACL or SIP credential, then an outbound trunk with its own SIP domain, then the called number. Inbound: a PSTN caller, then your DID, then an inbound trunk, then an origination URI. Concurrency and CPS limits are shared at account level.
  • Outbound. Each outbound trunk gets its own SIP domain, returned as trunk_domain. You point your PBX at that hostname, using the ports on the IP whitelisting page.
  • Authentication. Attach an IP Access Control List or a SIP credential. Credential trunks are challenged with 407. IP ACLs are evaluated first across your whole account, so a source address in any ACL on your account skips the challenge. Keep test traffic off those addresses when you test digest.
  • Registration. Registered soft-phones and WebRTC clients use endpoints, which are a separate resource from trunks. The 3CX guide shows a trunk set up through that PBX’s own registration step.
  • Inbound. An inbound trunk forwards calls for its linked numbers to an origination URI, set by host, port, and transport (UDP, TCP, or TLS). The API also accepts primary_uri_uuid and fallback_uri_uuid.
  • Encryption. The transport field controls signalling, including TLS. The secure field controls SRTP for media.
  • Firewalls. Allow the signalling and media ranges listed on the IP whitelisting page, which stays current as addresses change.
  • Capacity. Concurrency and CPS are enforced per account, so inbound and outbound calls share one pool across all trunks. The concurrent_calls_limit and cps_limit fields are stored on each trunk, while the account figures do the enforcing. Check live use with the Concurrency API, and model a campaign in the CPS and concurrency calculator.
  • Per-trunk features. Recording, transcription, PII redaction, and webhooks are all set per trunk.
  • Quality data. Each call detail record reports mos, jitter, packet_loss, and the negotiated codec, which lets you compare the sizing above with what really happened.
  • India. Calling regulations cover KYC, caller ID, and media anchoring, under which both legs of an Indian call stay in India. The UCC page explains complaint handling, and 140 and 160 series acquisition covers commercial numbers.
  • Pricing and reach. Vobiz is available in 130+ countries, and current rates are on the Vobiz pricing page. Extra capacity is a monthly subscription, and you can preview its price without being charged.
Test calls and capacity purchases are billed to your account. Run them with your own Auth ID and Auth Token, and confirm numbers and quantities first. Vobiz also connects trunks to voice AI platforms such as LiveKit and Vapi.

Frequently asked questions

Think of a SIP trunk as a phone line defined in software, linking your phone system to a carrier. It runs over IP rather than copper, so one connection can carry many calls at once. Your system can then place and receive ordinary phone calls through that carrier.
Your system sends a SIP request to the carrier, which authenticates it and connects the call to the phone network. SIP negotiates the call, and audio then flows separately over RTP or SRTP. A final SIP message ends the call and frees the channel.
A SIP trunk has no fixed channel count. You choose a number that suits your traffic, unlike an E1 PRI with its 30 channels. Calculate erlangs for your busiest hour, then apply Erlang B. For example, 60 erlangs needs 75 channels at 1% blocking.
Most teams need one trunk per distinct configuration, such as production and staging or one per tenant. Channel count, not trunk count, sets how many calls you can run. Add a trunk when settings must differ, and add channels when traffic grows.
SIP is the signalling protocol that starts, changes, and ends sessions. A SIP trunk is a carrier service built on that protocol, connecting your system to the phone network. You can use SIP inside a company without ever buying a trunk.

Further reading on Vobiz

Sources

Standards Indian regulators Reference

Build on Vobiz SIP trunking

Set up a SIP trunk and place your first call.