A European traveller does not think like a telecommunications regulator. They cross a border, keep the same phone in their pocket, and assume that 112 will work if something goes wrong. That expectation is reasonable. It is also technically and operationally demanding.

EENA's July 2026 warning that some countries still fail to protect emergency callers should be read as more than a compliance complaint. It is a reminder that emergency communications quality is uneven across Europe, especially when a caller is roaming, network technology is changing, or local emergency systems have not implemented the same location and warning capabilities.

The European Electronic Communications Code created clear obligations around emergency communications. The public experience, however, depends on national implementation, operator readiness, device behavior, PSAP capability, and cross-border coordination.

What the traveller problem reveals

The traveller scenario is a clean test of whether Europe's emergency communications model feels unified to the public. A resident may know local emergency habits, local language expectations, and local alternatives. A visitor usually does not. They need the emergency number, location delivery, routing, and operator process to work without insider knowledge.

That creates several practical risks:

  • The caller may not know the local emergency service structure.
  • The caller may not be able to describe their location accurately.
  • The caller may be roaming on a network with different emergency calling behavior.
  • The device may depend on 4G or 5G voice support that is not working correctly while roaming.
  • Caller location may be less precise if Advanced Mobile Location or equivalent systems are absent or poorly integrated.
  • Public warnings may not reach visitors if mobile-based warning systems are not fully deployed.

A country can have a working national emergency number and still perform poorly in one of those edge cases. For the person in trouble, it does not feel like an edge case.

AML is still the practical baseline

Advanced Mobile Location is not the whole NG112 story, but it remains one of the most important practical improvements for mobile emergency calling. When a smartphone places an emergency call, AML can activate location capabilities and send a more precise location to emergency services.

That matters because callers often cannot describe where they are. They may be on a rural road, in a foreign city, injured, panicked, unable to speak, or calling on behalf of someone else. Better location does not replace the call taker. It gives the call taker a stronger starting point.

For NG112 programs, AML should be treated as a baseline capability rather than a final destination. The future may include richer IP-based location conveyance, app-originated sessions, and more sophisticated emergency data. But if a country still has gaps in mobile caller location, that is a warning sign for broader modernization.

Public warning belongs beside emergency calling

Public warning is sometimes managed separately from emergency calling, but citizens experience both as part of public safety communications. When a flood, wildfire, chemical incident, attack, or severe weather event is developing, authorities may need to warn people before they call 112.

A strong mobile public-warning capability should be:

  • Fast enough to matter during a moving incident.
  • Geographically targeted enough to avoid unnecessary panic.
  • Understandable to residents and visitors.
  • Accessible to people with disabilities.
  • Reliable during network congestion.
  • Governed by clear authority and message approval processes.

The link to NG112 is resilience and trust. The same communications ecosystem that receives emergency calls also has to help authorities communicate outward during crisis conditions.

Roaming is the stress test

Roaming exposes coordination problems because it crosses commercial, technical, and regulatory boundaries. A domestic operator may understand its emergency routing model. A visited network may have its own emergency behavior. A handset may support certain bands, IMS profiles, or emergency service features in one country but not another. A caller may have no local language ability and no idea which emergency service they need.

As 2G and 3G networks retire, roaming emergency calling becomes even more important. Older networks often provided a fallback path for voice emergency calls. If that fallback disappears before 4G and 5G emergency calling works reliably for visitors, public-safety risk increases.

Mobile operators and regulators should therefore be asking hard questions before shutdown dates are treated as final:

  • Can roaming visitors place emergency calls over 4G and 5G reliably?
  • Are emergency calls prioritized and routed correctly under roaming conditions?
  • Does caller location reach the PSAP in a usable form?
  • Are there known handset or SIM profiles that fail emergency calling in the visited country?
  • What public communication exists for travellers if a transition risk is known?
  • How are PSAPs informed of network changes that could affect emergency call delivery?

This is not only a mobile-network engineering issue. It is a public-safety continuity issue.

What VoIP and enterprise teams should learn

The traveller problem has a cousin in enterprise emergency calling. A worker may join a cloud phone system from a hotel, branch office, shared workspace, home network, or mobile device. If the phone system assumes location from a billing address or static trunk assignment, emergency routing can become wrong.

Modern phone systems need to treat location as dynamic operational data. That includes:

  • Assigning civic locations to known offices and floors.
  • Mapping network identifiers such as subnets, Wi-Fi access points, and switches where supported.
  • Defining behavior for unknown, remote, or nomadic users.
  • Testing emergency calls after network and carrier changes.
  • Coordinating with VoIP providers and carriers on supported emergency routing models.
  • Keeping privacy controls clear so location is used for safety without becoming casual surveillance.

The similarity is useful: both roaming mobile callers and nomadic enterprise users break old assumptions about where a caller is.

A practical national readiness checklist

A country-level 112 readiness review should not stop at whether the number connects. It should include the messy operational questions that citizens actually depend on:

  • Does 112 work from mobile and fixed networks without charge?
  • Does it work for roaming visitors using modern 4G and 5G devices?
  • Is accurate mobile caller location available to PSAPs?
  • Are accessibility channels equivalent, reliable, and known to the public?
  • Are public warnings available through mobile-based systems?
  • Are PSAPs prepared for NG112-style multimedia and IP-originated emergency sessions?
  • Are 2G and 3G shutdowns coordinated with emergency service continuity plans?
  • Are national authorities publishing enough information for citizens, providers, and enterprises to understand requirements?

That kind of checklist is less glamorous than a next-generation architecture diagram, but it is where real safety improvements are found.

Editorial perspective

Europe has done something powerful by making 112 a shared emergency number. But a shared number is not the same as a fully shared emergency communications experience. The next phase is about closing the gaps between countries, networks, devices, and access needs.

The traveller is the right person to keep in mind because the traveller has no tolerance for institutional complexity. They only know whether help can be reached. If NG112 is going to earn public trust, it has to work for that person too.

Sources