Cloud PBX Australia: What It Is, How It Works, and Who Needs It

Cloud PBX is a business phone system where the software runs on a provider's servers, not in your office. You access it over your internet connection and your provider manages everything. This guide covers how cloud PBX works on NBN, what it costs in Australia, and who it suits -- and who it does not.

Cloud PBX is a business phone system where the PBX software runs on a provider's servers, not in your office. You access it over your internet connection, and your provider manages everything behind the scenes. This guide is built for Australian small business owners navigating the shift away from old phone hardware, with real context on how cloud PBX works on NBN, what it actually costs in Australia, and who it suits (and who it doesn't). By the end, you'll know exactly what cloud PBX is, how it differs from what you might have now, and whether it's the right move for your business.

First, a quick clarification: cloud PBX, hosted PBX, and VOIP phone system all mean the same thing

Before anything else: if you've searched for "cloud PBX", "hosted PBX", or "VOIP phone system for business" and gotten slightly different results each time, that's because the industry uses all three terms for essentially the same product. There's no meaningful technical difference between a "cloud PBX" and a "hosted PBX" in the way these terms are used by Australian providers. Some providers say cloud PBX. Others say hosted PBX. Others call it a hosted VOIP phone system. They're marketing synonyms.

You're not behind for finding this confusing. The industry made it confusing on purpose. This article will use "cloud PBX" throughout, but everything here applies equally if your provider uses the other terms.

What is a cloud PBX?

A PBX (Private Branch Exchange) is the system that manages phone calls for a business. Traditionally, it was a physical box in your communications rack or comms cupboard. It handled things like routing calls to the right extension, putting callers on hold, playing hold music, and forwarding calls after hours. That box was expensive, required ongoing maintenance, and needed someone with technical knowledge to manage it.

A cloud PBX does the same job, but the "box" is now software running on a server in a data centre managed by your provider. You don't own it. You don't maintain it. You access it over your internet connection. When someone calls your business number, the call routes through the provider's infrastructure, hits their PBX software, and then reaches the right phone in your office (or on your team's laptops or mobile apps).

Think of it this way: the business phone system moved from a box in your comms rack to software on a server you don't have to manage. The end result for the person calling your business looks and sounds identical. The difference is entirely in how it's deployed and who's responsible for keeping it running.

How cloud PBX differs from a traditional on-premise PBX

Traditional on-premise PBX systems were the standard for business phone communications for decades. If you worked in an office with a phone system in the 1990s or 2000s, you were probably using one. The hardware sat in your building, was maintained by your IT team or an MSP, and ran on the copper phone network (PSTN). When you needed a new extension, someone had to come onsite and configure it. When something broke, someone had to come fix it.

Here's how the two compare:

Hardware in your officeUpfront costOngoing costWho maintains itAdding new usersRemote work / softphoneWorks on NBNDisaster recovery
Cloud PBX (Hosted) None requiredLow to zero (hardware is provider-side)Monthly per-user subscription (~$20-60/user/month)Provider handles all software/infrastructureAdd a seat in an online portal, takes minutesBuilt in -- app works on any internet connectionYes -- designed for internet deliveryProvider handles redundancy
Traditional On-Premise PBX Yes -- PBX unit, cabling, sometimes a serverHigh ($3,000-$20,000+ depending on size)Maintenance contracts, IT/MSP support feesYour IT team or an MSP you pay separatelyRequires onsite configuration, sometimes hardware purchaseComplex and often expensive to set upDepends on hardware and config; often needs adaptationIf the box fails or there's a fire, you're offline

The short version: on-premise PBX made sense when businesses owned their IT infrastructure, had IT staff to manage it, and ran on a copper phone network that was going to be there forever. None of those things are true for most Australian SMBs today. The copper network is gone (more on that below), most small businesses don't have dedicated IT staff, and cloud services mean you don't need to own infrastructure to access enterprise-grade functionality.

For a deeper comparison, see our full hosted PBX vs on-premise PBX guide.

Why Australian businesses are moving to cloud PBX now

There are three things happening simultaneously in Australia that are driving businesses toward cloud PBX, whether they're ready or not.

