All articles
Buyer Guides 14 min read

What Is SIP Trunking? How It Works, What It Costs, and When You Need One

A rack-mounted phone system server on a dark desk, one braided cable from its back panel splitting into many glowing strands of light that stream into the haze

Short answer: SIP trunking is a phone line delivered over your internet connection instead of copper. It connects a phone system you own, usually an on-site PBX, to the public phone network. Each channel carries one call at a time, and you buy as many channels as you need.

If you are reading about SIP trunking, there is a good chance a phone carrier just told you your PRI or analog lines are going away, or an IT vendor quoted you "SIP" as the fix. Both can be true. But a SIP trunk is a fix for one specific situation: you own a phone system and you want to keep it. It is not the same thing as switching to a cloud phone system, and buying one when you needed the other is an expensive way to learn the difference.

Most of the pages that rank for this term are carrier sales pages, many written for the UK or Australia, that define the acronym and then list benefits. What they skip is the part a US business owner actually needs: how to size the trunk, what the bill is made of, and the four configuration jobs that land on you, not the provider, once the trunk is live.

Scope note: this page is about the trunk, meaning the line between your phone system and the outside world. If you are deciding whether to keep a PBX at all, start with what a cloud-based PBX moves to the provider. The wider choice between plain VoIP and a full platform is in UCaaS vs. VoIP, and the whole category is mapped in our business phone systems guide.

What is a SIP trunk?

SIP stands for Session Initiation Protocol, the signaling standard that sets up, changes and ends voice and video calls over IP networks. The current version was published by the Internet Engineering Task Force in June 2002 as RFC 3261, and almost every business phone system made since speaks it.

A trunk is old telephone language for a shared path that carries many calls between two switches, as opposed to a line that serves one phone. Put the two together and a SIP trunk is a shared, internet-delivered path between your PBX and a carrier, which hands your calls to and from the public switched telephone network (PSTN). The IETF specification for SIP (RFC 3261) describes the protocol as the signaling layer for creating, modifying and terminating sessions; the voice itself travels separately as RTP media packets.

Three terms you will see on every quote:

  • ▸Channel (or session, or call path). One simultaneous call. A trunk with 8 channels can carry 8 calls at once, in any mix of inbound and outbound. The 9th caller gets a busy signal or your overflow rule.
  • ▸DID (direct inward dialing) number. A phone number pointed at the trunk. You can have far more DIDs than channels; 40 staff with their own direct numbers can share 10 channels.
  • ▸ITSP. Internet telephony service provider, the carrier that sells the trunk. Some sell only trunks; others sell trunks alongside hosted phone service.

How does SIP trunking work?

The PBX does what it always did (extensions, transfers, the auto attendant, voicemail). Only the connection to the outside world changes. An outbound call follows this path:

  1. 1.A user dials a number. The PBX decides it is an outside call and picks the SIP trunk as the route.
  2. 2.The PBX sends a SIP INVITE message over your internet connection to the provider's session border controller, authenticated by IP address, credentials, or both.
  3. 3.The provider checks the caller ID you are presenting, signs it under the FCC's STIR/SHAKEN rules, and hands the call to the PSTN or another carrier.
  4. 4.When the far end answers, the voice flows as RTP packets between your PBX and the provider, usually using the G.711 codec (the same quality as a traditional landline).
  5. 5.Either side hangs up, a SIP BYE message ends the session, and the channel is free for the next call.

Inbound works in reverse: someone dials one of your DIDs, the carrier routes it to the provider, the provider sends an INVITE to your PBX, and your PBX's rules decide which phone rings. If your PBX or your internet connection is down, a good provider can send that call to a failover destination instead, such as a cell phone or a backup number. That setting lives at the provider, so configure it before the first outage, not during it.

SIP trunk vs. PRI vs. analog lines

SIP trunks mostly replace two older services. A PRI (primary rate interface) is a digital circuit, delivered on a T1, that carries 23 simultaneous calls plus one signaling channel. Analog lines (POTS) are individual copper pairs, one call each. Here is how they compare for a business that keeps its own PBX:

Analog lines (POTS)PRI (T1)SIP trunk
How it is deliveredOne copper pair per lineDedicated digital circuitYour internet connection
Calls per unit1 per line23 per circuit, bought as a block1 per channel, bought one at a time
Adding capacityNew line installAnother full circuitChange the channel count on the account
Moving officesReinstall everythingReorder the circuitPlug the PBX in at the new site (and update 911 addresses)
Outage behaviorWorks if the copper worksWorks if the circuit worksDepends on your internet; failover routing at the provider
FutureBeing retired by major carriersBeing retired along with legacy copperThe standard for PBX connectivity

