Services · E911

E911 provisioned at turn-up. Not retrofitted after.

Every DID and trunk deployment leaves provisioning with a Registered Location on file. You get an update path you can actually find, and dispatchable-location detail where the rules demand it. Available in the 50 US states, from the FCC-licensed carrier that answers for 911 delivery directly.

The basics

What E911 actually is.

E911 (Enhanced 911) is the layer of 911 service that delivers your callback number and registered street address to the PSAP — the Public Safety Answering Point — that answers the call. On VoIP, that address is the Registered Location your carrier puts on file before turn-up.

Basic 911 just connects the call — the dispatcher has to ask where you are and hope you can answer. E911 puts the answer on screen before anyone speaks. Here is how the three generations compare.

AT A GLANCE BASIC 911 E911 NG911
What the dispatcher gets Nothing — they must ask Callback number + registered address The same, plus IP media like text
How the call routes A dialing shortcut to a PSAP On the Registered Location, via the ALI lookup IP routing on the ESInet as states transition
What changes for you Nothing to register Keep your E911 address current Nothing new — same Registered Location duties

NG911 is the FCC-tracked, IP-based next generation of the 911 network — the FCC ordered transition steps in July 2024. It changes how 911 networks carry calls, not your side of the deal: keeping the Registered Location current stays the whole job.

What you get

911 handled like infrastructure, not paperwork.

Registered Location on every deployment

Every DID and trunk leaves provisioning with a physical service address on file. The FCC has required it of interconnected VoIP providers since 2005 — collected before go-live. No number goes live location-blind.

Available in the 50 US states

SIPNEX 911 services cover the 50 US states. One carrier, one provisioning process, whether your sites are in Texas, Maine, or Alaska.

A defined address update path

Office move, new site, agent going remote — each is a Registered Location update, and you know exactly where it happens. No digging through old tickets while 911 routes on a stale address.

Dispatchable-location guidance

Street address alone doesn't cut it in a 12-story building. We walk MLTS rollouts through adding suite, floor, and unit detail to meet the RAY BAUM'S Act standard.

Kari's Law turn-up checks

Our turn-up checklist covers the MLTS side. We confirm 911 and 9911 both complete from your dial plan, and point the on-site notification at a destination someone actually monitors.

The carrier answers for it directly

SIPNEX is the FCC-licensed carrier serving your interconnected VoIP traffic. The 911 delivery duties are ours directly — not diluted through a reseller chain nobody can pin down.

How it works

Four steps, all before your first call.

01

Collect the real address

At order, we collect the physical service address for every site and DID — where the endpoints sit, not where the invoices go. Multi-site rollouts register each site separately.

02

Add dispatchable detail

Suite, floor, and unit numbers go on the record for multi-floor and campus buildings. A responder then gets more than a street address and a lobby to stand in.

03

Provision and confirm

The Registered Location goes into the ALI (Automatic Location Identification) database the 911 network reads, before the deployment goes live. We confirm with you what is on file for each number — so you can verify it without a live 911 test call.

04

Update as you move

Relocations, new floors, remote agents — you send the change, we update the E911 address on file. The path is written down at turn-up, not made up during an emergency.

The call itself

How an E911 call routes.

01

You dial 911

The call leaves your PBX or endpoint on a SIPNEX DID or trunk — no prefix, no special dialing, nothing to remember.

02

The network reads the ALI record

The 911 network looks up the Registered Location tied to your number and selects the PSAP that covers that address.

03

The dispatcher answers, informed

Your callback number and E911 address are already on screen when the call is picked up. Nobody has to ask where you are.

Three steps, one dependency — the address on file. The nomadic-use rules and the full mechanism live in our E911 for VoIP guide.

Side by side

911 service at turn-up vs retrofitted later.

AT STAKE PROVISIONED AT TURN-UP RETROFITTED LATER
Registered Location On file before the first call Collected after go-live, if ever
Multi-site addresses One record per site Headquarters address everywhere
Floor / suite detail Provisioned with the deployment Street address and a lobby
Dial plan (911 and 9911) Verified at cutover Assumed from the old install
On-site notification Pointed at a monitored destination Whatever the installer left
Address update path Documented in your move runbook Discovered during an emergency
Who answers for delivery The FCC-licensed carrier, directly A reseller chain, eventually
The rules

Three regulatory layers, one turn-up.

The 2005 VoIP E911 order

Interconnected voice over Internet Protocol (VoIP) providers must deliver 911 calls with a callback number and the caller's Registered Location to the right PSAP. They must collect that address before go-live and give customers an easy way to update it. Customers cannot opt out of 911. These are the carrier-side duties SIPNEX carries — and provisions against at turn-up.

Kari's Law

Applies to multi-line telephone systems (MLTS) manufactured, imported, sold, leased, or installed after February 16, 2020. Users must be able to dial 911 with no prefix or access code. The system must also notify a front desk, security office, or designated contact when a 911 call is placed.

RAY BAUM'S Act §506

Requires dispatchable location information with every 911 call. That means the street address plus the apartment, suite, floor, or room a responder needs to find the caller. Deadlines have passed: January 6, 2021 for fixed MLTS devices, January 6, 2022 for non-fixed devices like softphones and remote endpoints.

