A SIP trunk is how most business phone systems now reach the outside world. It replaces bundles of analog or ISDN lines with a service delivered over your data connection, sized in channels and carrying your phone numbers. This guide explains what a SIP trunk is, how it works under the hood, how providers package it and what to check before you sign up.

What a SIP trunk is

In telephony, a trunk is a shared line between two switches, as opposed to a line that serves a single phone. A SIP trunk is the same idea over an IP network: a logical connection between your PBX and a provider's network, using SIP (Session Initiation Protocol, RFC 3261) to set up calls and RTP packets to carry the audio.

The provider, often called an ITSP (internet telephony service provider), gives you three things:

  • Channels: the number of external calls you can have at the same moment.
  • Numbers: DIDs (direct inward dialing numbers) that ring your PBX, either new or ported from your old carrier.
  • Connectivity to the phone network: routing to landlines, mobiles, international destinations and emergency services.

Nothing physical is installed per channel. The trunk is configuration on both sides, carried over your internet connection or a private link from the provider. The SIP Forum publishes SIPconnect, a technical recommendation for interconnecting IP PBXs with service provider networks; the current version, 2.0, was ratified in December 2016. If you're new to how the PBX side works, start with what an IP PBX is.

What it replaces

Traditional lineCalls at onceHow you add capacity
Analog line1Order another physical line
ISDN BRI2Order another BRI circuit
ISDN PRI on an E1 (most of the world)30Order another E1 circuit
ISDN PRI on a T1 (North America)23Order another T1 circuit
SIP trunkAny number of channels you buyChange the contract, as long as your bandwidth allows it

Traditional lines are disappearing in several countries. In the UK, Openreach says BT Group will retire the PSTN by 31 January 2027, which affects every service on copper lines, including ISDN. Other countries run their own timetables, so check with your carrier. If you're planning the move, our ISDN to VoIP migration checklist covers the steps.

How a SIP trunk works

Signaling and audio

For an outbound call, your PBX sends a SIP INVITE to the provider's SIP server, often a session border controller (SBC) that protects the provider's network. The provider routes the call onward and the audio flows as RTP between your PBX and the provider's media servers. Inbound calls work the other way round: the provider sends an INVITE to your PBX with the dialed number, and your inbound rules decide where it rings.

Authentication: registration or IP address

Providers recognize your PBX in one of two ways:

RegistrationIP authentication
How it worksYour PBX registers with a username and password, like a phone registering to a PBXThe provider accepts calls only from your fixed public IP address and sends inbound calls there
Needs a static IPNoYes
Main riskStolen credentials can be used to place fraudulent callsMisconfigured firewall rules; failover to another site needs provider changes
Typical fitSmall offices, dynamic IP connections, hosted PBXsFixed sites, data centers, larger trunks

Numbers and caller ID

The number of DIDs is independent of the number of channels: 50 numbers on a 10-channel trunk is perfectly normal. Each inbound call carries the dialed number, and your PBX matches it to a rule. For outbound calls, providers generally let you present only numbers you hold or have verified. Within trusted networks, SIP carries the verified caller identity in a separate header defined in RFC 3325, which is why "wrong caller ID" problems are often fixed in the trunk's header settings rather than on the phones.

Transport and encryption

Most trunks run SIP over UDP on port 5060, with TCP as an option. Some providers support TLS (usually port 5061) for encrypted signaling and SRTP for encrypted audio. If call privacy matters to you, ask for both, and confirm your PBX supports them on trunks as well as on phones.

How providers package SIP trunks

  • Per channel plus metered calls: a fixed fee per channel and per-minute charges by destination.
  • Per channel with bundled minutes: a higher channel fee that includes local and national calls, usually under a fair-use policy.
  • Pay as you go: no channel fee, only per-minute charges, with a cap on concurrent calls.
  • Burst channels: a base number of channels with extra capacity at peak, billed when used.

Model the options against a month of real call records, not the brochure. International and mobile destinations usually decide which plan is cheapest. To size the channel count, use our guide to how many simultaneous calls you need, remembering that internal calls never use the trunk. Each channel also needs bandwidth: about 87 kbps in each direction for a G.711 call, as our VoIP bandwidth guide calculates.

Choosing a provider: what to check

  1. PBX compatibility: is the provider tested with your platform? 3CX, for instance, publishes a list of supported SIP trunk providers with preconfigured templates.
  2. Numbers: can it supply numbers in every area or country you need, and port your existing ones? See keeping your business numbers.
  3. Emergency calling: how are addresses registered, and how are remote users handled?
  4. Codecs: G.711 is the safe common ground; ask whether G.729 or wideband codecs are supported. Our VoIP codecs comparison explains the trade-offs.
  5. Fax and tones: does it support T.38 fax relay, and does it send keypad tones (DTMF) as RTP events per RFC 4733, so menus on both ends recognize them?
  6. Security: IP allow lists, spend limits, blocking of destinations you never call and alerts on unusual traffic. Our guide to preventing toll fraud lists the controls to ask for.
  7. Resilience: more than one point of presence, and a rule that forwards calls to a backup number if your PBX is unreachable.
  8. Support and terms: support hours, access to call records, minimum term and how easily you can port numbers out.

Setting up a trunk: the overview

  1. Order the trunk, numbers and channels, and start any number port straight away, because porting often sets the go-live date.
  2. Collect the provider's details: SIP server, authentication method, credentials or IP addresses, number format (usually E.164, such as +44...) and supported codecs.
  3. Create the trunk on the PBX, using the provider template if there is one.
  4. Open firewall ports for SIP and RTP to the provider's addresses only, and disable SIP ALG on the router.
  5. Build inbound rules for each number and outbound rules for each destination type.
  6. Test inbound calls to every number, outbound local, mobile and international calls, caller ID display, keypad tones in menus, fax, failover and emergency calling, following the provider's test procedure.

Platform-specific steps for 3CX are in connecting a SIP trunk to 3CX.

Common SIP trunk problems

  • Registration fails: wrong credentials, a blocked port, or the provider expecting IP authentication instead.
  • One-way audio or calls dropping after about 30 seconds: nearly always NAT, firewall or SIP ALG. See one-way audio and dropped calls.
  • Wrong or missing caller ID: the number isn't verified with the provider, or it's in the wrong format or header.
  • Menus ignore key presses: a DTMF method mismatch between PBX and provider.
  • Faxes fail: a compressed codec on the fax path, or T.38 not enabled on both sides.

For how trunks fit into the wider phone system, see our business VoIP phone system guide.

How BtoBSkills can help

We set up and troubleshoot SIP trunks on 3CX, Yeastar, FreePBX and other platforms. Our VoIP support and configuration service covers trunk configuration, inbound and outbound call routing and fixing issues such as one-way audio or failed registrations. Request a quote and tell us your PBX and provider.