E911 Dynamic Location Routing integration and testing guide

Publisher

Bandwidth

URL

https://www.bandwidth.com/support/en/articles/12822952-e911-dynamic-location-routing-integration-and-testing-guide

Published

2026-02-11

Updated

unknown

Accessed

2026-09-30

HTTP status

200

License

proprietary; Bandwidth support site terms; no-redistribution; short excerpts and locators only

Source notes citing this source

• A Dynamic Location Routing 911 test call has the same parameters and flow as the 933 call except that the user part of the request URI is 911; while the account is in testing the call can be sent without connecting to the PSAP and is rejected, and Bandwidth can confirm the SIP request was correct. in context
• Sending Dynamic Location Routing location by value (a PIDF-LO attachment in the INVITE) requires TCP, because the attachment is likely to make the INVITE too large for a UDP packet, and the address sent must exactly match the standardized address Bandwidth returned at validation. in context
• A Dynamic Location Routing endpoint requires PIDFLOEnabled set to true, an Identifier of 10 to 30 alphanumeric characters that matches the SIP INVITE exactly, a 10-digit NANPA-valid CallbackNumber, and a CallerName of at most 50 characters; PreferredLanguage is optional and defaults to English. in context
• With E911 Dynamic Location Routing every geolocation must be prevalidated and added to the Bandwidth App before a call uses it. in context
• A Dynamic Location Routing endpoint identifier must be unique across Bandwidth; entering one already used on another Bandwidth App account returns an error. in context
• Bandwidth recommends Location by Reference for Dynamic Location Routing: the INVITE carries a Geolocation header whose URL is https://emergency.bandwidth.com/locations/ followed by the account number and the location reference, which keeps the INVITE small enough for UDP. in context
• A newly created or updated Dynamic Location Routing geolocation may take several seconds or several minutes to propagate to Bandwidth's 911 call processing servers. in context
• Because static E911 binds one address to each phone number while Dynamic Location Routing supplies the location in the INVITE at call time, static provisioning suits numbers used at one fixed place and Dynamic Location Routing suits devices that move between places. inferred in context

Cite this source record

APA

WarmTransfer. (2026, February 11). E911 Dynamic Location Routing integration and testing guide. WarmTransfer. https://warmtransfer.net/knowledge/sources/bandwidth-support-e911-dlr-guide

BibTeX

@misc{warmtransfer-bandwidth-support-e911-dlr-guide,
  title  = {E911 Dynamic Location Routing integration and testing guide},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/bandwidth-support-e911-dlr-guide},
  note   = {Bandwidth, accessed 2026-09-30}
}