[Developers]

PSAP NG911 / NG112 Integration: Next Generation Emergency Infrastructure

Legacy E911 infrastructure was designed for a world where emergency calls came from landlines with fixed addresses. Today, a caller reporting a wildfire might be sending a video from their phone, a deaf resident might be

Category: GeospatialLast Updated: Jan 9, 2026
geospatial

Overview#

Legacy E911 infrastructure was designed for a world where emergency calls came from landlines with fixed addresses. Today, a caller reporting a wildfire might be sending a video from their phone, a deaf resident might be texting from a moving vehicle, and a smart building might be triggering an automated fire alarm over IP. The PSAP NG911 / NG112 Integration module connects 911 and 112 centres to that reality.

The module enables PSAPs to transition from legacy E911 systems to IP-based NG911 / NG112 architecture with support for multimedia emergency communications, geospatial routing, and interoperability across jurisdictions. It is designed for emergency communications centres, police and fire dispatch operations, EMS coordination, and multi-agency coordination centres that need to meet NG911 / NG112 migration mandates while maintaining continuity with existing infrastructure during the transition.

Key Features#

i3 Standards Compliance Engine#

  • Emergency Call Routing Function (ECRF): Determines the proper PSAP based on caller location using GIS-based routing with polygon boundary definitions
  • Multi-jurisdictional overlap resolution
  • Time-of-day routing for consolidated centres

SIP/RTP Protocol Stack#

  • SIP Registration: Trunk registration with carrier partners supporting up to 500 simultaneous trunks
  • Automatic re-registration with exponential backoff
  • TLS transport for encrypted signalling

ESInet Connectivity Management#

  • Multi-Carrier Integration: Redundant connectivity across three paths
  • Primary carrier: Dedicated fibre connection
  • Secondary carrier: Alternative fibre path (diverse route)
  • Tertiary carrier: Wireless 5G backup for total failure scenarios

Legacy System Interoperability#

  • Selective Router Integration: Traditional CAMA/MF interfaces for continuity during transition
  • Multi-Frequency (MF) signalling emulation
  • Centralized Automatic Message Accounting (CAMA) trunks
  • ALI database query via TCP/IP connection

Emergency Call Data Management#

  • Voice Recordings: High-fidelity audio capture in Linear PCM, 16-bit, 8 kHz minimum
  • Optional wideband recording at 16 kHz for improved call quality
  • Dual-channel recording capturing caller and call-taker on separate tracks

Benefits#

  • Improved Location Accuracy: 50-metre precision enables faster dispatch and reduces wrong-address responses
  • Enhanced Caller Information: Multimedia contact types provide richer situational context for dispatchers
  • Accessibility Compliance: Text, video, and relay service support improves access for deaf and hard-of-hearing callers
  • Disaster Resilience: Automatic three-path failover prevents service disruption during outages
  • Multi-Media Support: Text, images, and video expand communication options beyond voice calls
  • Regulatory Compliance: Architecture aligns with NG911 / NG112 migration programmes and multimedia emergency communications requirements
  • Future-Ready: IP-based infrastructure supports emerging technologies as they become standardised

Use Cases#

  • Emergency dispatch centres migrating from legacy E911 to NG911 / NG112 architecture while maintaining operational continuity
  • Multi-agency coordination during complex incidents requiring shared multimedia evidence
  • Accessibility-compliant emergency communications for deaf, hard-of-hearing, and speech-impaired callers
  • Regional dispatch consolidation requiring unified NG911 / NG112 infrastructure across multiple jurisdictions
  • Island and remote emergency services establishing IP-based emergency communications with satellite or 5G connectivity

Integration#

The module connects with carrier ESInet partners via dedicated fibre and 5G backup paths, legacy selective routers through CAMA/MF emulation, ALI databases via TCP/IP, CAD systems for incident creation, and recording infrastructure for dual-channel call capture. Supports NENA i3 standards for NG911 together with NG112-aligned emergency IP interoperability patterns.

Open Standards#

  • NENA i3 (NENA-STA-010): The module's Emergency Call Routing Function, ESInet connectivity, and multimedia contact handling are built on the NENA i3 standard for Next Generation 9-1-1 architecture, the normative US reference for IP-based public-safety answering point infrastructure.
  • EENA NG112: European emergency IP interoperability follows NG112 specifications from the European Emergency Number Association, aligning call routing, location delivery, and multimedia contact types with EU PSAP migration mandates.
  • SIP (RFC 3261) / TLS: All voice and multimedia call signalling uses the IETF Session Initiation Protocol over TLS transport, enabling standards-based trunk registration, re-registration with exponential backoff, and encrypted call establishment across carrier ESInet paths.
  • RTP / SRTP (RFC 3550 / RFC 3711): Real-time voice and video media is carried over RTP, with SRTP used for encrypted media streams between the ESInet and call-taking positions.
  • PIDF-LO (RFC 4119) / LoST (RFC 5222): Caller location is delivered in Presence Information Data Format, Location Object and routed to the correct PSAP jurisdiction via the Location-to-Service Translation protocol, enabling the 50-metre precision referenced in the location accuracy feature.
  • RFC 7852 (Additional Data Related to an Emergency Call): Supplementary caller and device data, including device information and service provider identity, is conveyed using the RFC 7852 additional-data block attached to the SIP INVITE.
  • Linear PCM audio (ITU-T G.711 / G.722): Emergency call recordings are captured in Linear PCM at 16-bit 8 kHz (G.711 narrowband) with optional 16 kHz wideband capture (G.722), producing recordings that are compatible with any standards-compliant evidence management or quality-assurance platform.
  • OAuth2 / JWT (RFC 6749 / RFC 7519): Operator and system access to the module's GraphQL and REST surfaces is governed by OAuth2 bearer tokens and JSON Web Tokens, consistent with the platform-wide identity model.

Last Reviewed: 2026-01-09 Last Updated: 2026-01-09

Ready to Build?

Get started with our APIs or contact our integration team for support.