1. The PSTN copper network has been switched off. Telstra's traditional copper phone network (the PSTN) was the backbone of business phone systems for over a century. It's now gone. The NBN rollout replaced it with fibre, fixed wireless, and satellite connections. As of 2025, new copper services are no longer available. If your business has a phone service, it's already running over the internet in some form. The question is just how well set up that service is. For more on what the copper shutdown means for Australian businesses, see our PSTN shutdown guide.

2. NBN changed how business phones work. When NBN was installed at most Australian premises, the ISP provided a modem with a green phone port (technically called an ATA -- Analog Telephone Adapter). Many business owners plugged their existing phones into that port and assumed the setup was equivalent to what they had before. It's not. That green port connection is a basic consumer VOIP service controlled entirely by your ISP. It's not a business phone system. It has no PBX features, no call routing, no hold, no auto-attendant, no voicemail-to-email. (More on this in the Common Mistakes section below.)

3. Remote work made on-premise hardware impractical. A PBX box in your office is fine when all your staff are in that office. It's very difficult when staff work from home, travel, or operate across multiple sites. Cloud PBX solved this problem by design -- a softphone app on a laptop or mobile connects to the same system as the desk phones in the office. Your team is reachable on their work number regardless of where they are.

How cloud PBX works on NBN in Australia

Cloud PBX uses a protocol called SIP (Session Initiation Protocol) to carry voice calls over your internet connection. When someone calls your business number, the call is handled by your provider's infrastructure, converted to data packets, and delivered to your phone (or app) via your NBN connection. Your phone converts those packets back into audio. The whole process happens in milliseconds and, on a decent connection, is indistinguishable from a traditional phone call.

For this to work well, your NBN connection needs to meet some baseline requirements:

  • Upload speed: Each simultaneous call needs roughly 100 Kbps of upload bandwidth. If you have 5 staff who might all be on calls at the same time, you need at least 500 Kbps of stable upload capacity -- though aiming for 1-2 Mbps gives you headroom. Most NBN plans (50/20 or higher) comfortably handle a small team.
  • Jitter: Jitter is inconsistency in packet delivery times. High jitter causes choppy, robotic-sounding audio. A wired ethernet connection (not WiFi) from your phones to your router significantly reduces jitter. Acceptable jitter for voice calls is under 30ms.
  • Packet loss: Dropped packets cause gaps in audio or calls cutting out. Packet loss above 1% will be noticeable. Most Australian NBN services have low packet loss, but congestion at the node (for FTTN connections) can cause issues during peak hours.
  • Latency: Round-trip latency under 150ms is ideal for natural-sounding conversation. NBN services in Australian capitals typically run 10-30ms latency to domestic servers, which is excellent for voice.

One important setting: SIP ALG (Application Layer Gateway) is a feature in many consumer routers that was designed to help VOIP calls but typically does the opposite -- it interferes with SIP packets and causes one-way audio, dropped calls, and registration failures. If your provider hasn't mentioned this, ask them whether your router model needs SIP ALG disabled. Most specialist VOIP providers will configure this for you during setup.

For a full rundown on NBN and voice quality, see our VOIP call quality guide.

What features does cloud PBX include?

One of the biggest surprises for SMB owners who switch to cloud PBX is how much comes included at no extra cost. Most providers include the following features in their standard per-user plans:

Auto-attendant (IVR): The automated greeting that answers your calls and directs callers. "Thank you for calling Acme Plumbing. For quotes, press 1. For existing bookings, press 2. For emergencies, press 3." This alone changes how professional your business sounds to a first-time caller. You can set up different greetings for business hours and after hours, and update them yourself without calling your provider.

Ring groups: Define which phones ring when a call comes in. All phones ring at once. Or calls go to the sales team first, then overflow to admin if unanswered. Or calls ring each phone in sequence. You control this through a web portal.

Call recording: Record inbound or outbound calls for training, compliance, or dispute resolution. Recordings are stored by your provider and accessible via the admin portal. (Note: Australian law requires you to inform callers that the call may be recorded -- typically handled by playing a short announcement when the call connects.)

Softphone app: A mobile or desktop app that connects to your cloud PBX. Your team can take and make calls on their work number from their laptop or personal mobile, anywhere they have internet. For remote teams or business owners who are rarely in the office, this is often the primary way they use the phone system.

Voicemail to email: When a caller leaves a voicemail, you get an email with an audio file attached. You can listen from anywhere, respond faster, and keep a record. No more "messages left on the office phone that nobody checks".

