What equipment do I need to use SIP trunking?

SIP trunking runs on standard IT equipment instead of the dedicated telephone circuits an older phone system needed, so the core list is a SIP-capable phone system, endpoints for your people, a session border controller at the network edge, and an internet connection sized for the calls you make.[1][9] A gateway or analog adapter joins that list only when you keep analog phones or a legacy PBX that cannot speak SIP on its own.[5][6] None of it includes a physical trunk line, because the trunk is the service your provider delivers, not a box you install.[1]

The trunk is a service, not a box

The SIP trunk itself is not something you plug in. Your provider delivers it as a virtual connection over your internet link, using the Session Initiation Protocol to start, change, and end each call while the audio travels separately as Real-time Transport Protocol packets.[2][3] Because the trunk arrives as software rather than a physical line, the equipment question is really about what sits inside your building to originate calls and hand them to the provider cleanly.[1]

What decides how much you buy

How much equipment you actually own depends on one early decision: whether you run your own phone system or use a hosted one. An on-premises setup means you buy and maintain the IP-PBX, the session border controller, and the network gear that carries voice.[9] A hosted or cloud PBX moves most of that into the provider's data center, so the kit in your office can be as little as IP phones and a network that handles voice well.[9][14] Every deployment still comes down to three parts that have to talk to each other: a provider that carries your calls, a phone system that speaks SIP, and something at the border that secures and connects the two.[1][14] The sections below take each piece in turn.

The phone system is the one piece of equipment no SIP trunk can do without, because it originates and receives calls in SIP and hands them to the provider.[1] For most businesses this is an IP-PBX, which comes in three forms: a hardware appliance in a rack, software you run on your own server or a virtual machine, and a hosted PBX the provider operates for you.[9] The first two keep the system in your building, where you control it and carry the maintenance, while a hosted option removes most of that burden because the provider runs the platform and you connect phones to it.

The detail that trips people up is SIP compatibility. A system built for analog or PRI lines can still connect to a trunk, but it needs a gateway to translate its signaling first, and even a native IP-PBX can format SIP headers or negotiate codecs slightly differently from a given provider.[1][6] Those small mismatches are a common cause of one-way audio or calls that drop after a set time. Checking your PBX vendor's list of certified providers before you commit, or planning for a session border controller to reconcile the differences, saves a troubleshooting cycle after cutover.

Endpoints are the devices your team actually speaks into, and with SIP trunking they are IP based rather than analog.[4] A hardware IP phone looks like a normal desk phone but connects to your data network over Ethernet and registers to your phone system, while a softphone is an application that turns a computer or mobile device into the same thing.[4] Many organizations mix the two, giving desk phones to people who take calls all day and softphones to staff who are mobile or hybrid.

A practical point on hardware phones is power. Many draw electricity over the same Ethernet cable that carries their traffic through Power over Ethernet, so a switch that supplies PoE removes the need for a separate power adapter at every desk.[4][9] Endpoints are also where the codec choice shows up, since the phone and the provider have to agree on one for the call. G.711 delivers full narrowband quality at the cost of more bandwidth per call, while a compressed codec such as G.729 trades a little fidelity for lighter network use.[11][12] For a pure softphone deployment you may need no telephone hardware at all, only headsets and the network underneath.

A session border controller sits between your phone system and the provider, managing every SIP call that crosses the boundary of your network.[8] Most SBCs work as a back-to-back user agent, which means the device fully ends the provider's call leg and starts a fresh one toward your PBX, giving it authority over both sides of the call.[8] From that position it does jobs a plain firewall cannot: the IETF's requirements document groups them into perimeter defense such as access control and topology hiding, functions the endpoints lack such as NAT traversal and protocol repair, and traffic management such as media monitoring and quality of service.[7]

Whether you own one depends on how you deploy. An on-premises phone system almost always needs an SBC, either as a hardware appliance or as software on a virtual machine, because it is what protects an internet-facing phone system and smooths the header and codec differences between your PBX and the carrier.[7][9] With a hosted phone service the provider usually runs the SBC on its side, so a small office may never buy one. Sites with strict security requirements often keep their own regardless, so they set the policies at their own border.

