Your sales team hears static on half their outbound calls. Customers keep saying “you’re breaking up.” Conference calls turn into a game of guess what they said. So IT replaces the handsets. Then someone blames the internet and upgrades the plan. Then the PBX cops it.

And the calls still sound terrible, because the actual problem is sitting one layer further up: the SIP trunk provider carrying your voice traffic, the one company in the chain nobody thought to question.

Bad call quality isn’t random

It feels random, which is why it survives so long. In practice it follows patterns, and they trace back to how cheap voice providers build their networks. They pile too many customers onto shared links. They bounce your calls through third-party carriers to shave termination costs. They don’t prioritise voice traffic, so when the link gets busy, your phone call loses the fight against somebody’s video stream.

The technical symptoms have names. Jitter: packets arriving out of time, which you hear as robotic voices and echo. Packet loss: gaps where words used to be. A little of either makes conversation tiring. A bit more makes it impossible. The congestion behind them peaks at exactly the times that matter, Monday mornings and end of month, when everyone is on the phone at once.

Why the cheap trunk is cheap

That bargain per-channel rate is achievable because the provider is betting not all their customers will use the capacity at the same time. When the bet fails, your call quality is what pays out. Add codec conversion to squeeze bandwidth, plus long routing paths through other people’s networks, and you get a service that demos beautifully at 2pm on a Tuesday and falls apart under real load.

The part that actually breaks people: the carrier maze

Here’s the scenario we get called into. The IT team has done its homework. They can see the packet loss, they know it’s upstream, they’ve raised the ticket with evidence attached. What happens next is a masterclass in deflection: the ticket lands with a first-level team that asks them to reboot the router. Then it’s escalated to a different team that asks for the same logs again. Then the voice team says it’s a network issue, the network team says it’s a voice issue, and week three arrives with the case reassigned to someone new who opens with “so what seems to be the problem?”

Unless you’re one of the carrier’s top 50 accounts, this is the service you’re getting. They’re not being malicious. You’re just small to them, and their support structure is built to exhaust small.

This is where we earn our keep. Getting carriers to actually fix things is a skill: knowing which team really owns the fault, what evidence forces an escalation instead of a loop, which SLA clauses have teeth, and who to call when the process stalls. We manage these fights every week across dozens of clients, so we know the shortcuts through each carrier’s maze, and carriers respond differently to a party that manages a book of their business accounts. Your IT team gets their week back, and the fault gets fixed instead of reworded.

And if the trunk itself is the problem

Sometimes escalation confirms what you suspected: the provider’s network is simply not good enough, and no amount of ticket wrangling will make it so. Then the fix is moving your voice to a properly engineered network, with quality-of-service prioritisation, direct carrier interconnects, and an uptime SLA written into the contract. We handle that transition too: the porting, the cutover, and the contract terms that stop this happening again.

If your team is stuck in a carrier support loop right now, or you’ve stopped raising the tickets because nothing ever comes back, get in touch. Fighting carriers is a service we offer precisely because so few businesses have the leverage to win those fights alone.

Every business knows one of the stories. The company that ported its numbers and lost its 1300 line for two days. The office that switched internet providers and spent a week offline while two carriers blamed each other. The stories travel because they’re vivid, and they have a real commercial effect: businesses stay on overpriced contracts for years because switching feels like surgery with no anaesthetic.

Carriers know this. The fear of switching is priced into every renewal they offer you. If moving feels dangerous, they don’t have to be competitive, and that premium you pay for staying put, year after year, adds up to real money. It’s worth understanding what actually goes wrong in a switch, because none of it is bad luck. It’s all preventable, and the prevention is well understood.

Your numbers are yours

Start with the biggest fear: losing the phone numbers. The 1300 number on the billboards, the landline in every customer’s contacts. Those numbers belong to you, not your carrier, and Australian porting rules let you take them anywhere. The horror stories don’t come from the porting system; they come from preparation nobody did.

Ports get rejected for clerical mismatches: the business name spelled differently on the application than on the losing carrier’s records, an old account number, an unpaid final invoice the carrier uses to hold the port hostage. Each rejection resets the clock, and enough of them produce the two-days-of-dead-phones story. The other classic is the number that was quietly doing more than ringing phones: the line that also carried the EFTPOS terminal, the fax, or the security alarm. Port it without knowing that, and those services die with it.

All of this is discoverable in advance. Every field verified against the latest invoice before submission, every number audited for attached services, every outstanding balance settled or disputed before the port date. Done that way, ports overwhelmingly complete on schedule. Ours succeed on the first attempt over 99% of the time, and the ones that don’t are delayed, not lost.

Nobody needs to notice the cutover

The second fear is the outage: the moment between the old service stopping and the new one starting. A well-run migration doesn’t have that moment. The new service is built and tested while the old one still runs. Phones run in parallel, with calls forwarded or both systems live on the same numbers, until the new platform has proven itself. Internet cutovers are even gentler, because the new connection can carry test traffic for days before anything switches. The change happens outside business hours, with the old service kept alive as the escape hatch until the new one is confirmed.