After-hours routing: Outside business hours, calls can route to voicemail, play a custom message with your operating hours, forward to a mobile, or any combination. You define what "business hours" means in the portal, and the system handles the rest automatically.

Hold music or messages: Custom hold music, or pre-recorded messages that play while callers wait. "Thanks for holding. We answer all calls in the order received. Did you know you can also book online at..." This is basic for enterprise, but many SMBs on ISP ATA services have nothing -- callers get silence or a disconnected tone.

Hunt groups and call queuing: Manage multiple simultaneous inbound calls without losing any of them. Callers queue and hear their position updated. Your team sees the queue and picks up calls in order. Eliminates the busy signal problem entirely.

Number porting: You can move your existing business phone numbers to your new cloud PBX provider. You don't have to give up the number your customers already have. The porting process typically takes 5-10 business days in Australia.

Australian local numbers and 1300/1800: Your provider can allocate you a local geographic number (03, 02, 07, 08) for any Australian state, regardless of where you're located. Or set up a 1300 number for a national-facing presence. Both work identically with cloud PBX. See our business phone system guide for more on number types.

What does cloud PBX cost in Australia?

Australian cloud PBX providers typically charge on a per-user, per-month basis. The all-inclusive price range for small business plans is roughly $20 to $60 per user per month, depending on included call minutes, features, and support level.

Here's what to expect at different price points:

  • $20-30/user/month: Entry-level plans. Usually includes core PBX features (auto-attendant, ring groups, voicemail to email, softphone). Call costs may be metered separately (per-minute), or you get a modest included minutes bundle. Suits very low-volume callers or businesses that mostly receive rather than make calls.
  • $35-50/user/month: Mid-tier plans. Typically includes unlimited local and national calls, all standard PBX features, and often mobile app access. This is where most 1-20 seat Australian SMBs land. For a 5-person team, budget roughly $175-250/month all up.
  • $50-60/user/month: Higher-tier plans. Usually includes international calls, advanced call reporting, CRM integrations, call recording storage, or priority support. Suits businesses with specific compliance requirements or heavier outbound call volumes.

Most providers offer month-to-month contracts (no lock-in) for standard SMB plans, with discounts of 10-20% for 12-month commitments. Be wary of providers who push long-term contracts on a new customer without a trial period -- month-to-month is the norm with reputable AU specialists.

Hardware is separate. If your team needs desk phones (rather than using the softphone app on their computers), expect to pay $80-350 per handset (e.g. Yealink T31P at the entry level through to a full-featured colour-screen model). Many providers offer handset leasing, or will ship pre-configured phones that plug in and work immediately.

For a full breakdown including number porting costs and 1300 number pricing, see our hosted PBX pricing guide.

Who is cloud PBX right for?

Cloud PBX is a strong fit for a wide range of Australian businesses. Here's where it makes the most sense:

SMBs with 1-50 staff needing phones. This is the sweet spot for cloud PBX. Small enough that on-premise hardware is overkill, large enough that a basic ISP phone service is inadequate. If your business has more than one or two people who need to take calls, cloud PBX is almost certainly the right answer.

Businesses discovering they've outgrown the "green port" setup. If your phone system is currently the phone port on your NBN modem, you're on a basic consumer VOIP service. The moment you try to hire someone and share a number, add call routing, or look professional to incoming callers, you'll hit its limits. Cloud PBX is the natural next step.

Multi-site businesses. A cloud PBX treats multiple office locations as a single phone system. Staff at different sites can transfer calls between each other, share a phone number, and appear to be on the same system -- because they are. No hardware at each site, just internet connections.

Remote teams or hybrid workforces. The softphone app means your team is reachable on their work number wherever they have internet. No physical desk phone required. For a small team that works from home, an office, or client sites, cloud PBX is often the only option that actually works across all those locations.

Businesses without IT staff. You don't need a managed service provider or IT team to run cloud PBX. The provider handles all the infrastructure. Adding a user, changing call routing, or updating your after-hours greeting takes minutes in a web portal. If something breaks, you call your provider -- not an IT contractor.

Businesses planning to move premises. Cloud PBX has no physical tie to your premises. Moving offices means disconnecting your internet at the old site, connecting at the new one, and your phone system follows. No hardware relocation, no number changes, no downtime.

Who might not be the right fit for cloud PBX?

Cloud PBX is not the universal answer. There are situations where it's not the best fit:

