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: Audio packets arriving out of order, causing choppy or robotic-sounding calls. VOIP is more sensitive to jitter than to raw latency.
- Packet loss: Lost audio packets cause gaps, clipping, or complete audio dropout. A VOIP call is unusable above about 3% packet loss.
- Connection instability: If the NBN connection drops frequently (even for a few seconds at a time), SIP registrations expire and phones go offline, missing calls during the gap.
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. Traditional copper PSTN lines depended on neither. The telephone exchange powered the line and it continued working through power outages and local network issues.
For most businesses, NBN outages lasting 1 to 4 hours a few times a year are an acceptable risk, especially when mitigated by mobile failover. 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, the copper network option (where it still exists and will be available for your lifetime) or a dedicated leased line may be more appropriate.
For most businesses that think they need this level of resilience, a properly configured VOIP system with 4G failover and platform-level call forwarding to mobile achieves 99.9%+ availability in practice.
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. Most hosted PBX platforms support automatic fallback to mobile when VOIP extensions are unreachable.
Situation 4: You Have Specific Regulatory or Compliance Constraints
Some regulatory environments create specific constraints on telephony that affect VOIP adoption:
000 emergency calling. All VOIP systems in Australia must support 000 emergency calling, but the implementation varies by provider. The call must connect, and the registered address must be accurate for emergency location. If your business operates in a context where 000 calls are made with any frequency (childcare centres, aged care, clinics), confirm your VOIP provider's 000 implementation and test it before relying on it. 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. The analogue signals used by fax machines are incompatible with VOIP's digital audio compression. Fax over IP (T.38) exists and some providers support it, but reliability is inferior to a dedicated fax line. 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 13-digit mobile, 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. At that point, the cost of a hosted PBX (typically $25 to $35/month for the first user) is easily justified by the additional call capacity and professionalism it delivers.
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: Usually a SIP re-registration failure caused by an unstable internet connection or a NAT/firewall issue with your router.
- 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): Almost always caused by SIP ALG being enabled on the router. Disable SIP ALG.
- Phones going offline periodically: SIP registration timeouts. Adjust the registration interval on the phones or the PBX configuration.
Most VOIP problems in Australian businesses are caused by router configuration rather than fundamental VOIP unsuitability. 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.
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. Many businesses that "tried VOIP and it didn't work" had a setup issue that was fixable in 30 minutes. 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 to a VOIP phone system without testing the internet connection for jitter and packet loss is the most common cause of poor call quality post-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. A business with a fire panel that does not work on VOIP can keep one copper line for the panel while migrating all voice calls to VOIP. 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.
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). A connection with jitter under 20 ms and packet loss under 0.5% is suitable for VOIP.
- 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. Most Australian hosted PBX providers offer a 14 to 30 day trial period. Run the trial on a separate number while keeping your existing setup live.
Will VOIP work during a power outage?
Can I keep a traditional landline and use VOIP at the same time?
Does VOIP work with old fax machines?
Can emergency services trace my location if I call 000 from a VOIP phone?
What is the alternative to VOIP for a business with poor internet?
Is VOIP reliable enough for a medical or allied health practice?
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