The obligations legacy telephone services carried for decades now sit with interconnected VoIP. And this is only the summary. The full breakdown — nomadic use, who does what, and the eight-item deployment checklist — lives in our 911 requirements guide for VoIP.

Who this is for

Where emergency calling goes wrong without a plan.

PBX and MLTS operators

If you run a PBX behind SIP trunks, you wear two hats: the carrier's customer and the MLTS operator. Kari's Law dialing, notification, and per-device location are on your side of the line — our turn-up checklist covers them alongside the trunks themselves. See SIP trunking service.

Multi-site businesses

Every site needs its own Registered Location — a headquarters address covering twelve branches is the exact failure the rules target. Numbers for each site are provisioned with each site's address. See DID numbers.

Dialer operations with DID pools

Large caller-ID pools don't exempt the operation from 911. The trunk your agents dial from carries the duties. Each operating site gets its Registered Location on file at turn-up — separate from how the outbound pool is managed. See VICIdial carrier.

Life-safety lines leaving copper

Elevator phones, fire alarm panels, and security lines moving off POTS still have to reach emergency services with the right address. 911 provisioning is part of the replacement, not an afterthought to it. See POTS replacement.

Hospitals and multi-building campuses

Dispatchable location matters most where a street address is least useful — a campus with wings, floors, and outbuildings. Location detail is provisioned per building and floor, not per parking lot. See hospital phone systems.

Frequently asked

About 911 provisioning with SIPNEX.

Where is SIPNEX E911 service available?
SIPNEX E911 service is available in the 50 US states. Within that footprint, every DID and SIP trunk deployment is provisioned with a Registered Location before it goes live. That address routes a 911 call to the correct public safety answering point and appears in front of the dispatcher.
What address should I register for a SIP trunk?
The physical service address where the endpoints actually sit — not the billing address, not headquarters. If you operate multiple sites, each site gets its own Registered Location. In multi-floor buildings, add suite, floor, or unit detail. That lifts the record to the dispatchable location standard instead of the bare street-address minimum.
How do I change my 911 address after turn-up?
Your 911 address — the Registered Location on file — is what your 911 calls route on. To change it, send SIPNEX the telephone number or trunk and the new physical address, and we update the record. Do it before placing calls from the new location; until the record changes, 911 routes on the old address. Office moves, new sites, and agents going remote are all Registered Location updates. Make them a line item in your move runbook.
Do outbound dialer DIDs need 911 provisioning?
911 rides the trunk your stations dial out on. What matters is the Registered Location of each physical site where agents sit — that gets provisioned at turn-up. A DID pool used for outbound caller ID doesn't change this. The numbers point back to registered operating sites. A multi-site operation registers every site, not one headquarters address for the whole pool.
Does enhanced 911 work for remote agents on softphones?
It works the way all VoIP 911 works. The call routes on the Registered Location on file, not on where the softphone happens to be. A VoIP call carries no cell site or GPS fix the way a mobile call does, so the address on file is everything the dispatcher gets. A remote agent must have a current address registered and must update it on every move. The RAY BAUM'S Act deadline for non-fixed devices passed on January 6, 2022. Off-premises softphones sit inside the dispatchable location rule, not outside it.
Can I place a test call to 911 to verify my setup?
Not without coordinating first. Live 911 test calls tie up real public safety answering points (PSAPs), so never place one without agreeing on the method with your carrier first. Ask SIPNEX to confirm the Registered Location on file for each number instead. We can verify what the 911 system will see without an unplanned call to a dispatch center.
Is 911 compliance my responsibility or my carrier's?
Both, split by role. SIPNEX, as the carrier, delivers 911 calls with a callback number and your Registered Location to the right PSAP. We collect the address before go-live and give you an update path. If you run a PBX or hosted system, you are the MLTS operator. Direct 911 dialing with no prefix, the on-site alert, and per-device location detail sit on your side. Your account admin keeps every address current. We flag all three layers at turn-up so nothing falls in the gap.
Is VoIP E911 the same as wireless E911 on a cell phone?
No. Wireless E911 locates the handset under the FCC's Phase I and Phase II rules. The network passes cell-site data first, then the caller's latitude and longitude, to accuracy standards of 50 to 300 meters. VoIP E911 does not locate anything. It routes on the Registered Location your carrier holds on file. That is why the address you register decides everything on a VoIP deployment.
What is a PSAP and which one answers my 911 call?
A PSAP — Public Safety Answering Point — is the call center that answers 911 for a given area. It sends police, fire, or EMS. The United States has thousands of them, each covering its own area. On VoIP, the PSAP serving your Registered Location takes your call. That is why the address on file decides which center picks up and what shows on the dispatcher's screen.
Why is there an E911 fee line on a VoIP bill?
State and local governments fund their 911 programs through fees on phone service, and carriers must collect them and pass them through. Each state — sometimes each county or city — sets its own amount. It is not a SIPNEX add-on. If your sites span several states, expect the line item to differ from one bill to the next.

911 handled before the first call.

Tell us your sites, your platform, and how many numbers you're deploying. Emergency calling is provisioned with the deployment — Registered Location per site, dispatchable detail where it applies, update path written down. If the trunks aren't in place yet either, start with our SIP trunking service.

Or call direct: (833) 665-2220