Businesses with unreliable or very slow internet. If your premises has genuinely poor internet -- rural fixed wireless with variable speeds, satellite NBN with high latency, or a Fibre to the Node connection with chronic evening congestion -- call quality will suffer. Before switching to cloud PBX, test your connection's upload speed and stability at peak hours. If you're regularly dropping below 5 Mbps upload or experiencing high jitter, address the connection issue first, or consider a 4G/5G backup connection for your phones.

Businesses with complex legacy integrations. If your existing phone system is deeply integrated with specialist on-premise software (some older medical practice management or legal billing systems, for example) that was built specifically for analog lines or a specific on-premise PBX model, a cloud migration will require careful planning. Most modern software supports cloud/SIP integration, but check before assuming.

Businesses still on Telstra-dependent legacy systems. Some businesses have Telstra ISDN or specific Telstra business services with proprietary handsets and line configurations that don't migrate cleanly. A reputable cloud PBX provider will assess this during the quoting process and flag any porting complexity before you sign up.

Very large enterprises with complex requirements. Above 100+ seats with complex call centre functionality, multi-level IVR scripting, bespoke CRM integrations, or contact centre-grade reporting, you're likely looking at a different tier of product entirely. Cloud PBX as described in this article is designed for SMBs -- enterprise deployments are a different conversation.

How cloud PBX providers operate in Australia

Understanding how the provider relationship works helps you evaluate your options and set expectations:

Monthly subscription model. You pay per user per month. Most SMB plans are month-to-month. You can add seats during busy periods and scale back if headcount drops. The provider manages everything on the infrastructure side.

Number porting. You can bring your existing business number(s) to a new cloud PBX provider. This is regulated by the ACMA (Australian Communications and Media Authority) and governed by the Industry Number Portability Code. Most ports complete in 5-10 business days, though complex ports (multiple numbers, carrier issues, or numbers tied to bundled services) can take longer. During the port, there's a brief window where your number is transferred -- most providers coordinate this to happen outside business hours to minimise disruption.

Australian local numbers. Your provider can allocate you a geographic number for any Australian state -- a Sydney 02 number even if your business is in Brisbane, for example. This is useful for businesses that want a local presence in multiple cities.

000 emergency calling. This is an important one. Cloud PBX services in Australia are required to provide access to 000. However, unlike a traditional landline, the system needs to know your registered address to correctly route the call to the nearest emergency services. Register your physical address with your provider and keep it updated if you move. If your staff use softphones from different locations (home, client sites), they need to understand that 000 from the softphone will route based on the registered address, not their current location. For emergencies, a mobile is more reliable.

Power outage consideration. Unlike traditional copper-line phones, cloud PBX requires power. If your internet router or the power to your premises goes out, your cloud PBX phones go offline. For businesses where phone availability during a power outage is critical, a UPS (Uninterruptible Power Supply) on your router and phones is worth considering. Many cloud PBX providers also offer mobile app failover -- calls automatically route to a mobile number if the primary phones go offline.

The green port trap: what cloud PBX is NOT

This is worth its own section because it's the most common misconception in Australian SMB communications right now.

When NBN was rolled out, most ISPs provided a modem/router with a green phone port on the back. Many business owners plugged their existing phone into that port and assumed they were now on VOIP. In a narrow technical sense, they are -- the call travels over the internet. But that green port is an ATA (Analog Telephone Adapter) built into the modem. The VOIP service is programmed into the modem's firmware by your ISP, and you have no control over it.

This ISP ATA service:

  • Has no PBX features -- no auto-attendant, no ring groups, no call recording, no voicemail to email
  • Has one line -- two simultaneous callers means one gets an engaged signal
  • Is controlled entirely by your ISP -- you can't get SIP credentials to connect a proper VOIP handset or phone system
  • Has no admin portal -- you can't change call routing, after-hours behaviour, or anything else
  • Is often the first thing to be cut in a service outage or network change

Cloud PBX is a completely different product. It uses a separate SIP account provided by a specialist VOIP carrier. It connects to your network via an ethernet port (not the green phone port). It gives you full admin control. And it has all the PBX features that make a business phone system actually useful.

If you're currently on the ISP green port and wondering why you can't configure hold music or add a second line, now you know. Cloud PBX is what replaces it.

Australian considerations: NBN, PSTN shutdown, and number porting

