Emergency Calling & E911
Route every emergency call to the right answering point with a location a dispatcher can act on - E911 with dynamic location for the US and Canada, 112/999 routing internationally, and Kari’s Law and RAY BAUM’s Act compliance built in.
US & CA
E911 with dynamic location
112 / 999
Emergency routing internationally
Real-time
Location updates via API
What is Emergency Calling & E911?
When someone dials 911, 112 or 999 from a desk phone, softphone or Teams client, the call has to reach the correct public safety answering point with a location a dispatcher can act on - whether that user is in head office, at home or in a hotel. Dollu’s emergency calling service provides that capability across our SIP trunking, enterprise voice and Teams Direct Routing products, with E911 and dynamic location for the United States and Canada, and national emergency routing internationally wherever the number type and regulator allow it.
In the US and Canada every number or endpoint is associated with a validated dispatchable location - street address plus floor, suite or room - held in our emergency location database and pushed to the PSAP routing infrastructure. Locations can be static per number, per site or per device, or dynamic: your network or UC platform updates a user’s location automatically from the Wi-Fi access point, LLDP switch port, IP subnet or the address a nomadic user confirms in their client. Calls route to the correct PSAP with the location attached, and a configurable notification reaches on-site security or reception at the same time.
The service is designed to satisfy US federal requirements for multi-line telephone systems. Kari’s Law is met by direct 911 dialling with no prefix and simultaneous notification to a designated contact, and RAY BAUM’s Act by conveying dispatchable location for fixed and non-fixed devices. Canadian VoIP 9-1-1 obligations under CRTC rules are covered through our Canadian routing partner. Address changes, additions and validations are made through the portal or a REST API, so provisioning can be automated from your UC platform, HR system or network management tool rather than maintained by hand.
Outside North America the picture is fragmented: emergency numbers, routing methods and location requirements are set nationally, and many countries only permit emergency calling on numbers with a registered local address. Dollu routes 112, 999, 000 and other national emergency numbers to the correct handling authority for supported number types in the UK, EU member states, India, Australia and other markets, applies each country’s address-registration rules at provisioning time, and clearly flags in the portal where a number type - for example some non-geographic or virtual mobile ranges - cannot legally carry emergency calls.
Why choose Dollu for e911 & emergency.
The advantages of buying from a carrier that owns its network, interconnects and operations - rather than a reseller.
Compliance without a project
Kari’s Law, RAY BAUM’s Act and CRTC obligations are met by configuration on our platform, with audit reports you can hand to legal, insurers or a regulator.
Accurate location for hybrid workforces
Dynamic and user-confirmed locations mean a home worker’s call goes to their local PSAP with their home address, not the head-office address on the trunk.
Faster response, safer sites
Floor and room-level location plus instant notification to security or reception gets responders to the right door and lets your own staff assist before they arrive.
Automated, auditable provisioning
Bulk uploads, API updates and validation against postal and MSAG data keep addresses correct as people and desks move, with a full change history per number.
Consistent policy across countries
One place to see which numbers can carry emergency calls in which countries, what address is registered and what still needs attention.
Capabilities in detail.
Everything included with Emergency Calling & E911 - the platform features, options and controls you get from day one.
- 01
E911 routing for the US and Canada
Calls to 911 route to the correct PSAP based on the caller’s registered or dynamic location, with address delivered to the dispatcher; coverage of all US states and Canadian provinces through certified routing partners.
- 02
Dynamic and nomadic location
Location determined per call from network mapping - Wi-Fi BSSID, LLDP chassis and port, IP subnet - or from the address a user confirms in a softphone or Teams client when off-network.
- 03
Kari’s Law notifications
Configurable email, SMS, screen-pop and voice notifications to security, reception or a facilities team when 911 is dialled, including the caller’s extension and location.
- 04
Address provisioning and validation API
REST endpoints and portal tools to add, validate and update addresses per number, endpoint or user, with MSAG and postal validation and bulk CSV import for large estates.
- 05
UC platform integration
Microsoft Teams location information service and dynamic emergency calling, Zoom Phone nomadic 911, Webex Calling and on-premises PBXs using ELIN or PIDF-LO over SIP.
- 06
International emergency routing
112, 999, 000 and national equivalents routed to the correct handling authority for supported number types in the UK, EU, India, Australia and other markets, with per-country address rules applied at provisioning.
- 07
Test calling
Non-emergency test numbers that read back the address on file for a number or endpoint, so you can verify configuration for every site and user without calling a live PSAP.
- 08
Reporting and audit trail
Logs of every emergency call with location delivered and notifications sent, address change history per number and compliance summaries per site and country.
How it works.
From first conversation to live traffic - a tracked, engineer-led onboarding with a named owner at every step.
- Step 01
Inventory
We map your sites, number ranges, users, softphone and Teams estates and existing emergency configuration, and identify which countries and number types are in scope.
- Step 02
Provision addresses
Dispatchable locations are loaded by bulk import or API, validated against MSAG and postal data, and linked to numbers, endpoints or users; international address registrations are filed per country.
- Step 03
Integrate location and notification
Network maps for dynamic location, Teams or Zoom emergency policies and Kari’s Law notification recipients are configured and tested with your IT and facilities teams.
- Step 04
Test and operate
Test calls confirm the address on file for each site and user type. The NOC monitors emergency routing continuously and changes flow through the portal or API as your estate evolves.
Premium, Standard or Wholesale.
Every destination on the Dollu rate deck is offered in up to three quality tiers. Pick per destination - or per customer - and mix them on one interconnect.
| Dimension | Premium (CLI-guaranteed) | Standard | Wholesale |
|---|---|---|---|
| CLI delivery | Guaranteed - the originating number is delivered intact to the called party | Best effort - CLI is normally delivered but not contractually guaranteed | Not guaranteed - CLI may be withheld or replaced on some routes |
| Route type | Direct operator interconnects and Tier-1 partners only | Direct and vetted partner routes, quality-steered in real time | Least-cost blended routes, swapped freely to hold the price |
| Typical ASR band | Highest | High | Variable |
| PDD | Lowest | Low | Variable - can rise on multi-hop transit |
| Best for | Contact centres, retail and enterprise traffic, OTP voice calls - anywhere the called party must see who is calling | Business traffic where quality matters and CLI is helpful but not mandatory | High-volume carrier, dialler and call-centre traffic where price per minute dominates |
| SLA | Per-destination ASR, ACD and PDD targets with service credits | Quality targets monitored and reported; credits on core availability | Core availability only; route quality is managed, not guaranteed |
| Price position | Highest | Mid | Lowest |
All three tiers ride the same SIP interconnect, portal and CDRs - the tier is chosen per destination prefix, so you can move traffic between them without a new set-up.
Who uses this and why.
Typical deployments across carriers, enterprises, platforms and contact centres.
Enterprises with hybrid and remote staff
Home workers, travelling employees and hot-desking offices where a static per-trunk address would send responders to the wrong place.
Microsoft Teams and UC deployments
Organisations moving voice to Teams, Zoom or Webex that must retain compliant emergency calling with dynamic location across every site and client.
Campuses, hospitals and schools
Large multi-building sites that need floor and room-level location and immediate notification of on-site security or a nurse station.
Hospitality and multi-tenant buildings
Hotels, serviced offices and residential complexes with MLTS obligations under Kari’s Law and RAY BAUM’s Act for every room and suite.
Multinational offices
Companies that want one emergency-calling policy and one reporting view across US, Canadian, UK, EU and Asia-Pacific offices.
Technical & commercial specifications.
Key parameters at a glance. Ask us for the full service description and SLA document.
| Coverage | E911 in all US states and Canadian provinces; 112/999/000 internationally |
|---|---|
| Location types | Static per number, site or device; dynamic per call; user-confirmed |
| Location sources | Wi-Fi BSSID, LLDP chassis/port, IP subnet, client-confirmed address |
| Compliance | Kari’s Law, RAY BAUM’s Act, CRTC VoIP 9-1-1; national rules elsewhere |
| Notification | Email, SMS, screen-pop, voice; multiple recipients per site |
| Provisioning | REST API, portal, bulk CSV; MSAG and postal validation |
| Integration | Teams, Zoom Phone, Webex Calling, SIP PBX (ELIN, PIDF-LO) |
| Testing | Address read-back test numbers; no live PSAP calls required |
| Support | 24×7 NOC monitoring; P1 response ≤ 15 min |
How Voice & Wholesale is priced.
Wholesale voice is priced from an A–Z rate deck: a rate per destination and breakout for each quality tier, billed on connected seconds. There are no setup or port fees on SIP interconnects.
We publish the model, not a public rate card - actual rates depend on destination, route class, volume and regulatory cost. See how every Dollu service is priced.
- A–Z rate deck in USD, EUR, GBP or INR
- Premium (CLI), Standard and Wholesale tiers per destination
- 1/1 billing on most destinations; 60/60 flagged on the deck
- Volume tiers from 1M minutes a month; bilateral and swap for carriers
- Rate increases with at least 7 days’ notice; decreases immediate
- Billing
- Prepaid (online top-up, auto-recharge) or postpaid net-15/30 after credit review; per-second increments
- Commitment
- None - month-to-month usage; optional volume commitments unlock better tiers
230+ destinations, A–Z.
Every country on the rate deck, in Premium, Standard and Wholesale tiers where the market supports them - over 600 direct carrier interconnects and Tier-1 partners. Country guides cover the destinations with the most traffic.
E911 & Emergency - your questions answered.
The questions customers and carriers ask us most often before they interconnect. If yours is not here, our team answers within one business day.
Still have a question?
Ask our solutions teamRelated services.
Services customers commonly combine with Emergency Calling & E911.
Bring your emergency calling into compliance.
Send us your site list and UC platforms and we will return a gap assessment against Kari’s Law, RAY BAUM’s Act and local rules, plus a provisioning plan, within five business days.
