SIP trunking: what a SIP trunk is, and why it replaced the old phone lines

Any business older than a decade has a comms cupboard somewhere with a dusty box, a few pairs of copper and an ISDN card nobody remembers commissioning. It works, so nobody touches it. Then comes the day you need five more lines for a campaign, or a second office, or simply to let the team answer from home - and every small change turns out to need a technician, a coordination call with the carrier and a two-week wait.

SIP trunking is what replaces that copper. Instead of a physical line terminating in your building, the connection between your phone system and the public telephone network runs over the internet using SIP - the same standard protocol every modern PBX already speaks. The PBX stays the PBX and the numbers stay the numbers; what changes is the pipe that feeds them, and with it everything that used to be hard to change.

Quick takeaways

• The idea: a SIP trunk is a virtual phone line - a logical connection over the internet that replaces analog and ISDN circuits and carries calls to and from your PBX.
• How it flows: the PBX registers with the provider, outbound calls route through it to the public network, and inbound calls to your numbers come back over the same connection - all encrypted and authenticated.
• Why it matters: add and remove channels without a technician, carry numbers from any country on one connection, and pay for what’s actually in use rather than what was installed years ago.
• The requirement: stable bandwidth with priority for voice traffic, a provider that configures failover up front - and an encrypted connection, not bare SIP exposed to the internet.

How it actually works - four parts

1. Registration with the provider. Your PBX identifies itself to the provider, typically with a username and password plus a list of authorized IP addresses. From then on there’s an open channel between the two carrying calls in both directions.
2. Channels, not users. One channel carries one concurrent call. Twenty employees who take turns on the phone don’t need twenty channels - they need whatever the busy-hour peak demands. This is the point where nearly every business coming off ISDN discovers it spent years paying for more than it used.
3. Numbers on the same connection. One SIP trunk can carry a local Tel Aviv number, a London number and a toll-free number without separate infrastructure for each. Number types determine how the business looks from outside, not how it’s connected.
4. Encryption and authentication. Signaling is encrypted with TLS and media with SRTP, so nobody can listen in or inject traffic into a call. A SIP connection exposed to the internet without encryption is an invitation to toll fraud - that’s a default, not a premium add-on.

Why businesses switch - and what actually changes

• Immediate elasticity. More channels is a configuration change, not a work order. Seasonal businesses, hiring drives and campaigns get exactly what they need in the week they need it.
• Cost that tracks usage. Instead of a fixed bundle sized to what was installed once, you pay for the channels and minutes in use. Our cloud PBX pricing guide breaks that structure into its parts.
• Geographic presence without offices. A local number in a country where you have no staff is a provisioning question, not a real-estate one.
• Resilience you can configure. A cut physical line takes the business off the air. A SIP connection reroutes - to a backup destination, to mobiles, to a second site - by rules set in advance.
• A foundation for what comes next. Once telephony speaks SIP, browser calling, recording, transcription and AI voice agents attach to it without replacing the infrastructure again.

What to check before signing

• Route quality, not just the per-minute rate. A cheap rate on a poor route shows up as dropped calls and caller ID that doesn’t survive the journey. The difference between CLI and non-CLI routes is exactly that difference, and our termination guide explains what happens to a call after it leaves you.
• What happens on a bad day. Ask to see the failover configuration, not just to hear that it exists. Who answers when the office trunk stops responding, and within how many seconds.
• Encryption on by default. TLS and SRTP enabled from the start, not “available as an add-on”.
• Spend caps and alerts. A daily spend limit and a breach alert are the cheapest protection against toll fraud there is.
• Porting your existing numbers. The move is only worth it if the number comes along. Our practical porting guide covers the process and the mistakes that stall it.
• Whether you need this at all. If you’re still deciding between a line and a full platform, the comparison is in UCaaS vs VoIP vs PBX.

How this looks with us

SIP.IO is our SIP trunking infrastructure: a carrier-grade connection with dynamic multi-carrier routing, end-to-end TLS and SRTP encryption, and channel allocation that grows and shrinks with what the business actually needs that month. The same connection can carry numbers from 130+ countries through DIDHub, and attaches to an existing PBX via a media gateway or directly to our cloud PBX, PBX.IM - so you can replace the lines now and the PBX when it suits you. All on infrastructure certified to ISO/IEC 27001, with failover configured at deployment rather than after the first outage.

Want to know how many channels your business actually needs - and what that means for the monthly bill? Talk to us - we’ll pull the peak concurrent calls from your existing system, translate it into the right connection, and handle the number porting alongside it.