The retirement row is why most people are here. Carriers are winding down copper networks and the services that ride on them, and the FCC has relaxed the rules that slowed that process. What that means for your lines specifically is in our guide to business landline phone service in 2026.

SIP trunking vs. hosted VoIP: which one do you actually need?

This is the decision that matters, and it has nothing to do with the trunk. It is about whether you want to keep owning a phone system.

Your situationUsually the better fit
PBX installed in the last few years, paid off, staff like itSIP trunks: keep the system, replace the lines
Large building already wired for an existing handset fleet, or a call center platform you rely onSIP trunks
PBX is old, out of support, or the person who understood it leftHosted phone system: retire the PBX
Staff work from home or move between officesHosted phone system (apps follow the user, not the wiring)
No one on staff or on contract to patch and secure a PBXHosted phone system
Rules or contracts require call processing to stay on your premisesSIP trunks with an on-site PBX

With trunks, you still own the PBX: its updates, its security, its backups, its hardware failures. With a hosted system, the provider runs the switching and you pay per user. (Talk Is Cheap is the hosted kind, not a trunk: it replaces the PBX rather than feeding it, from $14.99 per user per month on annual billing; see pricing and cloud voice.) Neither answer is wrong. Buying trunks to keep a PBX that is already failing is the common mistake.

How many SIP channels do you need?

Not one per employee. You need enough channels for your busiest moment, meaning the peak number of calls in progress at the same time, inbound and outbound combined, plus a margin. The best evidence is your own: most PBXs keep call detail records, and many carriers can report peak simultaneous calls on your current lines. Pull the busiest hour from the last few months, including any seasonal spike.

Then check that your internet connection can carry it. Cisco's per-call bandwidth table puts one G.711 call at 87.2 kbps in each direction on Ethernet at the default 20 ms packet size; a compressed codec such as G.729 uses far less, at some cost in audio quality. A quick way to size it:

