configure dynamic E911 location updates with the Bandwidth Emergency Calling API
domain: bandwidth.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Provision Emergency Calling API access and register your application/device inventory with Bandwidth.
Submit a dispatchable location (street address plus unit/floor/room detail per RAY BAUM's Act) per registered device or session.
Update the location dynamically as a nomadic/softphone endpoint moves, via the location update call, before or at call time.
Ensure your dialing application allows direct 911 dialing with no access-code prefix and fires an internal notification when a 911 call is placed, per Kari's Law.
Test with Bandwidth's designated test routes before going live.
Known gotchas
The Emergency Calling API works without SIP PIDF-LO extensions, but that also means your app is fully responsible for keeping the on-file location fresh — a stale location is a compliance failure, not just an inconvenience.
Kari's Law's on-site-notification requirement is separate from the dispatchable-location requirement under RAY BAUM's Act — satisfying one doesn't satisfy the other.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?