NG112 reference
Fallback Behavior
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Resilience
Fallback Behavior
Emergency systems need safe degraded operation. Missing location, unsupported RTT, unavailable PSAPs, failed DNS, bad certificates or roaming limitations must not produce mysterious call loss. The fallback path should be explicit and tested.
Ideal path fails
->Fallback rule
->Degraded but usable service
->Operational alert
What it does
Fallback behavior defines what happens when location, media, routing or network support is incomplete.
Fallback keeps callers connected when ideal NG112 behavior is not available.
How it works
- Detects missing capability or impaired path.
- Selects an alternate route, media mode or handling workflow.
- Logs degraded behavior for operational follow-up.
Key interfaces and protocols
- Routing policy
- SIP error handling
- Monitoring
- PSAP continuity procedures
Systems it interacts with
- Resilience
- Policy routing
- ESRP
- PSAP
- Testing
Common failure modes
- Fallback exists on paper but not in configuration.
- Location is dropped in alternate path.
- Call takers are unaware of degraded mode.
- Public-facing services fail silently.
Implementation considerations
- Document fallback per media and access type.
- Test normal, degraded and disaster scenarios.
- Alert humans when fallback is active.
Standards
- ETSI TS 103 480
- Operational continuity practices
Related NG112 technologies
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- ETSI TS 103 480 deliverable directory - ETSI, accessed 2026-08-31
- 5th NG112 Plugtests Report - ETSI, accessed 2026-08-31
- 6th NG112 and NG eCall Plugtests Report - ETSI, accessed 2026-08-31
- ETSI TS 103 479 deliverable directory - ETSI, accessed 2026-08-31
Last verified: 2026-08-31
Advertisement