Study guide
4.2 Emergency Call Routing Function (ECRF) & LoST
NENA Emergency Number Professional ENP
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the NENA ENP Exam
2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture
1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1
3 Chapter 2: Modern Location Technologies & MLTS
2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act
4 Chapter 3: NG911 i3 Core Network & Security
3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow
5 Chapter 4: NG911 Location Services & Call Routing
4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements
6 Chapter 5: Public Safety Radio, Broadband & FirstNet
5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services
7 Chapter 6: Call Processing, Accessibility & Protocol Systems
6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment
8 Chapter 7: Computer Aided Dispatch & Information Systems
7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents
9 Chapter 8: GIS for Next Generation 9-1-1
8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management
10 Chapter 9: Cybersecurity & CJIS Compliance
9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning
11 Chapter 10: Telecommunications Policy, Funding & Civil Rights
10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws
12 Chapter 11: PSAP Governance, Strategy & Facility Design
11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning
13 Chapter 12: Power Redundancy, COOP & Disaster Recovery
12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases
14 Chapter 13: Emergency Incident Management & NIMS/ICS
13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS
15 Chapter 14: Procurement, Contracts & Financial Management
14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management
16 Chapter 15: Staffing Models, Scheduling & Wellness
15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD
17 Chapter 16: Training, CTO Coaching & Quality Assurance
16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service
18 Chapter 17: Employee Relations, Labor Standards & Legal Protections
17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act
19 Chapter 18: Records Governance, Liability & Public Relations
18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach
20 Chapter 19: Recruiting, Hiring, Compensation & Retention
19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning
4.2 Emergency Call Routing Function (ECRF) & LoST
Key Takeaways Explain This Topic AI
The Emergency Call Routing Function (ECRF) replaces legacy tabular selective routers by using the LoST protocol (RFC 5222) to perform spatial point-in-polygon queries against authoritative GIS boundary layers.
LoST findService queries convey caller location (GML geodetic or RFC 5139 civic) and an RFC 5031 Service URN (such as 'urn:service:sos'), returning the destination PSAP SIP URI.
The <serviceBoundary> GML polygon returned in a LoST findServiceResponse enables querying clients and proxies to cache routing decisions, preventing redundant ECRF lookups while the caller remains within that boundary.
RFC 5031 service URNs separate emergency sub-services (urn:service:sos.police, .fire, .ambulance, .marine, .mountain) from non-emergency services such as urn:service:counseling, while NENA's urn:emergency:service:responder.* URNs identify responding agencies for transfers.
When a caller's location falls outside the local ESInet boundary, the hierarchical Forest Guide (FG) routes the LoST query across a tree of LoST servers to the authoritative remote ECRF.
Last updated: September 2026
4.2 Emergency Call Routing Function (ECRF) & LoST
Quick Answer: The Emergency Call Routing Function (ECRF) is the core NG911 spatial routing engine that replaces legacy tabular selective routers. Using the Location-to-Service Translation protocol (LoST, IETF RFC 5222), the ECRF takes a caller's geographic location (conveyed in a PIDF-LO) and a Service URN (such as urn:service:sos ) and performs a real-time point-in-polygon spatial intersection against authoritative GIS boundary polygons to return the SIP URI of the destination PSAP. The LoST response includes a <serviceBoundary> GML polygon that allows clients to cache routing decisions. When nomadic callers dial 9-1-1 outside their home ESInet, the hierarchical Forest Guide (FG) discovers and routes queries to the authoritative remote ECRF.
Spatial GIS Routing vs. Tabular MSAG/Selective Router
In legacy Enhanced 9-1-1 (E9-1-1), emergency call routing relied on a rigid, multi-step tabular lookup architecture designed around the physical constraints of copper time-division multiplexing (TDM). When a 9-1-1 call arrived at an originating Central Office, the switch extracted the caller's 10-digit telephone number (ANI), matched it against a static Master Street Address Guide (MSAG) tabular range, mapped that range to an Emergency Service Number (ESN) , and routed the call across dedicated Centralized Automatic Message Accounting (CAMA) trunks to a legacy selective router.
Next Generation 9-1-1 executes a complete architectural paradigm shift: tabular, static number-based routing is entirely replaced by dynamic, real-time spatial GIS polygon intersection .
Architectural Dimension Legacy E9-1-1 Selective Routing NG911 ECRF Spatial Routing
Routing Mechanism Tabular lookup: 10-digit ANI -> MSAG record -> 3-to-5 digit ESN -> Outgoing Trunk Group Spatial intersection: Geodetic coordinate (lat/long) or parsed civic address -> Point-in-Polygon GIS query -> Destination SIP URI
Location Dependency Tied to fixed telephone billing records; wireless Phase I/II required external pseudo-ANI (ESRK/ESRD) routing Direct use of authoritative caller location conveyed inside the call signaling payload (PIDF-LO)
Boundary Representation Textual street address ranges (e.g., "Main St 100-198 Even"); cannot model irregular geographic perimeters Precise, vector-based GIS polygon layers representing exact municipal, county, and service boundaries
Provisioning Latency MSAG updates required 24 to 72+ hours of batch processing across multiple local exchange carriers Near-real-time ingestion of updated GIS layers via the automated Spatial Interface (SI)
Discipline Routing Restricted to primary PSAP routing; secondary dispatch transfers required speed-dials or tandem transfers Granular routing based on Service URNs ( urn:service:sos.* for the requested service; urn:emergency:service:responder.* for transfers)
Nomadic/IP Support Incapable of dynamically routing nomadic VoIP or mobile devices without pre-provisioned static addresses Universally routes any IP endpoint anywhere based on real-time geodetic coordinates or validated civic location
The LoST Protocol (IETF RFC 5222)
The Location-to-Service Translation (LoST) protocol, standardized in IETF RFC 5222 , is the foundational protocol used by endpoints, Originating Service Providers (OSPs), and Emergency Service Routing Proxies (ESRPs) to query the ECRF. LoST is an XML-based protocol transported over HTTP/HTTPS, employing a RESTful client-server paradigm. +-----------------------+ LoST <findService> Request +-----------------------+
- | Querying Client | ---------------------------------------------------> | ECRF Server |
- | (ESRP / OSP / CHE) | [Location (GML / Civic) + Service URN (RFC 5031)] | (LoST Engine) |
- | | <--------------------------------------------------- | |
- +-----------------------+ LoST <findServiceResponse> Message +-----------------------+
- [Destination PSAP SIP URI |
- + GML <serviceBoundary> Cache] v
- +-----------------------+
- | Authoritative GIS |
- | Boundary Polygons |
- +-----------------------+
- Structure of a LoST <findService> Query
A client constructs a <findService> request containing two mandatory components:
<location> : Contains the caller's location, formatted either as an RFC 5491 geodetic point/shape (GML) or an RFC 5139 civic address.
<service> : Contains an emergency Service Uniform Resource Name (URN) defined in RFC 5031 (typically urn:service:sos ). <!-- Example LoST findService Request -->
- <findService xmlns="urn:ietf:params:xml:ns:lost1">
- <location id="caller-point-01" profile="geodetic-2d">
- <gml:Point xmlns:gml="http://www.opengis.net/gml" srsName="urn:ogc:def:crs:EPSG::4326">
- <gml:pos>39.739236 -104.990251</gml:pos>
- </gml:Point>
- </location>
- <service>urn:service:sos</service>
- </findService>
- Structure of a LoST <findServiceResponse>
The ECRF processes the spatial query and returns a <findServiceResponse> containing a <mapping> structure with:
<uri> : The resolved destination SIP URI (e.g., sip:denver-psap@esinet.colorado.gov ).
<service> : The confirmed service URN.
<displayName> : A human-readable identifier for the target emergency communications center.
<expires> : A timestamp defining how long this routing mapping remains valid.
<serviceBoundary> : An optional GML polygon describing the boundary of the PSAP service area. This allows the querying client (e.g., a mobile device or local ESRP) to cache the routing decision ; as long as the device remains within that polygon, it does not need to re-query the ECRF for subsequent emergency calls. <!-- Example LoST findServiceResponse -->
- <findServiceResponse xmlns="urn:ietf:params:xml:ns:lost1">
- <mapping expires="2026-09-14T00:00:00Z">
- <displayName>Denver 911 Communications</displayName>
- <service>urn:service:sos</service>
- <serviceBoundary profile="geodetic-2d">
- <gml:Polygon xmlns:gml="http://www.opengis.net/gml">
- <gml:exterior>
- <gml:LinearRing>
- <gml:posList>39.75 -105.01 39.75 -104.97 39.72 -104.97 39.72 -105.01 39.75 -105.01</gml:posList>
- </gml:LinearRing>
- </gml:exterior>
- </gml:Polygon>
- </serviceBoundary>
- <uri>sip:denver-psap@esinet.colorado.gov</uri>
- </mapping>
- </findServiceResponse>
- Service Uniform Resource Name (URN) Taxonomy (RFC 5031)
In legacy 9-1-1 networks, dialed digits ( 9-1-1 ) were routed indiscriminately to a primary answering point. In NG911, call signaling relies on standardized Service URNs governed by IETF RFC 5031 . This allows networks to route sessions directly to specialized public safety entities based on incident discipline:
- Service URN Emergency Discipline / Target Entity
- urn:service:sos Universal emergency service fallback / Primary PSAP routing
- urn:service:sos.police Municipal police, county sheriff, or highway patrol dispatch
- urn:service:sos.fire Fire suppression and heavy rescue dispatch
- urn:service:sos.ambulance Emergency Medical Services (EMS) / Paramedic dispatch
- urn:service:sos.marine Coast Guard, maritime search-and-rescue, or harbor patrol
- urn:service:sos.mountain Mountain and alpine search-and-rescue units
urn:service:counseling (e.g., .mental-health , .suicide ) Counseling services; a separate RFC 5031 service, not an sos emergency sub-service
When a telecommunicator transfers a caller to fire dispatch, the NG9-1-1 Call Handling Equipment (CHE) issues a LoST query with the caller's location and a NENA responder URN such as urn:emergency:service:responder.fire , and the ECRF returns the URI of the fire agency serving that location. The urn:service:sos.* URNs describe the emergency service a caller requests; NENA's urn:emergency:service:responder.* URNs identify the responding agency for transfers and dispatch.
Point-in-Polygon (PIP) Spatial Containment Algorithms
When an ECRF evaluates a geodetic point (latitude and longitude), it executes a Point-in-Polygon (PIP) spatial containment algorithm within a spatial database (such as PostGIS):
Ray-Casting Algorithm: A theoretical ray is projected from the caller's coordinate point outward to infinity in any direction. The algorithm counts the number of times this ray intersects the edges of a PSAP boundary polygon:
Odd number of intersections: The point lies strictly inside the polygon.
Even number of intersections: The point lies outside the polygon.
Winding Number Algorithm: Computes the total number of times the polygon boundary winds around the coordinate point. A non-zero winding number indicates the point is inside the boundary. The winding number algorithm is computationally preferred when evaluating complex, self-intersecting, or concave jurisdictional polygons.
Boundary Topology Integrity: Gaps, Slivers, and Overlaps
NENA GIS standards mandate strict planar topology rules across all emergency service boundary layers. Two severe spatial defects must be rigorously eliminated during GIS data authoring: BOUNDARY GAP (Unassigned Void): BOUNDARY OVERLAP (Dual Contention):
- +------------------+ +------------------+ +------------------+==============+------------------+
- | PSAP A | GAP | PSAP B | | PSAP A | OVERLAP AREA | PSAP B |
- | Polygon | (X) | Polygon | | Polygon | (X) | Polygon |
- +------------------+ +------------------+ +------------------+==============+------------------+
- ^ ^
- [Point X lands in void; [Point X lands in both;
- Zero polygons match!] Conflicting URIs returned!]
Boundary Gaps / Slivers: Unintentional voids left between adjoining PSAP boundaries. If a caller's coordinate falls into a gap, zero polygons match, and the LoST engine returns a notFound error.
Boundary Overlaps: Erroneous slivers where adjacent jurisdictions both claim the same geographic parcel. If a caller lands in an overlap, the ECRF detects multiple conflicting PSAP URIs, creating routing ambiguity.
Default PSAP Fallback Routing & Safety Nets
Under no circumstances may an NG911 network reject or drop an emergency call due to a spatial routing failure. When a point falls into a boundary gap, when geocoding fails, or when carrier location is missing or unparseable:
LoST Default Return: The ECRF returns a pre-configured Default PSAP SIP URI provisioned for that broader geographic region (e.g., a designated regional or countywide answering center).
ESRP Default Rule Execution: If the ECRF fails to respond or returns an unresolvable error code, the Emergency Service Routing Proxy (ESRP) triggers its pre-programmed default routing rule, delivering the call to a designated primary backup facility.
Automated Discrepancy Logging: Every default routing occurrence triggered by a spatial failure automatically logs an error record with the Discrepancy Reporting Web Service (DRS) so GIS personnel can remediate the boundary defect.
Inter-ESInet Routing & The Hierarchical Forest Guide (FG)
What happens when a caller in California dials 9-1-1 using an enterprise VoIP softphone provisioned by a corporate network in New York? Or when a mobile subscriber roams across a state line near an ESInet boundary?
A local ESInet's ECRF only maintains authoritative GIS boundary polygons for its own municipal, county, or state territory. When an ECRF receives a LoST query for coordinates outside its provisioned coverage, it cannot resolve the target PSAP. It resolves this through the Forest Guide (FG) . +-----------------------------+
- | Top-Level Forest Guide |
- | (National) |
- +-----------------------------+
- / \
- / \
- +---------------------------+ +---------------------------+
- | Regional Forest Guide A | | Regional Forest Guide B |
- | (State / Regional) | | (State / Regional) |
- +---------------------------+ +---------------------------+
- / \
- v v
- +---------------------------+ +---------------------------+
- | Local ECRF (Region A) | | Local ECRF (Region B) |
- +---------------------------+ +---------------------------+
The Architecture of the Forest Guide:
LoST Mapping Architecture (RFC 5582): The Forest Guide is not a monolithic database. In the LoST mapping architecture it is the entry point that knows which trees of LoST servers are authoritative for which coverage regions (loosely analogous to the root of the DNS hierarchy).
Coverage Region Advertisements: Each Forest Guide peer advertises the broad geographic polygon boundaries (e.g., state borders or regional consortium footprints) for which its subordinate ECRFs are authoritative.
Query Delegation Flow:
The local ECRF receives a LoST query and evaluates the coordinates, determining they lie outside local coverage.
The local ECRF queries the National or Regional Forest Guide.
The Forest Guide inspects the coordinates against its coverage region database and refers or proxies the query to the authoritative remote ESInet ECRF.
The remote ECRF performs the granular point-in-polygon lookup and returns the destination PSAP SIP URI.
The originating ESRP routes the SIP session across inter-ESInet peering trunks directly to the destination network.