Selective routers in the 911 system

Welcome! I would love to help you wrap your head around how 911 calls actually get where they need to go. Before we dive into the nuts and bolts of legacy selective routers, it would be incredibly helpful to know a little bit about you so I can tailor my explanations perfectly for your background.

I work in public safety / emergency communications.

It's fantastic to have you here! Since you work directly in public safety and emergency communications, you likely interact with the results of these systems every day, even if the underlying machinery is hidden away in a telecom closet.

Your path

How Selective Routers Work (Technical Overview)

Limitations of Legacy Selective Routers

The Shift to Next Generation 911 (NG911)

Meet the Selective Router

To understand how a 911 call gets to your headset, we have to look at the workhorse of the legacy network: the Selective Router (SR). In traditional telecom architecture, a selective router is a specialized, hardware-based switch. Its sole job is to take an incoming emergency call and dynamically determine exactly which should answer it. Instead of just blindly dumping every emergency call from an entire city into a single trunk, the selective router acts like an automated traffic cop, dividing and directing calls based on the physical location of the caller.

What is the difference between a normal telephone switch and an SR?

That is a great question, and it gets right to the heart of why emergency routing is so specialized.

While a normal telephone switch is like a postal worker who only looks at the zip code on an envelope to send it to the next town, a selective router has to open the envelope, read the exact house address, and then decide which specific local station gets to deliver it.

The Specialized Logic of the Selective Router

To understand this difference, we have to look at how they make decisions. A standard telephone switch routes calls using the dialed phone number itself (the destination). When you dial a friend, the switch looks at their area code and prefix and sends the call along a predetermined path to their phone line. But when a caller dials 911, the destination number is always the same: 9-1-1. A normal switch has no idea what to do with that because 911 isn't a physical phone line. This is where the comes in. It does the exact opposite of a normal switch: instead of routing based on where the call is going, it routes based on where the call is coming from (the originating location). To do this, it instantly snatches the caller's phone number, known as the Automatic Number Identification (ANI), and queries a specialized database called the Selective Routing Data Base (SRDB) to fetch the caller's physical address.

The Internal Decoder Ring: The ESN

Once the selective router matches the phone number to an address, it doesn't just read the street name. Instead, it translates that location into a unique three-to-five digit code called an Emergency Service Number (ESN). Think of the ESN as an internal routing tag. It represents a unique geographic boundary—an Emergency Service Zone—served by a specific combination of police, fire, and medical responders. The selective router maintains a hardcoded routing table: if a call comes in with ESN 104, the table tells the router to instantly send that voice call down the dedicated trunk line linked directly to PSAP A.

A 911 call from a landline routed through a central office to a selective router, which queries an SRDB database for ESN 104 to direct the call to PSAP A instead of PSAP B.

I've outlined this call flow above so you can see exactly how the router acts as the traffic cop between the caller and your dispatch center.

Next, we can look closer at how the router performs this translation behind the scenes using the Master Street Address Guide.

What happens if the selective router database lookup fails?

That is a scenario every dispatcher dreads, but the system is built with fail-safes so emergency calls are never simply lost in the ether. When a database query fails, the system relies on a crucial backup mechanism called Default Routing to ensure the call still reaches human ears.

The Backup Plan: Default Routing

If a caller's phone number isn't in the database, or if the connection to the drops entirely, the selective router cannot look up an address or generate an ESN. Instead of failing, the router falls back to a pre-programmed default routing plan. It looks at the physical the call arrived on and routes it to a designated, pre-assigned default PSAP for that specific trunk. While this ensures the call is answered, it comes with a major catch: because the lookup failed, the call is routed based on the incoming trunk's broad region rather than the caller's precise location. This often means the call lands at a regional center and must be manually transferred to the correct local responders.

What is the difference between default routing and alternate routering?

It is completely natural to mix these two up because they are both fallback mechanisms designed to keep 911 calls from failing. The easiest way to separate them is to look at why the fallback is happening: Default Routing handles database and data lookup failures, while Alternate Routing handles physical traffic and capacity problems at the dispatch center.

Data Failures vs. Traffic Jams

To make this concrete, let's look at how the selective router handles each situation:

Default Routing (The "Who Are You?" Fallback): As we discussed, this kicks in when the selective router receives a call but cannot figure out where it is coming from. The phone line is physically working, but the SRDB lookup fails, or the database is completely offline. Because the router does not know the caller's ESN, it drops the call into a pre-assigned default PSAP based on the incoming trunk line.
Alternate Routing (The "Line Busy" Fallback): This is triggered when the database lookup works perfectly, the router knows exactly which should get the call, but that PSAP's physical lines are down, busy, or completely overloaded.

Instead of letting the caller hear a busy signal, the selective router automatically diverts the call to a pre-designated alternate PSAP (like a neighboring county or a regional backup center) so a human still answers.

Feature	Default Routing	Alternate Routing
Trigger	Database lookup failure (missing ANI/ALI/ESN)	Destination PSAP is busy, overloaded, or offline
Router Knowledge	Doesn't know where the call is originating	Knows exactly where the call should go
Destination	Pre-assigned PSAP for the incoming trunk	Pre-programmed backup PSAP for the target agency

Does this distinction make sense based on what you see on the dispatch floor? We can look at how the physical database matching works next, or I can quiz you on this first subtopic to make sure we have legacy routing locked down.