You've probably got a phone system that's been boringly reliable for years, which is exactly why it's easy to ignore. Then the letter lands, ISDN is going away, the desk phones still ring, and someone has to make a choice that won't embarrass the business when a line fails, a broadband circuit stumbles, or a branch keeps its old numbers and nobody can explain why inbound calls broke.
For a lot of UK SMEs, that choice gets reduced to a race through feature lists. That's the wrong test. SIP Trunking Providers should be judged on whether they keep calls flowing when the rest of the setup is under pressure, because the sale is easy, the outage is what you pay for.
Table of Contents
- Why SIP Trunking Is Now a UK Business Decision
- What SIP Trunking Actually Does for Your Business
- The Selection Criteria That Actually Matter
- UK SIP Trunking Pricing and Hidden Costs
- Your Migration Checklist From ISDN to SIP
- Matching Provider Profiles to Real UK Business Scenarios
- Common Pitfalls and How to Pressure-Test Any Provider
- Why a Local UK Support Partner Changes the Equation
Why SIP Trunking Is Now a UK Business Decision
A typical Essex SME does not wake up wanting a telecoms project. It has 15 staff, a reception line that still works, a few DIDs that everyone recognises, and a cabinet full of equipment that has done its job for years. Then the provider reminders start, the ISDN deadline becomes real, and the owner has to decide whether the business keeps its existing numbers, its current PBX, and its ability to answer calls if one part of the setup fails.
That makes this a business decision, not a telecoms hobby. Openreach stopped taking orders for ISDN services from 1 September 2023, with PSTN and ISDN switch-off planned by the end of 2025. Ofcom's migration updates on the UK telecoms switch from copper voice back that direction clearly. Copper voice is being retired, and leaving the move until the last minute is how clean migrations turn messy.
The real risk is downtime, not change
Most firms ask the wrong question first. They ask which provider is cheapest, or which one has the longest feature list. The better question is which supplier will keep inbound and outbound calling stable after the old line is gone. That means checking routing resilience, porting speed, and what happens when broadband or the PBX misbehaves.
Practical rule: if a supplier cannot explain how your calls continue during an outage, they are selling you a feature list, not a resilient voice service.
The wider UK market is already comfortable with IP voice. Ofcom reported that 74% of UK adults used VoIP or internet calling services in 2024, so SIP is not a fringe workaround. It is the replacement path the market has already normalised, and providers now have to prove they can carry real business traffic, not just demo calls.
Why this matters for revenue
When calls stop, businesses lose more than convenience. Missed inbound enquiries, failed branch routing, and broken CLI presentation all affect how customers experience your company. In practice, the provider that protects continuity is the one that protects revenue. That is the lens to use from here on, not the glossy brochure.
What SIP Trunking Actually Does for Your Business
A SIP trunk is a virtual phone line carried over your internet connection instead of a copper ISDN circuit. It connects your business phone system to the public telephone network through IP, so voice travels over the data network rather than a legacy line. That is the core job, and it is enough for most small businesses before they start comparing sip trunking providers.
What it replaces, and what it doesn't
SIP trunking replaces the telephone line side of ISDN. It does not replace your PBX, your handsets, your router, or your broadband circuit. If you still run an on-premises PBX, the trunk gives that system an IP route into the telephone network. If you have moved to a hosted PBX or cloud phone system, the SIP layer does the same job, with less hardware in the middle.
That flexibility matters because many SMEs do not want a full rip-and-replace. Some need to keep existing handsets and extensions for another cycle. Others want to move voice into a cloud platform while leaving the rest of the network alone. SIP trunking supports both approaches, which is why it fits so many migration paths.
Why the UK is moving this way
The UK government's 2024 business technology survey found that 85% of all UK businesses used at least one cloud computing service, and 28% used paid cloud services specifically for internet-based telephony or communications tools (UK business cloud adoption). It also showed that 63% of medium businesses and 76% of large businesses used cloud computing overall. That matters because SIP trunking sits neatly inside a cloud-ready communications stack.
SIP trunking works best when you already accept that voice is just another IP service. Once you think that way, provider selection becomes a resilience and support question, not a nostalgia contest.
The practical result is straightforward. If your business already uses cloud tools, remote work, or hosted telephony, SIP trunks fit well. If you are still on legacy lines, the switch-off makes the choice unavoidable.
The Selection Criteria That Actually Matter
Most comparison pages obsess over channel counts and gimmicks. I don't care about that first. I care about whether the provider can survive a local access fault, whether it ports numbers without chaos, and whether support staff understand what a broken call path looks like when a PBX or broadband link fails.
The seven checks I use on every shortlist
- QoS handling: Good providers are clear about traffic shaping, voice prioritisation, and what they expect from the access circuit. A weak answer sounds vague and shifts all responsibility to your internet connection.
- Redundancy and failover architecture: Good providers explain how calls move if one path fails, whether they offer multi-PoP or redundant routing, and what the service does during local access issues. A red flag is any supplier that says “our network is resilient” without describing the design.
- Codec support: Good providers match your PBX and your call profile. If they can't tell you which codecs they recommend and why, expect troubleshooting pain later.
- Number porting capability: Good providers are fast, accurate, and specific about porting existing DIDs. A bad one talks about sign-up speed and avoids the porting discussion.
- Pricing transparency: Good providers publish terms clearly enough that you can compare them properly. If the commercial model depends on a sales call, assume the quote will move.
- Security: Good providers discuss TLS/SRTP, fraud detection, and access controls without acting as if that's an upsell. A poor answer treats security as optional.
- SLA terms: Good providers show their service commitments in writing and can explain remedies. If the SLA is buried or fuzzy, expect the same fuzziness when something breaks.
UK SIP Trunking Provider Selection Criteria
| Criterion | What Good Looks Like | Red Flag |
|---|---|---|
| QoS handling | Clear guidance on voice prioritisation and circuit expectations | “Your internet should be fine” |
| Redundancy and failover | Native failover, redundant routing, sensible outage behaviour | No explanation of what happens if a path fails |
| Codec support | Compatibility guidance for your PBX and handset mix | “Standard SIP should work” with no detail |
| Number porting | Fast, documented porting with minimum disruption | Slow answers or unclear porting ownership |
| Pricing transparency | Easy-to-read commercial terms and clear inclusions | Quote-only pricing and hidden add-ons |
| Security | TLS/SRTP, fraud controls, and access restrictions | Security features treated as optional extras |
| SLA terms | Written commitments and support response clarity | Vague uptime claims with no practical detail |
The best providers answer these questions without getting defensive. The weak ones try to steer you back to features you didn't ask about. If a supplier can't discuss failover logic, porting discipline, and SLA wording, they're not ready for a live business circuit.
UK SIP Trunking Pricing and Hidden Costs
The headline rate rarely tells the whole story. UK SMEs get caught because they compare monthly numbers without asking how the service is billed, how numbers are ported, or what happens when fraud or failover issues appear. That's a quick route to a cheap-looking quote and an expensive support problem.
The main pricing models
Per-channel pricing means you pay for concurrent call capacity. That suits businesses with predictable call volume, but it punishes organisations that need bursts of capacity. Per-concurrent-call pricing is similar in effect, because the core issue is still how much capacity you reserve for busy periods.
Bundled minutes feel simple, but they can hide the actual cost of your call pattern. Bring-your-own-carrier, or BYOC, gives more control, but it only works if your team can manage the routing properly and the provider is honest about what's included. None of these models is automatically bad, but each one changes where the cost sits.
The costs that don't show up first
Number porting is one. If you're keeping existing DIDs, porting discipline matters more than a headline discount. Fraud exposure is another, especially if international calling is left too open or the provider doesn't enforce sensible controls. A broadband upgrade can also become part of the bill if the existing circuit isn't stable enough for voice traffic, and geographic number ranges across multiple sites can complicate pricing and support.
A useful benchmark for commercial clarity is examples of transparent pricing. Different market, same principle, if a supplier won't show the cost structure clearly, don't assume the missing detail is harmless.
Commercial rule: the cheapest SIP quote is often the one that assumes you won't ask hard questions about porting, failover, or fraud.
The provider you want is the one that can explain where every pound goes, what's optional, and what's unavoidable. That's especially true for UK SMEs with branches, inherited numbers, or mixed old and new telephony.
Your Migration Checklist From ISDN to SIP
The cleanest migrations I've seen don't start with a sales call. They start with a proper technical audit, because the first failure usually comes from a hidden assumption about broadband, routing, or the PBX. If you treat SIP like a quick swap, the cutover will punish you.
Start with the network and the PBX
Check whether your broadband has enough uncontested capacity for the number of simultaneous calls you expect. Then confirm the PBX is SIP-ready, because firmware, codec support, and call routing rules can make a supposedly simple migration awkward. Firewall and router settings matter too, especially if SIP ALG, port ranges, or voice prioritisation have been left in their default state.
Port numbers with care
Ofcom's General Condition C7 requires porting requests to be completed within one business day for fixed services where technically feasible, and the UK's geographic numbering framework keeps 01 and 02 numbers tied to location (porting and numbering context). That makes porting more than a paperwork task. It protects inbound continuity, CLI presentation, and the local number identity branches rely on.
Ask better trial questions
Use the trial to test failure behaviour, not just call quality on a good day. Ask how the service behaves if the broadband circuit drops, how the provider handles emergency location considerations, what fraud controls are active, and whether the SLA is published in writing.
- Broadband Audit: Check whether the circuit can carry voice cleanly under normal load.
- PBX Compatibility: Verify SIP readiness, firmware, and codec support before you touch production.
- Firewall and Router Review: Confirm the security and voice settings won't block or mangle traffic.
- Porting Plan: Arrange number transfer so inbound routing stays stable.
- Parallel Run: Test SIP alongside ISDN before the old service disappears.
That checklist gives you a defensible cutover, not just a hopeful one. If the provider can't support that process, keep looking.
Matching Provider Profiles to Real UK Business Scenarios
A 10-person London professional services firm doesn't need the same trunk design as a retailer with branches in Essex, and neither looks like a hybrid-working consultancy. The mistake is assuming one provider profile fits all. The better approach is to match the service model to how the business uses the phone.
A small office with steady inbound demand
A 10-person London office usually wants a handful of channels, clean inbound routing, and a simple path for call recording. It doesn't need exotic extras. It needs a provider that treats number continuity and support responsiveness as basic deliverables, because a missed main line call costs more than a feature it never uses.
A multi-site retailer with local numbers
A branch network in Romford, Chelmsford, and Brentwood has a different problem. Local 01 and 02 numbers matter because they anchor each branch to its own area identity, and any migration that makes those numbers flaky will be noticed immediately by customers. In that setup, I'd prioritise a provider profile that's strong on porting discipline and geographic number handling, not one that talks mostly about app integrations.
A hybrid consultancy with staff everywhere
A distributed consultancy lives or dies on routing stability across multiple broadband links. That means failover matters more than cosmetics. The provider profile to choose is the one that can survive home-office variation, keep call paths stable, and make troubleshooting clear when the network side changes.
Don't pick the trunk you'd buy for a brochure. Pick the trunk that behaves properly when one access line goes dark and the phone still has to ring.
The useful test is simple. If the business has one front door, choose for inbound reliability. If it has multiple branches, choose for number continuity. If staff are dispersed, choose for failover behaviour. That's a better fit than any generic “best provider” ranking.
Common Pitfalls and How to Pressure-Test Any Provider
The failures I've seen most often are boring in advance and expensive in production. A provider looks fine in a demo, the paperwork seems reasonable, and then a local access fault exposes weak routing or a support desk that can't explain what happened. The brochures never mention that part.
What usually goes wrong
Single-carrier dependency is a common trap. If everything relies on one route and that path fails, the business loses call continuity fast. Untested failover is almost as bad, because a supplier may advertise resilience but never show you how it behaves during a real interruption.
Codec mismatches cause ugly audio and intermittent call issues. Fraud is the nastiest surprise, because toll abuse can run up a bill before anyone notices. In other words, the problem is rarely the SIP concept itself, it's the weak service design around it.
How to pressure-test a provider
- Demand a documented failover test: Ask for a real description of what happens when the main path fails.
- Request written SLA terms: If the uptime and support commitments aren't visible, don't rely on verbal reassurance.
- Ask about fraud liability: You want to know who carries the risk and how controls are enforced.
- Trial with a geographic number: Test inbound routing on a number that matters to the business, not a throwaway route.
- Check who answers technical calls: If the first-line team can't read a SIP trace or explain routing, support will slow down when you need it most.
For support teams that deal with telephony issues regularly, for support teams is a useful place to compare how service standards are presented in adjacent communications markets. That kind of discipline is what you should expect from a trunk provider too.
The point is not to find perfection. It's to make sure the provider has already thought about the failure modes your business is going to hit.
Why a Local UK Support Partner Changes the Equation
For UK SMEs, a locally-supported provider changes the experience in a way feature sheets never capture. When a call path fails, you want someone who understands UK access networks, local number behaviour, and the difference between a routing issue and a line problem. That's why a provider with a UK footprint, engineering support, and a broader communications stack deserves serious attention.
A business like Networking2000 fits that model well because its portfolio covers VoIP telephony, internet connectivity, lines and calls, and phone system maintenance. That matters for SIP trunking because the trunk doesn't live in isolation, it has to work with the circuit, the PBX, and the wider support picture. Their extended support hours from 6am to 10pm, seven days a week, plus coverage across London and Essex, are the sort of operational details that reduce waiting around when something needs fixing.
The reason I value that kind of support is simple. A UK SME doesn't need a provider that only looks good in a quote. It needs one that can audit the existing setup, explain the trade-offs clearly, and help test the trunk against real failure conditions before the old line disappears.
If you're planning an ISDN migration and want a straight answer on resilience, porting, and support, speak to Networking2000. They offer VoIP telephony, internet connectivity, lines and calls, and phone system maintenance with UK-based support that fits this kind of migration properly. Book a conversation, compare your current setup against the checklist above, and get a SIP trunk plan that's built for how your business works.
