What is the difference between SIP trunking and VoIP?

VoIP and SIP trunking sit at different levels of the same system, so comparing them head to head is a little like comparing 'motor vehicles' with 'a delivery van.' VoIP, short for voice over Internet Protocol, is the general set of technologies that carry voice as packets of data across IP networks such as the internet, in place of the dedicated circuits the traditional phone network used.[2] SIP trunking is one specific service within that category. It uses the Session Initiation Protocol to set up and end calls between a company's own phone system and a provider that reaches the public telephone network.[1][3]

The category and one of its members

A SIP trunk is always a form of VoIP, because the calls travel as data over IP.[3] The reverse is not true, since a business can run VoIP without ever buying a SIP trunk. A consumer calling app is VoIP, and so is a fully hosted business phone system that a provider runs end to end, yet neither is a SIP trunk.[2] SIP itself is a signaling protocol, meaning it handles the setup, changes, and ending of a call while the audio travels separately as Real-time Transport Protocol packets.[1][7] VoIP as a whole does not depend on any one protocol: SIP is the most common signaling method today, but H.323, MGCP, and various vendor-specific protocols also carry VoIP.[2][4]

The comparison most buyers actually mean

When someone asks about SIP trunking 'versus' VoIP, the useful question underneath is usually a SIP trunk against a hosted VoIP service, because those are two products you can genuinely choose between.[5] A SIP trunk keeps your existing phone system in place and connects it to the outside world, while a hosted VoIP service, sometimes called hosted PBX or UCaaS, moves the whole phone system into the provider's cloud.[9] The rest of this answer works through where the two diverge and how to tell which one fits.

VoIP names a whole family of technologies, while SIP trunking names a single service within that family.[2][3] This is the distinction that clears up most of the confusion, because people often treat the two as rival products when they belong to different levels. VoIP covers anything that carries voice as data over an IP network, from a consumer calling app to an enterprise phone platform.[2] A SIP trunk is one particular way to deliver business calling: a virtual connection, sold by a provider, that carries calls between your phone system and the public network.[3]

Getting this relationship right changes how you shop. If a vendor pitches 'VoIP or SIP trunking' as an either-or choice, they are usually comparing their hosted VoIP product against a SIP trunk, not the broad category against the service.[5] Knowing that lets you ask the sharper question, which is whether you want to keep and connect your own phone system or hand the whole system to a provider. The scope difference is also why every SIP trunk is VoIP but many VoIP services are not SIP trunks, a point the next difference makes concrete.[3][10]

SIP trunking always runs on the Session Initiation Protocol, whereas VoIP as a category can run on any of several signaling protocols.[1][2] SIP, defined by the IETF in RFC 3261, is an application-layer control protocol that creates, modifies, and ends calls and other sessions.[1] It handles the signaling only. The audio itself rides separately as Real-time Transport Protocol packets, which timestamp and sequence each slice of sound so the far end can reassemble it in order.[7] A SIP trunk is the commercial service built on top of that protocol, so the protocol is the ingredient and the trunk is the finished product.[8]

VoIP does not depend on SIP. The same job of carrying voice over IP can be done with H.323, the Media Gateway Control Protocol, or a vendor's own proprietary scheme, and some large consumer services use signaling the public never sees.[2] That is why the accurate way to state the relationship is that all SIP trunking is VoIP, but not all VoIP uses SIP.[4][5] For a buyer, the takeaway is that 'SIP' on a spec sheet tells you the signaling method, while 'VoIP' only tells you that calls travel over IP, so the two words answer different questions.

A SIP trunk connects a phone system you own and operate, while a hosted VoIP service moves that phone system into the provider's cloud.[5][9] With SIP trunking you keep an IP-PBX, either a physical box in a comms room or a virtual instance you run, and the trunk gives it a path to the public telephone network.[3][9] Your IT staff continues to manage the PBX, including its dial plans and features, and the provider is responsible only for the trunk and the numbers on it.[9]