One of ours from last year: a fifty-user phone system moved between providers on a Thursday evening. The business opened Friday morning with no idea anything had changed, except that the bill was lower.

What this means for your negotiating position

Here’s the practical point, and it matters even if you never switch. A business that can credibly leave negotiates completely differently from one that can’t. When your carrier knows the fear-tax doesn’t work on you, the renewal conversation changes: suddenly the retention pricing appears, the contract terms soften, the account manager returns calls. Being genuinely able to switch is leverage you hold in every negotiation for the rest of the relationship.

And sometimes the right answer is to stay, on better terms. We’re carrier-agnostic on principle: the point is never switching for its own sake, it’s that the decision should be driven by price and service, not by fear.

If a bad contract is holding you hostage

If you’ve stayed on a contract you know is bad because moving feels too risky, that’s exactly the situation we exist for. We run the whole switch: the pre-port audit, the carrier paperwork, the parallel running and the cutover, with your old service held live until the new one is proven. Talk to us about what you’re locked into, or start with a Telco Health Check to find out what staying put has been costing you.

When we run a voice audit, we don’t start with the phone bill. We ask for every cost related to telephony, wherever it lives in the accounts: the maintenance contract, the IT hours logged against handset problems, the capital spent on the PBX, the emergency technician callout from the day the phones died before a board meeting.

The pattern is remarkably consistent. The real monthly cost of business telephony comes out at 2.5 to 3 times the carrier invoice. A business paying $800 a month for its phones is usually carrying a telephony burden of over $2,000, and most of it never appears on anything labelled “phone bill”.

The maintenance contract that outlived its value

Somewhere in your accounts is a PBX maintenance contract, probably $300 to $800 a month depending on system size. It promises four-hour response and replacement parts. What it delivers, on the day you need it, is often a two-day wait for a technician who then discovers the part is obsolete and has to be sourced from overseas, while your receptionist forwards calls to her mobile.

These contracts auto-renew unless cancelled well in advance, often 90 days. Businesses keep paying them for years, partly through forgetting and partly through fear of being uncovered. Paying premium rates for insurance on hardware that’s becoming uninsurable is one of the purest forms of telco waste we see.

Line rentals from another era

Legacy voice lines still command premium rates because carriers know exactly how locked in their remaining customers feel. Businesses running banks of old-style line rentals for their call capacity are routinely paying $1,300 to $1,600 a month for what SIP trunking delivers for $400 to $600. The carriers are in no hurry to point this out.

The same era gave us the call rates. Contracts negotiated years ago still bill local calls by the minute and carry inbound charges nobody remembers agreeing to, while the current market standard is unlimited national calling included. If your voice contract hasn’t been to market in five years, your call rates are almost certainly above it.

Hardware depreciating in a cupboard

Then there’s the PBX itself. A $15,000 system bought to support 100 users, now serving 40, half of whom work from home and use it barely at all. The capacity was paid for up front and depreciates in the server room regardless of use. Cloud voice platforms invert this: you pay per active user, per month, and the number flexes with your headcount. For a shrinking or hybrid workforce, the difference compounds every year.

Adding it up honestly

Take the carrier bill, add the maintenance contract, the depreciation, the support hours and the occasional emergency, and the true number emerges. That’s the figure worth comparing against a modern alternative, and the comparison is rarely close. When we rebuild a voice environment (SIP capacity, calling inside Teams, no maintenance contract, no hardware), the ongoing cost typically lands well under the old carrier bill alone, before counting everything else that stops being necessary.

A Telco Health Check includes exactly this exercise: your full telephony cost assembled honestly, compared against what the same capability costs today. If your phone system is more than five years old, the number will be worth seeing.

Most Australian businesses are still running phone systems installed five to ten years ago. They work, mostly, which is why they survive. But the maintenance contracts get dearer, the parts get scarcer, and eventually someone has to answer the question: what do we replace this with?

That’s where it gets confusing, because the market answers with a pile of acronyms. Here are the actual options, in plain terms, and who each one genuinely suits.

Option one: keep the PBX, replace the lines

If your PBX is reasonably modern and supports SIP, you can keep the whole system and just swap the expensive legacy lines for SIP trunks, which carry calls over your internet connection instead of dedicated copper. Same handsets, same call flows, materially smaller bill. Line rental savings alone often run to hundreds a month.

This is the right move when the PBX still has life in it, the handset investment was recent, or your call routing is complex and hard-won. It’s a cost fix, not a modernisation, and there’s nothing wrong with that. The one prerequisite: your internet connection has to be good enough to carry voice cleanly, with quality-of-service configured, or you’ll trade line rental for call complaints.

Option two: hosted PBX

Here the box in the comms room goes away entirely. The phone system runs in the provider’s cloud, you pay per user per month, and handsets plug into the network wherever they are. Multi-site businesses get one system across every location. Nobody maintains hardware, and scale moves with headcount in either direction.

