FCC LICENSED CARRIER ·499 FILER ·STIR/SHAKEN CERTIFIED
SIPNEX
Services · E911

E911 provisioned at turn-up. Not retrofitted after.

Every DID and trunk deployment leaves provisioning with a Registered Location on file, 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.

Provision E911 at Turn-Up → E911 Requirements Guide
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 — collected before activation, as the FCC's 2005 VoIP E911 order requires. No number goes live location-blind.

Available in the 50 US states

SIPNEX E911 service covers 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 support-ticket archaeology 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 deployments through provisioning 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: confirm 911 and 9911 both complete from your dial plan, and point on-site notification at a destination someone actually monitors.

Carrier-direct accountability

SIPNEX is the FCC-licensed carrier serving your interconnected VoIP traffic. The 911 delivery obligations 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 deployments register each site separately.

02

Add dispatchable detail

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

03

Provision and confirm

The Registered Location is provisioned before the deployment goes live, and we confirm with you what is on file for each number — so you can verify it without placing a live 911 test call.

04

Update as you move

Relocations, new floors, remote agents — you send the change, we update the record. The path is documented at turn-up, not improvised during an emergency.

Side by side

E911 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 VoIP providers must deliver 911 calls with a callback number and the caller's Registered Location to the appropriate dispatch center, collect that address before activating service, and give customers an easy way to update it. Customers cannot opt out of 911. These are the carrier-side obligations SIPNEX carries — and provisions against at turn-up.

Kari's Law

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

RAY BAUM'S Act §506

Requires a dispatchable location with 911 calls — 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.

This is the summary. The full breakdown — nomadic use, the responsibility split, and the eight-item deployment checklist — lives in our E911 requirements guide for VoIP.

Who this is for

Where E911 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 location 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 obligations, and each operating site gets a Registered Location 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 the right dispatch center with the right address. E911 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 E911 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 — the address that routes a 911 call to the correct dispatch center 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 so the record meets the dispatchable location standard, not just the street-address minimum.
How do I change my E911 address after turn-up?
Contact SIPNEX with the number or trunk and the new physical address, and we update the Registered Location on file. Do it before placing calls from the new location — until the record changes, 911 calls route 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 E911 provisioning?
911 rides the trunk your stations dial out on, so 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 that: the numbers point back to registered operating sites, and a multi-site operation registers every site, not one headquarters address for the whole pool.
Does E911 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 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, so off-premises softphones are inside the dispatchable location requirement, not an exception to it.
Can I place a test call to 911 to verify my setup?
Not without coordinating first. Live 911 test calls tie up real dispatch resources, so never place one without coordinating 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 uncoordinated 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 appropriate dispatch center, collects the address before activation, and gives you an update path. If you run a PBX or hosted system, you are the MLTS operator: direct 911 dialing with no prefix, on-site notification, and per-device location detail are configured on your side. Your account admin keeps every address current. We flag all three layers at turn-up so nothing falls in the gap.

Related Guides

More Services

SIP TrunkingSIP Trunking for PBXDID NumbersToll-FreeSMS MessagingCall TrackingHosted PBX

911 handled before the first call.

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

Provision E911 at Turn-Up → DID Numbers
Or call direct: (833) 665-2220