PSTN copper shutdown context. Australia's traditional copper phone network (PSTN) was decommissioned as part of the NBN rollout. As of 2025, Telstra no longer offers new PSTN services, and businesses on legacy copper-line services have been migrated. If your business hasn't already transitioned, that process is either complete or imminent. Cloud PBX is the natural landing point for businesses coming off legacy copper phone systems.

NBN technology type matters. The performance of your cloud PBX will vary depending on which NBN technology type services your premises:

  • FTTP (Fibre to the Premises): Best option. Low latency, stable speeds, suitable for any call volume.
  • FTTN (Fibre to the Node): Adequate for most SMBs, but performance depends on copper line quality from the node to your premises. Evening congestion can affect call quality.
  • Fixed Wireless: Variable -- can work well, but more susceptible to congestion and weather. Test your connection under peak load before committing.
  • Satellite (Sky Muster): High latency (600ms+) makes real-time voice calls challenging. Not recommended as a primary connection for cloud PBX.

Number porting when switching providers. If you're moving from an existing phone service to cloud PBX (or switching between cloud PBX providers), number porting is how you keep your existing numbers. The process is governed by the ACMA Industry Number Portability Code. Key things to know: porting takes 5-10 business days typically; your old service remains active during the port process; you cannot port a number that is currently suspended or cancelled (keep it active until the port completes); complex ports involving multiple numbers or non-standard carrier arrangements may take longer. Your new provider will manage the porting process -- you just need to provide account details from your current carrier. For a detailed walkthrough, see our phone system guide for small business.

Common Mistakes: What Most Businesses Get Wrong with Cloud PBX

Mistake 1: Assuming the ISP green port is a business phone system. This is the most common mistake by a wide margin. The phone port on your NBN modem is a basic consumer VOIP service, not a cloud PBX. It has no ring groups, no auto-attendant, no admin portal, no call recording, no second line. Businesses run on this setup for years without realising how much they're losing -- missed calls because two customers rang at once, no after-hours message, no voicemail-to-email, nothing. Cloud PBX is the product that replaces the green port service entirely.

Mistake 2: Buying handsets before choosing a provider and phone system. The single most common misstep is starting with "I need a VOIP phone" and buying a Yealink or Grandstream desk phone without first setting up a cloud PBX service. A VOIP desk phone connects via ethernet to a SIP account -- it needs to be pointed at your provider's PBX to work. If you don't have a cloud PBX service set up, the phone can't do anything. The right order is: choose a provider, get a plan, understand the features you need, then order handsets (many providers will ship pre-configured phones). See our VOIP phone system guide for how to sequence the decision.

Mistake 3: Cancelling the old phone number before porting completes. If you're switching from your current carrier to a cloud PBX provider and want to keep your existing business number, do not cancel your current service until the number port is complete. Once a number is released by the carrier, it goes back into the pool and may be reassigned. Keep paying for the old service until your new provider confirms the port has completed successfully. It typically takes 5-10 business days -- plan for two weeks to be safe.

Your Next Steps

If you've read this far and you're thinking cloud PBX is probably the right direction for your business, here's a practical sequence to follow:

  1. Assess your current setup. Are you on the ISP green port, an existing on-premise PBX, or already on a cloud/hosted service? This determines how complex the transition will be.
  2. List what you actually need. Ring groups? Auto-attendant? Call recording? Softphone for remote staff? Write down the features your business genuinely uses or needs. This stops you overpaying for features you'll never touch.
  3. Check your internet connection. Run a speed test at peak hours. Make sure your upload speed is at least 1-2 Mbps stable. If it's borderline, mention this when speaking to providers.
  4. List your numbers to port. Write down every phone number your business uses and which carrier currently holds it. Your new provider will need this to manage the porting process.
  5. Get a recommendation. Talk to a specialist AU VOIP provider -- someone who understands how Australian SMBs operate, can assess your specific situation, and will configure the system for you. Avoid setting this up alone based on a comparison table if you've never done it before. A specialist takes the guesswork out of it.
  6. Plan your cutover. Decide when to make the switch. Most businesses prefer to cut over outside peak hours -- early morning or a weekend. Your provider should coordinate this for you.

Not sure which cloud PBX setup is right for your business? Tell us about your team, your current setup, and what you need -- and we'll point you to the right solution.