Peak simultaneous callsG.711 bandwidth, each directionWhat to check
4about 0.35 MbpsEven modest business broadband carries this; the upload side is what to watch
10about 0.9 MbpsMake sure backups and cloud sync cannot saturate the upload
23 (one PRI's worth)about 2 MbpsPrioritize voice with QoS, or put voice on its own circuit

The numbers come from Cisco's voice bandwidth consumption reference, and they are the floor, not the target. Bandwidth is rarely what makes trunk calls sound bad; jitter, packet loss and a router that rewrites SIP traffic are. Those are diagnosed in our VoIP call quality guide. If calls do overflow, a queue or overflow rule beats a busy signal; see call queues and overflow.

What does SIP trunking cost?

Rate cards make SIP trunks look cheap because they quote one line item. The invoice has several. Providers price channels in one of two ways, and the rest of the bill is the same either way:

  • ▸Metered. A small charge per channel (or none) plus per-minute usage. Good for low or unpredictable call volume, painful in a busy month.
  • ▸Flat-rate channels. A fixed monthly price per channel with domestic calling bundled, usually under a fair-use policy. Predictable for steady volume. Read the fair-use clause: it is where the bundle ends.
  • ▸Phone numbers. A monthly fee per DID, and often a separate rate for toll-free numbers and inbound toll-free minutes.
  • ▸911. A monthly fee per number or per registered address for E911 service, plus state and local 911 surcharges.
  • ▸Taxes and regulatory fees. Federal Universal Service Fund charges and state telecom taxes appear on trunks just as on any phone service.
  • ▸One-time charges. Setup, porting, and sometimes a fee to configure the provider's side to work with your PBX model.
  • ▸Your side. Internet capacity, a firewall or session border controller that handles SIP correctly, and someone's time to configure and maintain the PBX end. This is the line item rate cards never show.

The fair comparison is total monthly cost for your real channel count and usage, against your current lines and against a hosted system priced per user. Real per-user price bands for hosted service are in what a business phone system costs in 2026. Ask every trunk provider for a sample invoice with taxes and 911 fees filled in.

Four jobs that stay with you after the trunk goes live

With a hosted system, the provider handles most of these. With trunks, your PBX is the phone system, so they are yours (or your IT provider's).

1. 911 dialing and location

Federal rules cover multi-line telephone systems, which includes a PBX on SIP trunks. Under Kari's Law, users must be able to dial 911 directly, with no prefix such as 9, and the system must notify a central point such as the front desk when someone does. Under the RAY BAUM'S Act, 911 calls must carry a dispatchable location: a street address plus the floor or suite where that matters. The FCC's summary of the MLTS 911 rules explains who is responsible. In practice that means mapping each extension or caller ID to a registered address at the provider, and updating it when people or phones move.

2. Caller ID that the far end trusts

Under STIR/SHAKEN, the provider that originates your call signs the caller ID with an attestation level. Full attestation requires the provider to know you are entitled to use that number. If your PBX sends a number the trunk provider does not know about, such as a main line still held by another carrier, the call can go out with lower attestation and is more likely to be labeled spam or blocked. The FCC's caller ID authentication page explains the framework. Fix: port the numbers you present to the trunk provider, or have them verify your right to use the ones you keep elsewhere.

3. Firewall and router settings

Many routers ship with a SIP ALG (application layer gateway) feature that rewrites SIP messages and breaks them, causing one-way audio and calls that drop after a fixed time. Turn it off unless your provider says otherwise. Allow SIP and RTP traffic only from your provider's published IP ranges, and give voice priority over other traffic.

4. Toll fraud

A PBX exposed to the internet gets scanned for weak SIP credentials within days, and a compromised trunk can run up international charges overnight. Lock the trunk to your public IP, use long random credentials, block international and premium-rate destinations you do not call, and ask the provider for a daily spending cap and fraud alerts.

If those four read like a part-time job, that is the honest trade-off of keeping a PBX. Houston-area offices that want trunks and do not want the firewall work can hand the network side to our sister company TMG, which handles network infrastructure and firewall management.

Questions to ask a SIP trunking provider

  1. 1.Is my PBX model and software version on your tested list, and do you have a configuration guide for it?
  2. 2.Is pricing metered or flat-rate per channel, and what does the fair-use policy say exactly?
  3. 3.Can I add or remove channels month to month, and how fast does a change take effect?
  4. 4.Do you support redundancy: more than one data center, and failover to a backup number or cell phone if my site is down?
  5. 5.How do I register 911 addresses per number or per extension, and what does E911 cost?
  6. 6.What attestation will my outbound caller ID get, and what do you need from me for full attestation?
  7. 7.Which codecs do you support, and do you support encrypted signaling and media (TLS and SRTP)?
  8. 8.What fraud controls do you offer: IP restriction, destination blocking, spending caps, alerts?
  9. 9.Who owns my numbers, and how fast do you release them if I port away?
  10. 10.Can I see a sample invoice for my channel count with every tax and fee included?

Moving carriers is a project with a cutover date, not a form. The sequence that avoids a dead-line morning (inventory, port timing, test calls, cancellation last) is in our checklist for switching business phone providers.

Frequently asked questions

Is SIP trunking the same as VoIP?
SIP trunking is one kind of VoIP. VoIP is the general method of carrying calls over an internet connection; a SIP trunk is the specific service that connects a phone system you run, usually an on-site PBX, to the public phone network using the SIP protocol. A hosted phone system is also VoIP, but there the provider runs the PBX and you do not buy a trunk at all. The wider map is in UCaaS vs. VoIP.

Do I need a SIP trunk for a cloud phone system?
No. A cloud or hosted phone system already includes the connection to the public phone network, so there is nothing to trunk. You need SIP trunks only when you keep running your own PBX, either a box in a closet or PBX software on your own server, and want to replace its copper or PRI lines with internet-delivered ones. How the hosted model divides the work is in our cloud-based PBX guide.

How many calls can one SIP trunk handle?
As many as it has channels, and you choose that number. Each channel carries one simultaneous call, inbound or outbound. The practical ceiling is your internet connection: one standard G.711 call uses about 87 kbps in each direction on an Ethernet network, so ten simultaneous calls need roughly 0.9 Mbps up and down, plus headroom for everything else on the line.

Is SIP trunking cheaper than a PRI?
Usually, because you buy channels in ones instead of a fixed block of 23 and you drop the dedicated circuit. But the real comparison is the whole bill: channels, per-minute usage if the plan is metered, a monthly fee per phone number, 911 fees, taxes, and the internet capacity and firewall work you need to carry the calls. Ask for a sample invoice, not a rate card.

Can I keep my phone numbers when I switch to SIP trunks?
Yes. Business numbers can be ported to a SIP trunking provider the same way they move between any carriers. Submit the port with the account name, service address and PIN exactly as the current carrier lists them, keep the old lines active until the port completes, and test inbound calls on every number before you cancel anything. The full sequence is in how to port a business number with no downtime.

Ready to stop overpaying for dial tone?

Get the whole platform — voice, text, video, AI — from $14.99 per user. Set up today, port your number free, cancel whenever. Talk is cheap; switching is even cheaper.