Europe has a simple public message for emergency access: call 112. The operational reality behind that message is more complicated.
In July 2026, EENA warned that some travellers across the EU still do not receive the same level of protection when they call for help. The warning focused on three linked issues: gaps in Advanced Mobile Location implementation, gaps in mobile-based public warning systems, and the growing risk that 2G/3G shutdowns could weaken access to emergency calls on newer networks if transition planning is poor.
For anyone working on NG112, this is not a side story. It is the reason NG112 needs to be treated as a governance program, not only a standards migration.
The promise and the gap
The European Electronic Communications Code created a stronger legal baseline for emergency communications. The European Commission's 112 policy page also points to the delegated regulation that defines effective emergency communications around timely connection to the most appropriate PSAP and the provision of contextual information derived from the user, device, or network.
That framework matters because modern emergency access is no longer only about completing a voice call. It increasingly includes:
- Accurate caller location.
- Equivalent access for users with disabilities.
- Routing to the most appropriate technically enabled PSAP.
- Text, video, and app-originated emergency communications.
- Roadmaps for national PSAP migration to all-IP communications.
- Common interoperability requirements for emergency communication apps.
The gap appears when legal obligations exist but deployment is uneven. EENA's July 2026 statement says AML has been mandatory since December 2020, yet identifies Poland, Malta, and Cyprus as still not having implemented AML. It also states that mobile-based public warning systems have been mandatory since June 2022, while Finland, Slovakia, Ireland, and Cyprus still do not comply with that requirement.
Those details should be treated carefully: national situations can change, and country profiles should be reverified against official sources before procurement or operational decisions. But the broader lesson is durable. A European emergency number does not automatically mean a uniform emergency communications experience.
Why travellers expose the weakness
Travellers make emergency systems honest because they remove local familiarity from the equation. A resident may know a local road, a landmark, or a national emergency number. A traveller may only know that 112 is supposed to work.
That raises the value of location technology. If a caller cannot describe where they are, the system has to help. AML, network-derived location, handset-derived location, and future NG112 location conveyance models all exist because the caller's voice is not always enough.
Travellers also expose roaming problems. EENA has repeatedly warned about cases where phones can make ordinary calls but may fail to complete emergency calls under some 4G/5G roaming conditions, especially as 2G and 3G networks are switched off. That is a hard problem because the failure can sit between handset compatibility, home-network configuration, visited-network support, roaming architecture, and emergency call routing.
In plain terms: the phone appearing "connected" is not proof that emergency calling works.
What this means for national authorities
National authorities need more than policy alignment. They need live assurance.
Useful questions include:
- Is AML implemented and monitored for actual delivery quality?
- Are public warnings mobile-based and reachable without an app dependency?
- Is emergency calling tested under roaming conditions, including devices bought outside the visited country?
- Are 2G/3G shutdown plans reviewed against emergency access obligations?
- Are PSAPs able to receive alternative access modes such as real-time text, video, or app-originated emergency communications?
- Are citizens and travellers told about known limitations in language they can understand?
This is where NG112 should help over time. IP-based emergency service networks can make routing, media, and contextual data more flexible. But NG112 does not remove the need for enforcement, funding, migration planning, and public accountability.
What enterprises and VoIP providers should learn
The same pattern appears in enterprise emergency calling. A cloud PBX or UC platform can be configured correctly in one country and dangerously incomplete in another. A VoIP provider may support structured location in one market but depend on different routing or validation processes elsewhere. A mobile-first workforce may be partly covered by enterprise location records and partly by wireless carrier location evidence.
That means European emergency calling programs should avoid one-size-fits-all designs. Teams should document:
- Country-level emergency numbers and routing assumptions.
- Whether 112, national numbers, or both are relevant for user education.
- Provider behavior for emergency calls from fixed, nomadic, and mobile users.
- Location source priority when enterprise data and network data differ.
- Roaming and travel guidance for staff.
- Escalation paths when a test call reaches the wrong PSAP or loses location context.
The goal is not to copy the United States E911 model into Europe. The better goal is to borrow the discipline: clear location records, tested provider handoff, routing evidence, audit trails, and explicit ownership.
Why public warning belongs in the same conversation
Public warning may feel separate from emergency calling, but operationally it belongs in the same resilience conversation. Both depend on the public being reachable through communications networks under stress. Both rely on operator participation, national authority readiness, and clear legal obligations. Both become harder when implementation varies across borders.
For NG112 planners, public warning is a reminder that emergency communications modernization is not only inbound. Citizens need to reach help, and authorities need to reach citizens.
Editorial perspective
EENA's warning lands because it challenges the comfortable story that Europe already solved emergency access with a single number. Europe solved the number. It is still solving the system behind the number.
That distinction matters for NG112. A mature emergency communications program cannot stop at "112 is available." It has to ask whether the call reaches the right place, whether location arrives, whether accessibility paths work, whether roaming users are protected, whether warnings reach people in danger, and whether failures are visible before they become tragedies.
The public message should remain simple. The engineering and governance behind it cannot be.