What is SIP trunking?

SIP trunking carries your phone calls over an internet connection between your phone system and a provider that reaches the public telephone network, so you no longer buy the physical trunk lines a traditional setup required.[1][13] The name comes from the Session Initiation Protocol, the standard the industry uses to start, change, and end a call, whether that call is voice, video, or a mix.[2] A trunk in telephone terms is simply the shared link that connects a private phone system to the outside world, and with SIP trunking that link is a software session riding your existing data connection rather than copper pairs or a T1 circuit.[1]

Signaling and media travel separately

Two jobs run at the same time on every call. SIP does the signaling, which means it locates the far end, negotiates which audio formats both sides can handle, and then connects or ends the call as the conversation requires.[2] The voice itself does not travel inside SIP. Once both ends agree, the audio flows as Real-time Transport Protocol packets, which timestamp and sequence each slice of sound so the far end can play it back in order.[3] Splitting the two lets a provider route a call intelligently while the audio takes the most direct path.

Where the provider fits

Between your building and the public phone network sits an internet telephony service provider, usually shortened to ITSP.[1] Your phone system hands each outbound call to that provider over the SIP trunk, and the provider passes it into the wider phone network so it can reach any mobile or landline number, with inbound calls traveling the reverse route.[4] Most business deployments place a session border controller at that boundary, a device or software instance that ends the provider's session and starts a fresh one toward your PBX, which gives it control over security and call formatting on both sides.[4][5]

A SIP trunk needs a phone system that can speak SIP, which for most businesses is an IP-PBX. This is the on-premises or virtual system that routes internal calls, applies dialing rules, and hands outbound calls to the trunk.[1] Older PBX equipment built for analog or PRI lines can still work, but it needs a gateway that converts its signaling into SIP before the call reaches the provider. The point that matters for planning is compatibility, because not every PBX implements SIP the same way, and small differences in how each side formats headers or negotiates codecs are a common cause of one-way audio and dropped calls.[5] Before you commit, check your PBX vendor's list of certified providers, or plan for a session border controller to reconcile the differences, since sorting this out in advance avoids a painful troubleshooting cycle after cutover.

The provider, formally an internet telephony service provider, is the company that carries your calls between the trunk and the public phone network.[1] It assigns your phone numbers, routes calls to and from other carriers, and bills you for capacity or usage. Providers differ in ways that affect both cost and reliability, including the geographic footprint where they hold numbers, whether they price by channel or by the minute, how they handle number porting, and whether emergency calling is bundled or sold separately.[9] Because the provider becomes the path for every call your business makes, it is worth asking how their network is built, whether they operate their own connections to the phone network or resell someone else's, and what their record is on outages. A provider that reaches the public network also carries regulatory duties for 911 and caller identification, so confirming they meet those obligations protects you as much as them.[10][11]

A session border controller sits at the edge of your network and manages every SIP call passing between your phone system and the provider.[5] It works as a back-to-back user agent, which means it fully ends the provider's session and starts a new one toward your PBX, giving it authority over the call on both legs.[4] That position lets it do several jobs a plain firewall cannot: it hides your internal network layout, blocks malformed or hostile SIP traffic, translates between codecs when the two sides do not match, and handles the address translation that lets private IP phones reach a public provider.[5] The IETF's requirements document for SBC deployments groups these functions into perimeter defense, connectivity fixes such as NAT traversal, and traffic management like media monitoring and quality of service.[5] For a small setup the provider may supply this function from the cloud, while larger or security-sensitive sites often run their own SBC so they control the policies at their border.

Voice quality on a SIP trunk depends on the internet connection carrying it, so sizing bandwidth to your call volume is part of the setup rather than an afterthought.[8] Each concurrent call needs roughly 85 to 87 kilobits per second in each direction with the common G.711 codec, once the IP, UDP, and RTP headers are counted on top of the 64 kilobit payload.[7][8] A more compressed codec such as G.729 drops that to about 31 kilobits per second per direction at a small cost in fidelity, which helps where bandwidth is tight.[8] Multiply your busy-hour concurrent calls by the per-call figure, add headroom for the data traffic sharing the link, and you have a floor for the connection you need. Voice is sensitive to delay, jitter, and lost packets, so prioritizing call traffic with quality-of-service settings on your network is what keeps audio clean once the link gets busy.[8]

