SIP trunking connects an existing on-premises phone system (PBX) to the internet and is typically priced per channel (concurrent call), while hosted VoIP is a fully cloud-based phone system priced per user. If you already own a capable PBX, SIP trunks usually cost less; if you have no on-site kit or a remote team, hosted VoIP is simpler. Which fits depends on your current hardware, call volumes and where staff work.
The context: why this choice matters now
Picture a London accountancy firm whose ISDN lines are being switched off. The partners don't care about protocols — they want calls to work on Monday, staff to answer from home, and one predictable bill. With the PSTN switch-off continuing across the UK, every traditional phone line must move to an internet-based alternative, and the two main routes are SIP trunking and hosted VoIP.
Both carry calls over your data connection rather than the old copper exchange network. The difference is where the 'brain' of the phone system lives. With SIP trunking, the intelligence stays in a PBX you own and run. With hosted VoIP — also called cloud PBX — that intelligence lives in the provider's data centre and you simply log in.
Get the choice right and you cut cost, add flexibility and simplify support. Get it wrong and you pay for capacity you don't use, or you scrap perfectly good hardware you'd already paid for.
What SIP trunking and hosted VoIP actually are
SIP trunking is a service that delivers phone lines to an existing PBX over the internet using the SIP protocol. It replaces ISDN or analogue lines without replacing your phone system. A 'trunk' is a bundle of channels, and each channel carries one concurrent call — so 10 channels means up to 10 simultaneous calls, regardless of how many handsets you own.
Hosted VoIP is a complete cloud-based phone system. There's no PBX on your premises; the provider hosts everything and you connect handsets or softphone apps to it. It is not simply 'calls over the internet' — it bundles the full feature set (auto-attendant, queues, voicemail-to-email, call recording) as a managed service you consume per user.
The short version: SIP trunking is lines for a system you already have. Hosted VoIP is the system and the lines together. Our SIP trunking and cloud hosted PBX pages set out both in more detail, and many firms now fold voice into Microsoft Teams with a Teams phone system.
Cost comparison: per-channel vs per-user pricing
The pricing models differ in a way that drives the whole decision. SIP trunking is usually charged per channel plus call costs, with indicative UK pricing in the region of £5–£12 per channel per month. If 60 staff share a PBX but rarely have more than 15 calls running at once, you might only buy 15–20 channels — so you pay for concurrency, not headcount.
Hosted VoIP is charged per user, with indicative UK pricing of roughly £8–£20 per user per month depending on the feature tier and whether calls are inclusive. Every person who needs an extension is a licence, whether or not they're on a call. For a 60-person site that can mean 60 licences.
These are indicative guides, not quotes — your real figure depends on handsets, number porting, call bundles and contract length. The rule of thumb: a large team with modest concurrent call volumes often works out cheaper on SIP trunks, while small-to-medium teams and contact-style operations frequently land better on per-user hosted VoIP once you factor in avoided hardware and maintenance.
- SIP trunking: per channel (concurrent call), roughly £5–£12/channel/month — best when concurrency is far lower than headcount.
- Hosted VoIP: per user/licence, roughly £8–£20/user/month — best when most staff need their own feature-rich extension.
- Don't forget one-offs: PBX maintenance and licensing (SIP) versus handset purchase or softphone apps (hosted).
- Number porting of existing UK numbers is usually a small one-off cost either way.
When SIP trunking makes sense
SIP trunking is the strong choice when you already own a capable, reasonably modern PBX that isn't due for replacement. If you've recently invested in on-premises phone hardware, trunks let you drop the old ISDN lines and keep the system you've paid for — extending its life rather than writing it off.
It also suits organisations with high headcount but lower concurrent call volumes, because you buy channels rather than per-person licences. A manufacturer, warehouse or professional-services office where only a fraction of staff are on the phone at any moment can see meaningful savings.
Finally, SIP trunking appeals where you want tight control over call routing, specific integrations, or on-site features your PBX already provides. The trade-off is that you remain responsible for the PBX — patching, resilience and support — so it works best for firms with in-house IT or a co-managed IT support arrangement to share the load.
When hosted VoIP wins
Hosted VoIP is the natural fit when you have no on-premises phone equipment, or your PBX is end-of-life. There's nothing to buy, rack or maintain; you add users in a portal and plug in handsets or use the desktop and mobile apps. For a new office or a business avoiding capital outlay, that simplicity is the point.
It also wins for remote and hybrid teams. Because the system lives in the cloud, staff get the same extension, voicemail and call-handling features from home, a café or a client site — exactly the flexibility the switch to internet telephony is meant to deliver. Adding or removing users as the business flexes is a portal change, not a site visit.
Hosted VoIP removes a whole class of maintenance, upgrades and single-site risk from your shoulders. If your organisation already lives in Microsoft 365, routing calls through a Teams phone system with support from our Microsoft 365 support team keeps voice, chat and meetings in one place.
Which is more resilient if your internet goes down?
Both SIP trunking and hosted VoIP depend on your internet connection — that's the honest answer. If the line drops, on-site handsets lose service in either model. The real difference is in how easily calls can be rerouted and how you engineer the connection underneath.
Hosted VoIP often has an edge for failover because the system itself stays up in the cloud. If your office connection fails, inbound calls can automatically divert to mobiles or a backup site, and staff can keep working from the mobile app on 4G/5G. With SIP trunking, failover depends on what your provider and PBX support — usually divert-on-failure to a mobile or alternative number.
The decisive factor isn't the phone technology — it's the connectivity. For business-critical voice we'd pair either option with a dedicated leased line for guaranteed bandwidth, add backup connectivity such as a second circuit or 4G/5G, and use SD-WAN to prioritise voice traffic and switch paths automatically. Resilience is bought at the network layer, whichever call model you choose.
Making the decision for your London business
Start with three questions: Do you own a PBX worth keeping? How many staff need their own extension versus how many calls run at once? Where do people actually work? Your answers usually point clearly to one model — SIP trunks to extend existing kit with low concurrency, hosted VoIP for a clean slate or a distributed team.
Then factor in the total picture, not just the monthly line. Include PBX maintenance and in-house IT time for SIP, or avoided hardware and simpler support for hosted. A five-year view often changes a decision that looked close on the first invoice.
If you'd like a straight recommendation, our team can review your current setup, number inventory and call patterns and map the costs both ways. Talk to us through connectivity and telecoms or contact us — we run connectivity, phones and support as one accountable team, so you get one number and one invoice rather than finger-pointing between vendors.
