E911 provisioned at turn-up. Not retrofitted after.

SIPNEX enhanced 911 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.

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.

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.

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.

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.

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.

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.

No. Wireless enhanced 911 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. The VoIP service 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.

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.

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.