The Optus outages sent shockwaves through Australia’s emergency services community, and for good reason. When millions of Australians suddenly couldn’t reach 000, it exposed vulnerabilities that many of you had been warning about for years. Now, the Australian Communications and Media Authority (ACMA) is taking a harder look at telecommunications resilience, and your agency’s compliance requirements are evolving.
If you’re responsible for emergency communications infrastructure, you’re facing tighter scrutiny, potentially new obligations, and legitimate questions from your executive leadership team about whether your systems can withstand similar disruptions. Let’s cut through the complexity and focus on what actually matters for your operations.
What ACMA Actually Regulates (And Why It Matters to You)
ACMA’s role in emergency communications focuses on regulating telecommunications providers, not emergency service agencies themselves. They oversee how carriers like Telstra, Optus, and other providers handle emergency calls under the Telecommunications Act 1997 and the Telecommunications (Emergency Call Service) Determination 2019.
What does this mean for your operations? ACMA ensures that telecommunications carriers properly route 000 and 112 calls, prioritise emergency traffic, and provide accurate location information. They regulate Telstra as the designated Emergency Call Person (ECP), the entity that answers initial 000 calls before transferring them to your agency.
ACMA also sets standards for telecommunications equipment interoperability, ensuring that different systems can communicate using established protocols. This becomes relevant when you’re procuring new Private Branch Exchange (PBX) or contact centre infrastructure, your systems need to interface correctly with carrier networks and meet technical standards for emergency call handling.
However, ACMA doesn’t regulate your agency’s internal operations, dispatch procedures, or how you manage calls once they reach your Public Safety Answering Point (PSAP). Those operational aspects fall under state and territory emergency services management.
Where ACMA’s regulations directly impact you is at the handoff point: your communications infrastructure must be compatible with carrier emergency call networks, support caller location data including Advanced Mobile Location (AML), and maintain the priority routing and technical standards that ACMA requires of the broader telecommunications system.
The Post-Outage Reality: Higher Standards Are Coming
Here’s what you’re probably already sensing: the regulatory landscape is shifting. ACMA has always had standards around emergency call handling, but the conversation has changed. Government and public expectations around telecommunications resilience have intensified, and your agency sits right in the crosshairs of that scrutiny.
While specific new regulations may still be taking shape, the direction is clear. Expect increasing focus on:
Network diversity and redundancy. If your PSAP relies on a single carrier or a single connection point, that’s becoming an unacceptable risk. You need genuine diversity, different carriers, different physical paths, different technologies.
Failover capabilities. When your primary systems go down, what happens? Can calls automatically reroute to backup facilities? Do your call-takers have alternative ways to communicate with dispatchers and field units? These aren’t nice-to-haves anymore.
Testing and documentation. ACMA wants evidence that your resilience measures actually work. That means regular testing of failover scenarios, documented procedures, and proof that your staff know what to do when systems fail.
Where Your Communications Infrastructure Comes Under Scrutiny
You know your Computer Aided Dispatch (CAD) system and your radio network get attention during audits and reviews. But your telephony platform, your PBX and contact centre infrastructure, deserves equal focus when it comes to ACMA compliance.
Consider what happens during a 000 call at the infrastructure level. The call arrives via Telstra’s emergency network. Your PBX needs to recognise it as priority traffic. Your contact centre platform must present it to an available call-taker immediately, regardless of queue status. Location data needs to flow through your systems into CAD. All of this needs to happen reliably, consistently, and in a way that you can demonstrate to regulators.
If you’re running older telephony infrastructure, this is where gaps often emerge. Legacy PBX systems may not have been designed with current regulatory requirements in mind. They might lack the redundancy features, the logging capabilities, or the integration flexibility that ACMA compliance now demands.
The Integration Question Nobody’s Asking (But Should Be)
Here’s a compliance angle that often gets overlooked: how well does your telephony infrastructure integrate with everything else in your emergency response ecosystem?
ACMA doesn’t just care that calls get answered, they’re concerned with the entire emergency response chain. Your systems need to support effective location data flow to CAD, enable call transfers between PSAPs during major incidents, and maintain comprehensive call records with timestamps and location data. These capabilities aren’t just operational necessities; they’re increasingly part of regulatory expectations for emergency services infrastructure.
Modern compliance requires modern integration. Your telephony platform needs open APIs, standards-based protocols, and the flexibility to connect with specialist emergency services systems like your existing CAD platform. Closed, proprietary systems that don’t play well with others aren’t just technically limiting, they’re becoming compliance liabilities.
What You Should Be Doing Right Now
Waiting for new regulations to be finalised before acting isn’t a strategy. Here’s what practical compliance preparation looks like:
Audit your current resilience. Map out exactly what happens when your primary telecommunications path fails. Be honest about the gaps. Document them. Quantify the risk.
Review your carrier diversity. Are you genuinely diversified, or are you using different services that ultimately rely on the same physical infrastructure? Real diversity is harder to achieve than it looks.
Test your failover procedures. Not on paper, actually test them. Simulate carrier outages. Verify that calls route to backup facilities. Confirm that your teams know what to do without needing to consult manuals.
Document everything. ACMA compliance increasingly means being able to demonstrate your capabilities, not just claim them. Build documentation that shows your architecture, your procedures, your testing results, and your incident response plans.
Evaluate your technology roadmap. If you’re planning infrastructure upgrades anyway, now’s the time to ensure compliance requirements are central to your specifications, not afterthoughts.
The Bigger Picture
ACMA compliance isn’t just about avoiding regulatory penalties. It’s about ensuring that when your community faces its worst day, a major disaster, a terrorist incident, a mass casualty event, your communications infrastructure doesn’t become part of the problem.
The agencies that navigate this changing regulatory environment most successfully won’t be the ones that do the bare minimum to tick compliance boxes. They’ll be the ones who use regulatory requirements as a framework for building genuinely resilient, future-ready communications infrastructure.
Your community is counting on you to get this right. ACMA is watching to make sure you do. The question is: does your current infrastructure give you confidence on both counts?
Need guidance on ensuring your emergency services communications infrastructure meets evolving ACMA requirements? Connect with specialists who understand both the regulatory landscape and the technical realities of PSAP operations.