Platforms like 3CX sit in this family too, with a twist: 3CX is software you can host wherever you like, licensed by concurrent calls rather than per user, which can make it notably cheaper for businesses with many staff but few simultaneous calls. The trade-off is that someone has to own the platform’s configuration, so it best suits businesses that have IT capability and want the control.

Option three: calling inside Microsoft Teams

If your staff already live in Teams, the phone system can simply become part of it. Add PSTN calling to Teams and the separate phone platform disappears: one app for chat, meetings and phone calls, on the laptop and the mobile, with numbers, queues and voicemail all inside it. Licensing runs per user per month on top of your Microsoft agreement, and for organisations already paying for Microsoft 365, the incremental cost frequently undercuts running any separate voice platform at all.

There are a few routes to connect Teams to the phone network, ranging from Microsoft’s own calling plans to carrier programs like Operator Connect. They differ meaningfully in cost and flexibility, and the right one depends on your carrier situation and call volumes. (We’ve written more on that in our Operator Connect piece.)

How to actually decide

The pattern from the migrations we run: businesses with a solid recent PBX keep it and swap lines. Businesses with multiple sites, an end-of-life system, or no telephony expertise in-house go hosted. Businesses already deep in Microsoft 365 increasingly fold voice into Teams and stop thinking about phone systems altogether. And a hundred-line business moving off legacy line rentals saves tens of thousands a year under any of the three.

The wrong way to decide is on a provider’s brochure, because every provider’s brochure concludes you need what they sell. The costs that actually matter are your real ones: what the current system truly costs (including the maintenance contract and the hardware nobody counts), what your call patterns look like, and what your internet can carry. We do that analysis carrier-agnostically, then run the migration end to end: numbers ported, cutover staged, nobody’s Friday morning interrupted. Talk to us when the old system’s time is up, or before the next maintenance renewal locks you in for another year.

Your staff already spend their day in Microsoft Teams. Chat, meetings, the lot. What surprisingly few businesses realise is that Teams can also be the phone system: real numbers, real inbound and outbound calls to the public network, reception queues, voicemail, the works, in the same app on the laptop and the mobile.

When it’s set up well, the separate phone platform (and its bill, and its maintenance contract) simply ceases to exist. The question is how you connect Teams to the actual phone network, and that’s where the options split.

The three ways in, and why Operator Connect usually wins

Microsoft will sell you its own calling plans: simple, but per-user pricing runs high and call rates aren’t negotiable. At the other extreme is Direct Routing, where your own session border controllers link Teams to a carrier: maximally flexible, and an infrastructure project with ongoing care and feeding that most businesses have no appetite for.

Operator Connect is the middle path Microsoft built after watching everyone struggle with the other two. Certified carriers plug directly into the Teams platform; you pick one, numbers appear in your Teams admin centre, and the carrier owns the telephony layer. Local numbers, local call rates, carrier-grade voice, no hardware. For most Australian SMEs it’s the sweet spot on cost, control and simplicity, and you keep your existing numbers by porting them across.

What it costs, roughly

Two components: a Microsoft licence for phone functionality per user (already included in some enterprise plans, an add-on for the rest) and the carrier’s calling plan on top. All up, for a typical 50-user business, it lands well under what a traditional PBX with lines and maintenance costs, and it scales per user rather than per hardware upgrade. Add what disappears (the PBX replacement cycle, the maintenance contract, the separate conferencing bill) and the comparison usually isn’t close.

Where it goes wrong

This is the part the licensing pages don’t mention. The businesses that come to us mid-mess have usually hit one of these:

• The porting trap. Moving your numbers into Operator Connect is a real carrier port, with all the classic failure modes: mismatched account records, numbers with EFTPOS or alarms silently attached, rejections that reset the clock. Get this wrong and the business is uncontactable, which rather undermines the shiny new phone system.
• Emergency addresses. Australian regulation requires accurate emergency service addresses on every number. It’s mandatory, it’s audited, and it’s routinely skipped by DIY setups.
• Call flows nobody designed. A PBX accumulates years of routing wisdom: the after-hours behaviour, the overflow rules, who rings when reception is busy. Recreating that in Teams takes deliberate design, not defaults. The gap is invisible until the first missed customer call.
• A network that can’t carry it. Voice in Teams rides your internet connection. If the upload is already saturated or quality-of-service was never configured, you’ve moved your phone system onto your most congested asset.

The sensible path

None of those problems are exotic. They’re the standard failure modes of any voice migration, wearing a Microsoft badge, and avoiding them is a matter of doing the boring work in the right order: audit the current numbers and what’s attached to them, verify the network can carry voice, design the call flows on paper, port with parallel running, then cut over. That end-to-end job is what we do, carrier-agnostic, including choosing which Operator Connect provider actually suits your call volumes and rates.

If Teams calling is on your roadmap, or your phone system’s next maintenance renewal is coming and you’re wondering if there should even be a next one, talk to us before you’re locked in for another term.