Most VOIP content tells you why to switch. This article is different: it is an honest assessment of the situations where sticking with a traditional setup (or combining VOIP with a backup plan) is the more sensible choice. Understanding the failure modes of VOIP before you commit helps you make a better decision, and it is the kind of assessment that builds more trust than a one-sided sales pitch.
VOIP works well for the majority of Australian businesses. If you have a stable NBN connection, a business with multiple staff handling calls, and no specific regulatory constraints, VOIP is almost certainly the right move. But the situations below are real exceptions, not edge cases to dismiss.
Situation 1: Your NBN Connection Is Unreliable
VOIP is only as reliable as the internet connection it runs on. For most Australian businesses on FTTP or HFC NBN connections in metropolitan areas, reliability is high and this is not a real concern. For businesses on FTTN (Fibre to the Node) connections in congested areas, or in outer regional locations where NBN service quality degrades, VOIP call quality can be unacceptable.
The specific failure modes on a poor NBN connection:
- Jitter: Variation in packet delay or interarrival timing, which can cause choppy or robotic-sounding calls when it exceeds the receiving system's jitter-buffer capacity. VOIP is more sensitive to jitter than to raw latency.
- Packet loss: Lost audio packets cause gaps, clipping, or complete audio dropout. Even low packet loss can cause clipping or skips; the point at which a call becomes unusable depends on the codec, loss pattern and packet-loss-concealment capabilities.
- Connection instability: If the NBN connection drops, calls and signaling may fail during the interruption; after connectivity returns, the endpoint may also need to restore its SIP connection, registration or NAT state.
Before writing off VOIP on a poor NBN connection, try these mitigations: configure Quality of Service (QoS) on your router to prioritise VOIP traffic (see our QoS settings guide), upgrade from FTTN to FTTP if available in your area, or add a 4G failover router. But if you are in a location where the NBN is genuinely unreliable and 4G coverage is also poor (some rural and remote areas), VOIP may not be the right primary phone system. A mobile-forwarded landline number or a satellite-based solution may be more reliable in practice.
Check your NBN connection type and quality before switching. See our VOIP on NBN compatibility guide for what each NBN technology type means for call quality.
Situation 2: Your Business Cannot Tolerate Any Call Outages
VOIP depends on two things working: internet connectivity and mains power. A legacy copper PSTN service could continue through a premises power outage when used with an unpowered corded handset, provided the exchange and copper network remained operational.
NBN outage frequency and duration vary by connection, technology, provider and location; each business should assess its own outage history and continuity requirements, including whether mobile failover is viable. For some businesses, any outage is not acceptable:
- Emergency service providers and first responders who need telephony available at all times, including during power outages.
- Critical care facilities (hospitals, residential aged care) where call continuity is a direct patient safety issue.
- Businesses with contractual uptime obligations for call availability (some financial services firms, critical infrastructure operators).
For these situations, VOIP should be used alongside a failover system, not as the sole telephony path. Mitigation options include battery backup for internet equipment, a cellular backup router that maintains internet connectivity during NBN outages, and a separate mobile number that calls automatically roll to when the primary system is unreachable. If even this level of complexity is unacceptable, ask whether your premises is eligible to retain a legacy copper service-an option that may exist in some Fixed Wireless and Sky Muster areas-or consider a dedicated connectivity service.
A properly configured VoIP system with cellular failover and provider-side forwarding can improve resilience, but actual end-to-end availability depends on every component and should be tested against the business's uptime requirement.
Situation 3: You Are in a Location With Poor 4G Coverage Too
The standard mitigation for NBN-based VOIP reliability is mobile failover: a 4G router that takes over when the NBN drops. In most Australian metropolitan and regional areas, this works well. But in some rural and remote locations, both NBN reliability and 4G coverage are poor simultaneously.
A business in a remote area with patchy Telstra 4G and unreliable satellite NBN does not have an obvious VOIP-first answer. Options for these situations:
- Starlink for NBN + 4G as primary voice: Use Starlink for internet (now suitable for VOIP in most Australian coverage areas) and route calls through a mobile number as the primary phone.
- Mobile-first phone system: Use a business mobile plan as the primary phone system, with a cloud-based call routing service (like a virtual receptionist or a hosted PBX that routes to mobile) as the business number layer.
- Hybrid: Keep a mobile as the fallback while using VOIP when the NBN connection is stable. Some hosted PBX platforms can forward calls to mobile when VoIP extensions are unreachable, but availability and configuration vary by provider and plan.
Situation 4: You Have Specific Regulatory or Compliance Constraints
Some regulatory environments create specific constraints on telephony that affect VOIP adoption:
000 emergency calling. Certain VoIP services support 000 emergency calling; confirm the capability and emergency-call arrangements of the specific provider and service before relying on it. The call must connect, and the registered address must be accurate for emergency location. Confirm the provider's 000 capability and registered service details before relying on it. If a live test is required, have the provider coordinate it under the formal emergency-call testing procedure rather than placing an unarranged test call. Most providers handle this correctly, but it is worth verifying rather than assuming.
Older fire alarm and lift monitoring systems. Many commercial fire panels and lift emergency phones were designed for copper PSTN lines and do not work reliably over VOIP or NBN. These systems send specific analogue signals that VOIP's digital path sometimes distorts. If your premises has a fire panel, security monitoring system, or lift phone connected to the phone line, get a technical assessment of whether those systems will continue working after migrating to VOIP. Many building managers have been caught out by this after assuming everything would transfer seamlessly. Your fire panel supplier or building services engineer can advise.
Fax machines. VOIP does not reliably support traditional fax. Traditional fax over VoIP is compatibility- and configuration-dependent: compressed voice codecs, packet loss and timing variation can disrupt fax, while supported implementations may use T.38 or fax pass-through. T.38 is a fax-over-IP standard supported by some providers, but reliability depends on end-to-end provider support, device compatibility and network conditions. If your business relies on fax (medical practices, government suppliers, some legal contexts), either keep a separate copper-based fax line while migrating voice calls to VOIP, or migrate to a fax-to-email service.
Situation 5: Your Business Genuinely Only Needs One Line
VOIP delivers its best value when a business needs multiple simultaneous calls, auto-attendant routing, call recording, ring groups, or other PBX features. For a sole trader who receives fewer than 5 calls a day, takes them on a mobile, and never needs more than one line, the overhead of a hosted PBX subscription is probably not justified.
A basic mobile plan with a business-grade number (a 10-digit mobile number, or a geographic number forwarded from a VoIP provider to the mobile) is simpler, cheaper, and adequate. The business context where this applies: trades businesses where the owner takes calls directly on the mobile, sole practitioners, or micro-businesses in industries where a personal mobile number is standard and customers expect it.
The switch to a hosted PBX becomes worth it when the sole trader starts missing calls because they cannot answer while already on a call, or when the business grows beyond one person handling inbound calls. Hosted-PBX pricing varies widely by provider, call inclusions, hardware and features, so compare the total first-user cost for the required configuration.
Situation 6: Your Business Uses Equipment That Requires an Analogue Phone Line
EFTPOS terminals, security alarm panels, fax machines, lift emergency phones, and some medical devices are designed for traditional PSTN analogue lines. Many will not function reliably over VOIP, and some will not work at all. The relevant question is not whether to use VOIP for voice calls, but whether VOIP can coexist with your analogue-dependent equipment. The practical options are: retain a provider-supported fixed-voice service only after the device and service providers confirm compatibility, or retain legacy PSTN copper where it remains available; use an ATA (analogue telephone adapter) and test the device thoroughly before committing; or replace the device with an IP-native equivalent. Do not assume your EFTPOS provider or security alarm company will support VOIP until you have confirmed it in writing -- many will support it but require specific configuration from your VOIP provider, and some will require a retained analogue line regardless. This is one of the most common reasons businesses end up with a hybrid setup rather than a full VOIP migration.What VOIP Problems Look Like Before They Become Deal-Breakers
If you are already on VOIP and experiencing problems, here are the early warning signs worth acting on before they become critical:
- Calls that drop without explanation: Possible causes include connectivity loss, SIP session-refresh or timer failures, NAT/firewall behavior, provider faults and endpoint problems; diagnose the call trace before attributing the cause.Choppy or robotic audio: Jitter on the internet connection. Check QoS settings on your router and test your connection quality with a VOIP-specific test tool.
- One-way audio (you can hear the caller but they cannot hear you, or vice versa): Common causes include routing, NAT, firewall or RTP-path problems. Check the provider's router requirements before changing SIP ALG.Phones going offline periodically: Check registration logs, connectivity, DNS, NAT/firewall state and provider status. Change registration intervals only in accordance with the provider's and PBX vendor's requirements.Router configuration is a common troubleshooting area, but VoIP faults can also originate in the access connection, provider platform, endpoint, cabling or power system. Check the router first before concluding that VOIP is not right for your setup. See our VOIP call quality troubleshooting guide for a systematic approach to diagnosing these issues.The most useful pre-switch test is running VOIP in parallel with your existing service for two to four weeks. Make all outbound calls via VOIP while keeping the PSTN line active as a fallback. If call quality issues appear consistently at the same time of day, that is a network congestion pattern that will persist after switching. If issues are random and infrequent, identify where delay or loss occurs before changing QoS. Router QoS may help when local or WAN-edge congestion is the cause, but it will not correct every intermittent fault. A provider that will not offer a trial period before a contract commitment is one that does not stand behind their call quality.
What Most Businesses Get Wrong
Dismissing VOIP because of a bad experience with a poorly configured system. A VOIP system with a misconfigured router (SIP ALG on, no QoS, wrong jitter buffer settings) will produce unreliable calls. This is a configuration problem, not a fundamental limitation of VOIP. Before concluding VOIP is not right, get a proper diagnosis of what went wrong.
Migrating to VOIP without checking the NBN connection quality first. Switching without first testing latency, jitter, packet loss and available bandwidth increases the risk of poor call quality after migration. Before porting your existing numbers to a new VOIP system, run a VOIP-specific test on your internet connection from the office location. Most hosted PBX providers offer a test tool or can advise on what to look for.
Treating VOIP as binary (all-in or stay on legacy). For businesses with genuine resilience requirements or compliance constraints, the answer is often a hybrid: VOIP as the primary system with a specific fallback for the edge cases. Where a legacy copper service remains available, a business may be able to retain it for the fire panel; otherwise the panel provider must approve an NBN-compatible or alternative monitored solution before voice migration. A business in a regional area with poor NBN can use VOIP when connectivity is good and mobile forwarding when it is not. The either-or framing misses the practical middle ground.
Businesses sometimes treat the VOIP decision as all-or-nothing: either switch everything or do nothing. A practical alternative can be a hybrid approach using provider-approved services for analogue-dependent devices while migrating staff handsets and the main hunt group to VOIP; legacy PSTN retention is only available at some premises. This is a common configuration for medical practices with EFTPOS or monitored alarms, retailers with integrated payment terminals, and buildings with analogue lift phones. The cost of a hybrid configuration varies by the retained or replacement service, provider, monitoring requirements and any equipment changes; compare the total cost with replacing the legacy device.Your Next Steps
If you are evaluating whether VOIP is right for your situation:
- Test your NBN connection quality with a VOIP-specific test (jitter, packet loss, latency). Jitter and packet loss should be low, but VoIP suitability must also account for end-to-end latency, available bandwidth, codec, call volume and local network conditions.
- Identify any legacy devices on your current phone line: fire panel, lift phone, security monitoring, fax machine. Get technical advice on whether each will work over VOIP or needs to stay on copper.
- Assess your 4G signal strength at the office location. If 4G coverage is poor and your NBN is unreliable, flag this as a real constraint before committing to VOIP-only.
- If you are on FTTN NBN and experiencing quality issues, check whether FTTP upgrade is available in your area before writing off VOIP.
- Consider starting with a trial rather than a full migration. Some Australian hosted-PBX providers offer trials, but availability, duration, included credit and migration conditions vary. Run the trial on a separate number while keeping your existing setup live.
For most Australian businesses VoIP is still the right answer, even if full cloud is not. Our guide to the best VoIP phone system for small business in Australia compares the top hosted providers on price, reliability, and feature set so you can work out what the right system looks like for your specific setup.
If you are still weighing up whether to switch at all, our guide to VoIP versus a traditional phone service in Australia compares the two on cost, reliability, features, and business suitability so you can make the call with the full picture in front of you.
Will VOIP work during a power outage?
Not without additional equipment. VOIP phones and the internet router they connect through both require mains power. If your power goes out, the phones go offline. Mitigation options include a UPS (uninterruptible power supply) for the router and phones, or using mobile phones as the failover during outages. Traditional copper PSTN landlines were powered by the exchange and continued working during home or office power outages. This capability is lost when migrating to VOIP unless you add battery backup.Can I keep a traditional landline and use VOIP at the same time?
Yes. Hybrid setups are common and often appropriate. A business might use VOIP for their main phone system (auto-attendant, multiple lines, mobile apps) while keeping a single copper line for a fax machine, a fire panel, or as an emergency backup. The copper line and VOIP system are completely independent. You can port your main geographic number to the VOIP provider while keeping a separate number on the copper line for the specific legacy device that needs it.Does VOIP work with old fax machines?
Reliably, no. Traditional fax uses analogue signalling that high-compression voice codecs such as G.729 can distort; G.711 pass-through may work when supported, but fax remains sensitive to packet loss and timing variation. T.38 fax-over-IP is a standard that improves reliability, and some VOIP providers support it, but it is not as reliable as a dedicated copper fax line. For businesses that send or receive occasional faxes, a cloud fax service (receive faxes as email, send via web portal) is a more practical solution than attempting to run a physical fax machine over VOIP.Can emergency services trace my location if I call 000 from a VOIP phone?
For a VoIP service that supports 000, emergency services may receive the address information held in the IPND, but it may not represent the caller's current location. The operator may ask the caller to state their town, state and exact location. It is critical that your registered address in your VOIP provider's system is accurate and up to date. If your business moves premises, update the registered address immediately. For mobile workers using softphones from varying locations, this is a limitation to be aware of: the registered address may not match the caller's actual location.What is the alternative to VOIP for a business with poor internet?
For businesses with genuinely poor internet that cannot be improved, a mobile-first phone system is the most practical alternative. This means using business mobile plans as the primary phone lines, with a virtual number layer (a 1300 or geographic number from a cloud routing service) that presents a professional business number to callers and routes to the relevant mobile. This approach does not need a fixed internet connection and scales easily by adding mobile plans rather than SIP trunk channels.Is VOIP reliable enough for a medical or allied health practice?
Yes, for most Australian metro and regional practices with good NBN connections. Medical practices are heavy phone users and VOIP's multiple-line capability, voicemail to email, and call recording features are well suited to the use case. The specific things to check: confirm 000 support and registered address accuracy, confirm call recording compliance with your professional obligations (check AHPRA and relevant body guidelines), and ensure you have a mobile fallback for staff on call during NBN outages.Not sure whether VOIP, a mobile-first setup, or a hybrid approach is right for your specific situation? Tell us the details and we will give you a straight answer.
Get a Recommendation