What Is a Hosted PBX? Porting Your AU Number
- stfsweb
- 1 day ago
- 11 min read
A Hosted PBX is a cloud-based business phone system where the switching and call routing live in remote data centres instead of a box in your office. In Australia, that shift has moved fast: the hosted PBX market passed USD 5 billion in 2020 and was projected to grow at over 12% CAGR between 2021 and 2027, while over 70% of Australian businesses with 5–199 employees used internet-based communication tools in 2022, up from roughly 45% in 2017 (hosted PBX market overview).
If you're reading this, there's a fair chance your current phone setup is annoying someone every day. Calls ring out on an old desk phone no one sits near anymore. Staff forward business calls to personal mobiles. A number you've had for years is tied to a service nobody fully understands. You want to modernise, but you don't want to lose your main number or break the phones on a Monday morning.
That's where most Australian small businesses start. The question usually isn't just what is a Hosted PBX. It's whether you can move your existing numbers across without chaos, missed calls, or a drawn-out fight with your current carrier.
You can. But the smooth jobs are the ones that get prepared properly before anyone submits a port.
Why Australian Businesses Are Moving to Hosted PBX
A traditional PBX sits on-site. It uses local hardware, old line infrastructure, and usually a mix of settings that only one technician remembers. A Hosted PBX moves that call control into the cloud and delivers the service over your internet connection.
For a small business, that changes the day-to-day reality more than the technical definition suggests. Staff can answer the main business number from a Yealink desk phone, a laptop softphone, or a mobile app. A receptionist can transfer calls to a home-based employee as easily as someone at the next desk. Adding a new extension becomes an admin task, not a hardware project.
What changes in practice
The biggest shift is operational. You stop treating telephony like a special, fragile office utility and start treating it like a managed business service.
Hosted PBX can save time and money and give staff flexible working locations.
That matters because many Australian businesses aren't operating from one fixed reception desk anymore. They have hybrid staff, a warehouse and an office, a second site, or a manager who needs to take calls while travelling between jobs.
According to an ACMA-linked market summary, over 90% of Australian business voice services had moved off copper, and organisations adopting hosted solutions reported an average 25–35% reduction in monthly voice line and maintenance costs over three years. The same source notes that running multiple sites on a single virtual PBX reduces per-site configuration effort and supports flexible work locations (Australian shift to hosted voice).
Why owners usually move
Some businesses move because the old system is failing. Others move because they want features they should've had years ago.
A Hosted PBX usually makes sense when you need:
One business identity across locations so calls to the main number can ring the right person wherever they are.
Less hardware overhead because you don't want to maintain an ageing on-premise phone system.
Simpler changes when staff join, leave, or move roles.
Better fit for modern work where desk phones, softphones, and mobile access all matter.
If you're still weighing the broader options, this guide to cloud phone systems is a useful companion read because it helps separate the sales language from the practical business impact.
Preparing for a Smooth Switch to a Hosted PBX
The porting process usually goes wrong before the form is even submitted. Not during the cutover. Not during activation. It goes wrong when a business assumes any internet service will do, or when nobody has a clean list of the numbers being moved.
Check whether your internet is actually ready
Hosted PBX lives and dies on call quality. That doesn't mean you need an exotic connection, but you do need one that's suitable for voice.
Australian broadband conditions vary more than many providers admit. The ACCC's 2023–24 Measuring Broadband Australia reporting highlighted that upload speeds, which matter for VoIP, are often uneven, with many premises receiving less than 10 Mbps upload. That matters even more on services such as Fixed Wireless and Sky Muster, where latency can also become a factor (Australian broadband conditions and VoIP readiness).
A practical rule from the field is simple. Work out how many concurrent calls you expect, not how many staff you employ. Then size the connection around that. The verified guidance for hosted PBX deployment is to allow at least 100 kbps per concurrent VoIP call. If a business under-allocates bandwidth and skips a dedicated voice VLAN, it can run into 3–5% packet loss and poorer call quality, including MOS scores below 3.5 (hosted PBX implementation guidance).
Practical rule: Test your busiest hour, not your quietest one. If your internet sounds fine at 3 pm on a Friday but falls over at 9 am on a Monday, that's the result that matters.
Audit the services before you touch them
Before you port anything, gather the actual service picture. Not the version in someone's head.
Check:
Every number in use. Main numbers, direct inward dial numbers, fax lines still connected to EFTPOS or alarms, and hunt groups.
The current account holder details. The carrier will validate against their records, not what your website says.
Whether numbers are bundled with internet, alarm monitoring, EFTPOS, or another carriage service.
Any minimum terms or cancellation rules that could affect timing.
A quick review of your current connection type also helps. If you're not sure whether you're on FTTN, FTTP, HFC, Fixed Wireless, or something else, this plain-English explainer on internet connection types is worth checking before you commit to voice over that link.
Decide what stays and what goes
Not every service should be cut over on day one. That's a common mistake.
Keep a simple planning table:
Service item | Move now | Check first |
|---|---|---|
Main advertised business number | Yes | Confirm account details |
Direct numbers for staff | Usually | Confirm if all are still needed |
Fax or analogue device lines | Maybe not | Check if device can be replaced or adapted |
Alarm or lift phone line | No assumption | Confirm compliance requirements with vendor |
This is also the point to set your call flow. Decide where the main number should ring, what the after-hours greeting says, who receives voicemail to email, and whether your team will use desk phones, softphones, or both. Businesses that leave those questions until the port date often confuse a successful number transfer with a poor system setup.
Gathering Your Authorisation and Documentation
Most rejected ports come down to admin, not technology. The number can be perfectly valid. The new Hosted PBX can be ready. But if the paperwork doesn't exactly match the losing carrier's records, the request can bounce.
What the Porting Authority actually does
In Australia, your new provider will usually ask you to sign a Porting Authority Form, often called a PAF. That document authorises the gaining provider to act on your behalf and request the transfer of the number from the current provider.
The important part isn't just signing it. It's matching the existing carrier record exactly.
If the current record says "Smith Trading Pty Ltd" and the form says "Smith Pty Ltd", that can be enough to trigger a rejection. The same applies to unit numbers, old trading addresses, or account numbers copied from an outdated invoice.
What to have ready
Have these items in front of you before filling anything in:
A recent phone bill that shows the service details and current provider
The full account number exactly as listed by the carrier
The legal business name attached to the service
The physical service address recorded against the number
A contact person who can answer validation questions quickly
A simple internal note can save days of back-and-forth. Write down who approved the port, which numbers are in scope, and whether any related services must remain active until after cutover.
The fastest porting jobs usually aren't the ones with the best provider. They're the ones with the cleanest customer records.
Handle privacy and recordings properly
There's another piece many businesses miss. When you move to cloud telephony, your responsibility for customer data doesn't disappear.
The OAIC position is clear. Australian organisations remain the data controller even when they use cloud providers for telephony. That means you still need to protect personal information such as call records, and you should confirm whether voice recordings are stored in Australian-based data centres and how encryption is applied (Australian privacy responsibilities for cloud telephony).
For a small business, that leads to practical questions:
Are you using call recording at all, and if so, why?
Where are those recordings stored?
Who can access them?
Do you need a written internal policy for staff who listen back to calls?
That's not legal theatre. It's basic operational discipline. If you're authorising a provider to port services and potentially host call data, you need to know what information is being handled and under what controls.
The Number Porting Process and Timelines
Once the paperwork is lodged, the porting process becomes far less mysterious than people think. It follows a sequence. The delays usually happen at validation points, not because your number is floating around somewhere in limbo.
Early in the process, it helps to understand the workflow visually.
What happens behind the scenes
The new provider submits your port request to the current carrier or to the upstream network responsible for that number range. The losing provider checks the submitted details against their record. If the data matches, the request moves to approval and scheduling. If it doesn't, the request is rejected and must be corrected.
The broad business driver behind all this is bigger than any one port. Australian SMEs adopting cloud-based telephony, including hosted PBX, reported average telephony-related cost reductions of 30–60% over three-year periods compared with maintaining legacy PBX hardware, and ACMA has set a migration path for copper PSTN phase-out scheduled to complete by 2025–2027 in many regions (Australian hosted PBX migration drivers). That's why carriers, providers, and customers are all dealing with these migrations in volume now.
If you want a provider-side explanation of the steps involved when moving an existing number, this walkthrough on porting your existing telephone number onto a hosted PBX network gives a practical view of how requests are handled.
The cutover isn't the whole job
A common misunderstanding is that "the port" means one single event. In reality, there are two separate tracks:
Administrative transfer of the number
Configuration of the Hosted PBX service that will receive calls
Those tracks need to meet cleanly on cutover day. Your auto attendant, hunt groups, voicemail destinations, Yealink handsets, softphone apps, and extension routing should already be configured and tested before the number moves.
This video gives a useful visual overview of the concept and can help non-technical staff understand what the platform is replacing.
What affects timing
There isn't one universal timeline for every number type, and that's where unrealistic expectations creep in. A straightforward business number with clean account data is generally simpler than a legacy multi-line service, a complex hunt group, or a service tied to old infrastructure nobody has touched in years.
What usually slows things down is:
Mismatch in account name or address
Bundled services that need to remain active
Multiple numbers on one account with partial-port complications
Old service records with outdated contacts
Special number types such as inbound service numbers
If a provider promises that every number ports the same way, they haven't spent much time cleaning up legacy business services.
The predictable approach is to treat porting as a scheduled change, not a casual admin task. That means testing first, scheduling during a sensible business window, and keeping your old service active until the port is confirmed complete.
Troubleshooting Common Porting Problems
Most porting problems feel dramatic when they happen. In practice, they're usually routine. A rejected port isn't a disaster. It's a clue that one of the moving parts doesn't match.
The usual rejection reasons
The first category is record mismatch. The legal entity name, account number, or service address doesn't align with the losing carrier's database. That's the classic one.
The second is premature cancellation. A business asks the old carrier to disconnect the service before the number has ported. Once that happens, recovering the number can become far messier.
The third is hidden service dependency. The number sits on a bundle with internet, EFTPOS, monitored alarms, or another critical service. The port request might be valid, but the surrounding service design isn't.
A simple response table helps keep everyone calm:
Problem | What it usually means | Best fix |
|---|---|---|
Port rejected for incorrect details | Carrier record doesn't match form | Re-check latest bill and resubmit with exact data |
Number can't be moved yet | Another service depends on it | Split the plan properly before re-lodging |
Calls fail after cutover | PBX routing or handset registration issue | Test inbound, outbound, and extension config separately |
Intermittent recovery after outage | SIP failover settings are too slow | Review provider failover design and keep-alives |
Don't blame the port for a network problem
Sometimes the number ports correctly and the business still has trouble. Calls don't recover quickly after an outage, or incoming service behaves unpredictably. That's often not a failed port. It's a resilience issue in the VoIP setup.
In Australia, a critical design step is to implement SRV-based failover to an alternate SIP proxy. A common operational mistake is leaving default SIP keep-alives at 120 seconds, which slows failover detection. VoIP-aware providers commonly reduce keep-alives to 30–45 seconds, cutting post-failure call-route recovery times from 2–5 minutes down to 20–40 seconds (Australian SIP failover guidance).
That matters for business owners because the symptom can look like "the number didn't port properly" when the underlying issue is delayed failover after a network event.
What to do on the day if something looks wrong
Use a short diagnostic sequence:
Test inbound first from an external mobile. If that fails, check whether the number has fully cut over.
Then test outbound from the new service. If outbound works but inbound doesn't, the issue is often routing rather than handset setup.
Try extension-to-extension calls to confirm the PBX itself is operating.
Check one device and one app. If the desk phone fails but the softphone works, you've narrowed it down fast.
Keep the old service active until you've confirmed that inbound and outbound calling both work. That's the safety net too many businesses remove too early.
Your Final Switchover Checklist and Special Cases
By switchover day, the heavy lifting should already be done. What matters now is disciplined checking. Not guesswork.
The day-of checklist
Run these checks in order:
Confirm the Hosted PBX is active. Handsets should be registered, softphones logged in, and call flows loaded.
Call the main number from outside. Use a mobile on a different network and make sure the call lands where it should.
Place outbound calls to a mobile and a landline so you know caller ID and routing are correct.
Check voicemail and after-hours logic by forcing a missed call path.
Test transfers between staff, especially across sites or remote workers.
Tell your team what has changed. New transfer methods, new voicemail access, and any app login details should already be in their hands.
A smooth port can still feel messy if the humans using the system don't know the new workflow.
Special cases that need extra care
Not every number ports under the same rules.
1300 and 1800 numbers often involve the Rights of Use holder rather than just the bill payer. If the person or business authorising the transfer isn't the recognised holder, the paperwork can stall. These services can also involve separate inbound routing logic, so confirm where calls are meant to terminate after transfer.
Mobile numbers follow their own portability process and identity checks. If your business uses mobiles as public contact numbers, don't assume the fixed-line porting process applies. This guide to mobile number portability is useful if your switchover includes staff mobiles or business SIM services.
Remote and multi-site setups deserve one extra check. Make sure every location can register devices cleanly and that local internet quality supports voice before the public numbers are pointed at the new system.
What success looks like
The end state is simple. Your existing number still belongs to your business identity. Customers dial the same contact point. Your staff answer from the office, from home, or on the road. You don't have to nurse an old PBX in a comms cupboard anymore.
That's the practical answer to what is a Hosted PBX. It's not just cloud telephony in abstract terms. It's a business phone system that lets you keep the numbers your customers already know while replacing rigid on-site hardware with something far easier to run.
If you're ready to move off legacy phone services and want local help with number porting, handset setup, and an Australian-supported Hosted PBX, Hosted Telecommunications can help you plan the cutover properly and keep your business numbers working through the transition.
Comments