A hosted VoIP service works the other way around. The provider runs the phone system in its own data center, delivers it to your handsets and apps over the internet, and takes on the servers, software updates, and maintenance for you.[9] Neither arrangement is better in the abstract, because the fit depends on what you already have and how much of the system you want to run yourself. Organizations with an existing PBX and the staff to maintain it often keep it and add SIP trunks, while teams that would rather not operate any phone infrastructure tend toward a hosted service.[5][9] This is the difference that usually drives the real decision, since it sets who owns the equipment and who carries the maintenance.

SIP trunking is typically priced by the concurrent channel, while hosted VoIP is typically priced by the user.[5][9] A channel is one simultaneous call path, so a SIP trunk buyer sizes capacity to how many calls happen at the busiest moment rather than to headcount.[5] A company with fifty employees rarely has fifty calls at once, which is why per-channel pricing can work out lower for organizations with an existing PBX and steady call volume.[5] Published rates for SIP channels commonly land around 15 to 25 dollars per channel per month, though they vary by provider and plan.[5]

Hosted VoIP instead charges a monthly fee for each named user, often somewhere around 20 to 35 dollars per user, which bundles the phone system, its features, and calling into one per-seat line item.[5][9] The per-user model tends to suit smaller teams that want predictable, all-inclusive billing and no hardware to run.[9] Because the two models count different things, comparing them fairly means translating both to your own numbers: how many concurrent calls you actually place against how many people need an extension. Price alone rarely settles it, since the maintenance burden of an on-site PBX belongs in the total just as much as the monthly invoice.[9]

Both options are VoIP underneath, so several practical details apply across the board and a few separate them.

The comparison itself can mislead you

Because VoIP is a category and a SIP trunk is a service, a head-to-head labeled 'VoIP vs SIP trunking' almost always means something narrower, usually a hosted VoIP product against a trunk.[5] Reading it literally can send you comparing a whole class of technology against one member of it, which is not a real decision. Pin down whether the choice on the table is keeping your own phone system or moving to a hosted one before you weigh features or price.

Both depend on internet and power

Any VoIP service, a SIP trunk included, stops working if the internet link or local power fails, unlike an analog line that draws power from the phone company.[2] Sites that cannot tolerate downtime plan for a backup connection, battery power, and a provider setting that reroutes calls to mobiles or another location when the primary link goes dark.

Emergency calling rules apply to both

A service that lets you call the public telephone network counts as interconnected VoIP under FCC rules, whether it is a SIP trunk or a hosted system.[6] That status brings duties around 911, including passing a call-back number and a validated location and telling users plainly when 911 might not work.[11] Keeping location records current is an ongoing task, not a one-time setup step.

Where the features live differs

With a SIP trunk, call features such as auto-attendants and routing live in the PBX you run, so changing them is your job.[9] With a hosted service, those features live with the provider and are configured in its portal.[9] That difference sets who you call when something needs to change, which matters as much day to day as the price.

The two terms get tangled in a few predictable ways, and separating them prevents buying the wrong thing.

A SIP trunk is not an alternative to VoIP

SIP trunking is a form of VoIP, not a rival to it, so a choice framed as 'VoIP or SIP trunking' compares a category with one of its own services.[5][10] The real alternatives to a SIP trunk are other ways of delivering business calling, such as a hosted phone system.[5]

SIP is not the same thing as a SIP trunk

SIP is the signaling protocol that sets up calls for many applications, including video and messaging.[1] A SIP trunk is a commercial service built on that protocol to carry voice between your phone system and a carrier, so the protocol is one component and the trunk is the packaged service.[3]

A SIP trunk is not a hosted phone system

With a SIP trunk you still run your own phone system, and the trunk only connects it outward.[9] A hosted phone system, sometimes sold as hosted PBX or UCaaS, moves the whole system into the provider's data center, so the two solve different parts of the problem and are sometimes used together.[9]

VoIP is not always SIP

Because VoIP can run on H.323, MGCP, or proprietary protocols, a service being VoIP does not mean it uses SIP.[2][4] When the signaling method matters, such as compatibility with a specific PBX or session border controller, confirm the protocol rather than assuming SIP.[8]