SIP Trunking Explained: How It Replaces Traditional Phone Lines
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 line | Calls at once | How you add capacity |
|---|---|---|
| Analog line | 1 | Order another physical line |
| ISDN BRI | 2 | Order another BRI circuit |
| ISDN PRI on an E1 (most of the world) | 30 | Order another E1 circuit |
| ISDN PRI on a T1 (North America) | 23 | Order another T1 circuit |
| SIP trunk | Any number of channels you buy | Change 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:
| Registration | IP authentication | |
|---|---|---|
| How it works | Your PBX registers with a username and password, like a phone registering to a PBX | The provider accepts calls only from your fixed public IP address and sends inbound calls there |
| Needs a static IP | No | Yes |
| Main risk | Stolen credentials can be used to place fraudulent calls | Misconfigured firewall rules; failover to another site needs provider changes |
| Typical fit | Small offices, dynamic IP connections, hosted PBXs | Fixed 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
- PBX compatibility: is the provider tested with your platform? 3CX, for instance, publishes a list of supported SIP trunk providers with preconfigured templates.
- Numbers: can it supply numbers in every area or country you need, and port your existing ones? See keeping your business numbers.
- Emergency calling: how are addresses registered, and how are remote users handled?
- 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.
- 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?
- 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.
- Resilience: more than one point of presence, and a rule that forwards calls to a backup number if your PBX is unreachable.
- 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
- Order the trunk, numbers and channels, and start any number port straight away, because porting often sets the go-live date.
- Collect the provider's details: SIP server, authentication method, credentials or IP addresses, number format (usually E.164, such as +44...) and supported codecs.
- Create the trunk on the PBX, using the provider template if there is one.
- Open firewall ports for SIP and RTP to the provider's addresses only, and disable SIP ALG on the router.
- Build inbound rules for each number and outbound rules for each destination type.
- 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.
Frequently asked questions
Do I need a special internet connection for SIP trunking?
What is the difference between a SIP trunk and a hosted PBX?
Can I use more than one SIP trunk provider?
Is SIP trunking secure?
How quickly can I add channels?
Related services
-
VoIP Support Configuration $200.00
Related articles
- What Is an IP PBX and How Does It Work?
What's inside an IP PBX, how a call is set up and carried step by step, how it connects to SIP trunks and analog lines, and the setup mistakes to avoid.
- Moving from Analog or ISDN Lines to VoIP: A Migration Checklist
A step-by-step checklist for moving from analog or ISDN lines to VoIP: switch-off dates, special devices like alarms and lift phones, numbers, power, testing and cutover.
- How Many Simultaneous Calls Does Your Business Need?
What counts as a simultaneous call, how to measure your busiest hour, a worked Erlang B example and how to turn the result into a 3CX license or Yeastar capacity.
- How Much Bandwidth Does VoIP Need? A Practical Calculation
Per-call bandwidth for G.711, G.729, G.722 and Opus, the header math behind it, what packet size and encryption add, and a worked example for a whole office.
- VoIP Codecs Compared: G.711, G.729, G.722 and Opus
How G.711, G.729, G.722 and Opus differ in sound quality, bitrate, loss handling and compatibility, and the codec order to use on phones, trunks and apps.
- VoIP Security: How to Prevent Toll Fraud and SIP Attacks
How attackers use hacked phone systems to run up call charges, the controls that stop them on 3CX, Yeastar and FreePBX, and what to do if you're hit.
- One-Way Audio and Dropped Calls: NAT, SIP ALG and Firewall Fixes
Why NAT, SIP ALG and firewall rules cause one-way audio and calls that drop at 32 seconds, the settings that fix them and a step-by-step way to find the fault.
- Business VoIP Phone Systems: The Complete Guide for SMEs
How a business VoIP phone system works, the deployment and licensing choices you'll face, what your network needs, and how to switch without losing calls or numbers.
Sources
- IETF RFC 3261: SIP: Session Initiation Protocol (accessed 2026-11-19)
- SIP Forum: SIPconnect Overview (accessed 2026-11-19)
- Openreach: Time for a big switch up as PSTN switch off looms (5 February 2026) (accessed 2026-11-19)
- IETF RFC 3325: Private Extensions to SIP for Asserted Identity within Trusted Networks (accessed 2026-11-19)
- IETF RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals (accessed 2026-11-19)
- 3CX Supported SIP Trunk Providers with pre-configured templates (accessed 2026-11-19)