Get a Free Recommendation
Is cloud PBX the same as hosted PBX?

Yes -- in the way Australian providers use these terms, cloud PBX and hosted PBX describe the same product: a business phone system where the PBX software runs on the provider's servers rather than in your office. Some providers use "cloud PBX", others say "hosted PBX" or "hosted VOIP phone system". The technology underneath is identical. When comparing providers, don't let the terminology differences confuse you -- focus on the features, pricing, and support model instead.

Do I need special internet for cloud PBX in Australia?

You don't need a special internet plan, but you do need a stable, reasonably fast connection. Each simultaneous call uses roughly 100 Kbps of upload bandwidth. For a small team of 5 where all staff might be on calls at once, that's 500 Kbps -- easily handled by any NBN 50/20 plan or faster. What matters more than raw speed is stability: consistent upload speeds, low jitter (under 30ms), and minimal packet loss. A wired ethernet connection from your router to your phones is strongly recommended over WiFi, as it significantly reduces jitter and dropped packet issues.

Can I keep my existing phone number when switching to cloud PBX?

Yes. Number porting allows you to transfer your existing business phone number to your new cloud PBX provider. This applies to geographic numbers (02, 03, 07, 08), 1300 numbers, and 1800 numbers. The process typically takes 5-10 business days in Australia and is governed by the ACMA Industry Number Portability Code. Your new provider manages the porting process -- you provide them with your current carrier account details and they handle the rest. Keep your old service active until your new provider confirms the port is complete.

What happens to cloud PBX calls when the power goes out?

Unlike traditional copper landlines, cloud PBX requires power and internet to work. If your premises loses power, your router goes offline and your phones stop working. For most businesses this is acceptable -- it's a rare event and mobile phones work as a fallback. If continuous availability during outages is critical (medical practices, emergency-adjacent services), consider two options: a UPS (Uninterruptible Power Supply) to keep your router and phones running during short outages, and/or failover routing set up through your provider so that calls automatically forward to a nominated mobile number if your primary phones go offline. Ask your provider about failover options -- most cloud PBX systems support this.

How long does it take to set up cloud PBX for a small business?

For a basic setup -- new numbers, no porting, a handful of desk phones or softphone users -- a specialist provider can have you live within 1-3 business days. The main variables are: number porting (add 5-10 business days if you're bringing existing numbers), handset delivery (pre-configured phones shipped from your provider typically take 2-5 business days), and call flow complexity (a simple setup with one auto-attendant and a couple of ring groups takes an hour to configure; a complex multi-level IVR with custom schedules and integrations takes longer). Most Australian cloud PBX providers will walk you through the setup as part of the onboarding process.

Does cloud PBX work with my existing desk phones?

It depends on the phone. Modern SIP-compatible VOIP desk phones (such as Yealink, Grandstream, Polycom, or Fanvil models) will generally work with any cloud PBX provider -- they just need to be reconfigured with your new provider's SIP credentials. Older analog phones (the kind that plug into a wall socket or the green port on your modem) are not compatible without an ATA adapter. Many businesses take the switch to cloud PBX as an opportunity to upgrade handsets -- entry-level SIP desk phones start around $80-120 AUD and most providers can ship them pre-configured so they work straight out of the box.

What is the difference between cloud PBX and a SIP trunk?

A SIP trunk is a connection that carries calls between your phone system and the PSTN (the public phone network). A cloud PBX is the phone system itself -- the software that manages call routing, ring groups, auto-attendants, voicemail, and all the features. A SIP trunk can connect to an on-premise PBX or to a cloud PBX. When you sign up with a cloud PBX provider, the SIP trunking is included -- you don't need to think about it separately. The distinction only becomes relevant if you're running your own on-premise PBX and sourcing your SIP trunks separately, which is a more complex setup generally suited to larger businesses with in-house telephony expertise.

Can cloud PBX call 000 emergency services in Australia?

Yes, Australian cloud PBX providers are required to provide access to 000. However, there is an important difference from traditional landlines: the system routes 000 calls based on your registered service address, not your physical location at the time of the call. This is fine for a fixed office, but if your staff use softphone apps from different locations (home, a client site, a cafe), they should be aware that a 000 call from the softphone will be routed to emergency services based on the address registered with your provider, not where they actually are. For genuine emergencies while mobile, a mobile phone is the more reliable option as it uses cell tower triangulation to determine location.