A gateway or analog adapter is optional equipment that only matters when you are holding onto phones or a PBX that cannot speak SIP.[5][6] An analog telephone adapter, or ATA, connects traditional analog telephones and fax machines to an IP voice network through one or more foreign exchange station ports, so a fax machine or a lobby phone can keep working on a SIP trunk.[5] A VoIP gateway does the same job at larger scale, converting time-division voice from a PRI or T1 into the Real-time Transport Protocol packets an IP network carries.[6]

This piece is what lets a business migrate without replacing everything at once. A company with an older PBX built for PRI lines can put a gateway in front of it, connect the SIP trunk, and keep its existing handsets running while it plans a full move to IP.[6] The trade-off is that routing calls through a gateway adds a conversion step and can limit access to newer SIP features, so a gateway suits a transition better than a permanent design. Where every phone is already IP and every user can move to a softphone, you skip this equipment entirely.[4]

Voice on a SIP trunk shares your internet connection with everything else, so the connection and the gear around it are as much a part of the equipment list as any phone.[9] Each concurrent call needs roughly 85 to 87 kilobits per second in each direction with the common G.711 codec once IP, UDP, and RTP headers are counted, dropping to about 31 kilobits with the more compressed G.729.[11] Multiply your busy-hour concurrent calls by that figure, add headroom for the data traffic on the same link, and you have a floor for the connection to buy.[9]

The network gear matters as much as raw bandwidth. A business-grade router with quality-of-service settings lets you prioritize voice packets so a large download does not turn calls choppy, and a managed switch, ideally one that supplies Power over Ethernet, connects and powers the phones.[9] Unlike a PRI, where adding a twenty-fourth simultaneous call meant ordering another physical circuit, a SIP trunk scales in software over the connection you already have, so the ceiling is your bandwidth rather than a hardware limit.[10] A provider that reaches the public phone network also has to record the physical location of your equipment for 911, and that registered location has to stay current as devices move.[13]

The single biggest factor in what you buy is whether the phone system lives in your building or in the provider's data center, and each approach carries trade-offs worth weighing before you order hardware.[9]

On-premises deployments

Running your own IP-PBX and SBC gives you direct control over configuration, security policy, and how calls route, which suits organizations with complex needs or strict data requirements.[7][9] The cost is that you buy, secure, patch, and eventually replace that equipment, and you carry responsibility for its uptime.

Hosted and cloud deployments

A hosted or cloud PBX shifts the PBX and usually the SBC to the provider, so your equipment shrinks to phones and a solid network.[9] That lowers the upfront hardware bill and the maintenance load, though you depend on the provider's platform and configuration choices, and deep customization can be harder to arrange.

What to watch either way

Two things bite regardless of model. Voice quality depends on the network, so a link without quality-of-service settings or with too little headroom produces choppy calls under load no matter whose PBX runs them.[9][11] And because a trunk connects to the public phone network, 911 obligations follow you: the provider records the location of your equipment, and that record has to stay accurate as people and devices move, or an emergency call can route to the wrong place.[13]

SIP trunking removes several things older phone setups needed, and knowing what you can skip prevents over-buying.[1]

It does not need a dedicated phone circuit

A SIP trunk arrives over your existing internet connection, so there is no PRI, T1, or copper pair to order from the phone company.[1][10] Capacity that once meant installing another physical circuit is now a software change with your provider.[10]

It does not always need an SBC you own

An on-premises system almost always needs a session border controller, but a hosted phone service usually includes that function on the provider's side, so a small office may never rack one of its own.[7][8]

It does not require replacing your analog phones

Analog handsets, fax machines, and alarm lines can stay in place behind an adapter or gateway that converts their signaling to SIP.[5][6] Replacing them is a choice about features and tidiness, not a requirement of the trunk.

It is not the same as a hosted phone system

A SIP trunk connects a phone system you already run to the outside world, while a hosted PBX is the phone system itself delivered as a service.[1] The two are sometimes used together, and confusing them leads to buying equipment you do not need or skipping equipment you do.