A SIP trunk is sized in concurrent call paths, also called channels, which is the number of calls you can run at the same time rather than the number of phones or numbers you own.[6] A company with fifty employees rarely has fifty calls happening at once, so the useful measure is how many simultaneous calls you place at your busiest hour, plus a little headroom.[6] Separate from channels are your direct inward dial numbers, the individual phone numbers that route to specific people or departments, and you can hold far more numbers than channels because most of them sit idle at any given moment.[9] This split is one of the practical advantages of SIP over a PRI, where numbers and capacity were bound to the physical circuit. With a trunk you can carry hundreds of numbers on a handful of channels, and you can raise the channel count for a seasonal peak and lower it again without touching hardware.[6]

SIP trunk pricing follows two main models, and which one fits depends on how predictable your call volume is.[9] Channel-based plans charge a flat monthly fee per concurrent call path, commonly in the range of 15 to 30 dollars per channel for unlimited domestic calling, which suits businesses with steady, high call volume that want a predictable bill.[9] Metered plans instead charge per minute, often around one to three cents a minute, which works out cheaper for organizations whose lines sit quiet much of the day.[9] On top of either model you pay a small monthly fee for each phone number, commonly about a dollar per number, with enhanced numbers that include emergency calling costing more.[9] A common mistake is buying a channel for every phone, because capacity is measured in simultaneous calls, so most businesses need far fewer channels than handsets, and right-sizing that number is where the savings over a PRI actually come from.[6][9]

SIP trunking depends on your internet connection and exposes your phone system to the public network, so a few limits deserve planning that a legacy circuit did not require.

Toll fraud and security

Because a SIP trunk connects to the internet, an exposed or misconfigured system can be found and abused by attackers who route expensive international calls through it. Telecom fraud is not a small problem: the Communications Fraud Control Association estimated 38.95 billion dollars in global losses in 2023, up 12 percent from two years earlier, with PBX fraud among the top methods reported.[12] Strong credentials, closed unused ports, encryption of signaling and media, and provider-side limits on call destinations and spending are the usual defenses.

Dependence on internet and power

A SIP trunk stops working if the internet link or local power fails, unlike an analog line that draws power from the phone company. Sites that cannot tolerate downtime pair the trunk with a backup connection and battery power, and configure the provider to reroute calls to mobiles or another site when the primary link goes dark.

Emergency calling obligations

A provider that lets you call the public phone network is an interconnected VoIP service under FCC rules, which means 911 calls must carry a call-back number and a validated location, and subscribers have to be told plainly when 911 might not work, such as during an outage.[10][11] Because a trunk can serve numbers registered at different addresses, keeping location records accurate for each number is an ongoing responsibility rather than a one-time task.

Call quality under load

Voice shares the connection with everything else on your network, so a link that is fine for email can still produce choppy calls when it saturates. Prioritizing voice traffic and keeping enough headroom for the number of concurrent calls is what prevents that.[8]

SIP trunking is one specific way to deliver business phone service, and it gets confused with several neighboring ideas.

It is not VoIP in general

VoIP is the broad category of carrying calls over IP networks, and SIP trunking is one form of it aimed at connecting a phone system to the public network.[1] A softphone app or a hosted phone system is also VoIP, yet neither is a SIP trunk.

It is not a hosted or cloud phone system

With SIP trunking you still run your own phone system, on-site or virtual, and the trunk only connects it outward.[1] A hosted PBX or UCaaS product moves the whole phone system into a provider's data center, so the two address different parts of the problem and are sometimes used together.

It is not the SIP protocol by itself

SIP is the signaling standard that sets up calls for many applications, including video and messaging.[2] A SIP trunk is a commercial service built on that protocol to carry voice between your system and a carrier, so the protocol is the ingredient and the trunk is the finished service.

It is not a PRI

A PRI is a physical digital circuit with a fixed channel count, while a SIP trunk delivers the same connectivity as software over your internet link.[6] Both connect your phones to the outside world, but only the SIP trunk scales without new hardware.