E911 Registration Error Codes
E911 Registration Error Codes
Section titled “E911 Registration Error Codes”When you enable E911 on a phone number, or change the address it uses, SIPSTACK registers that address with emergency services. If the registration cannot be completed, you see the reason and an error code, such as (Error E911-301). The same message is shown on the location until the address is registered.
A failed registration never blocks a 911 call. Calls to 911 are always routed to emergency services.
The codes are grouped by where the registration stopped:
- E911-3xx: the registration itself. The address could not be verified, or another save for the number is already in progress.
- E911-9xx: the registration could not be confirmed. It is not a problem with the address you entered.
What happens when you save
Section titled “What happens when you save”Every E911 save tells you where the registration actually stands. A save is never shown as complete before E911 is active.
| Result | What you see | What to do |
|---|---|---|
| Saved | The address is saved. | Nothing. E911 is active at this address. |
| Accepted, still processing | Your E911 address was accepted but is still being processed. E911 is not active at this address yet. | Do not save again. SIPSTACK finishes the registration on its own. Check back in a few minutes. |
| Already in progress (E911-302) | A save for this number is already in progress. Wait for it to finish, then try again. | Wait until the earlier save finishes, then save again only if you still need to change the address. |
| Could not be confirmed (E911-902) | We couldn’t confirm this registration. Treat E911 as not active and contact support. | Treat E911 as not active on this number and open a ticket with this code. |
If you use the API
Section titled “If you use the API”The same outcomes come back as HTTP status codes from PUT /api/v2/numbers/{id}/e911 and the Switchboard E911 save:
200: the registration is saved and E911 is active.202: accepted but not confirmed. The response hasdata.registrationset topendingand the “Accepted, still processing” message. It is not an error and carries no error code. Do not treat a202as confirmed, and do not resubmit.409with E911-302: another save for the same number is still in progress.409with E911-902: the registration could not be confirmed. Treat E911 as not active.
The old bulk migration endpoint, POST /e911/migrate-bandwidth, is retired and always answers 410: “This migration endpoint is retired. Re-save the E911 address on the number to register it.” To register a number, save its E911 address as described in E911.
Error codes
Section titled “Error codes”| Code | Meaning | What you can do |
|---|---|---|
| E911-301: Address could not be verified | We could not verify this address as a location emergency services can be sent to, so E911 was not registered with it. | Check the street number, street name, unit, city and postal code, then save again. If the address is correct, contact support with this code. |
| E911-302: Already in progress | A save for this number is already in progress. Wait for it to finish, then try again. | Wait until the earlier save finishes, then save again only if you still need to change the address. |
| E911-902: Could not be confirmed | We couldn’t confirm this registration. Treat E911 as not active and contact support. | Treat E911 as not active on this number and open a ticket with this code. |
The E911 enrollment fee is only charged once the registration is complete. If a registration fails, the card hold for the fee is released and you are not charged.
Contacting support
Section titled “Contacting support”If an error keeps happening, open a ticket and include:
- the error code,
- the phone number,
- the time you saw the error.