Business VoIP and UCaaS platforms route 911 calls over IP to your provider, who then hands the call to the appropriate emergency services network. In Canada, the CRTC requires certain telecommunications service providers to support emergency calling for fixed and nomadic VoIP services. That framework exists — but compliance on paper does not guarantee the dispatch location matches where your employee is standing. Configuration, location databases, and operational discipline still sit with your organization.
How VoIP emergency calling differs from legacy lines
A traditional business line is tied to a physical address the carrier already knows. VoIP decouples the user from that wire: the same extension might ring on a desk phone downtown, a softphone at home, or a mobile app in a hotel. Emergency services need a dispatchable location — street address, floor, suite — and VoIP systems supply that through registered location data your provider maintains.
When registration is wrong or stale, 911 may still connect, but to the wrong public safety answering point (PSAP) or with incorrect coordinates. That delay matters in a medical or safety emergency. Treat location accuracy as life-safety infrastructure, not a checkbox in the admin portal.
Provider obligations vs your responsibilities
What to expect from your VoIP or UCaaS vendor
Qualified providers offer emergency calling for Canadian numbers, a method to register civic addresses per site or user, and documentation on how calls are routed. Many platforms expose emergency response locations (ERLs), dynamic location updates, or integrations with building management systems. During procurement, ask for written confirmation that every site on your order is covered — including remote-worker scenarios if your contract includes them.
What your team must operate
Someone in your organization owns the location database. That means updating addresses when you open a branch, renovate a floor plan, or reassign hybrid workers. Offboarding should remove stale locations. Onboarding should assign the correct ERL before the user receives a dial tone. If IT provisions phones and HR moves people without telling IT, location drift is inevitable — unless you automate updates or run periodic audits.
Multi-site and hybrid workforce considerations
Each branch needs its own registered emergency address. Shared main numbers and centralized auto-attendants do not change the rule: the caller's physical location drives dispatch. For hybrid teams, decide whether remote users get home-address registration, a default office ERL with explicit acknowledgment, or a policy that restricts 911 to on-site devices only. There is no universal right answer — but an undocumented default is the wrong one.
SIP trunking behind an on-prem PBX introduces the same requirement at each trunk endpoint. If you are comparing architectures, see our SIP trunking vs UCaaS comparison and UCaaS buyer's guide for platform questions beyond emergency calling.
Outages, failover, and backup paths
VoIP 911 requires IP connectivity to your provider. When primary internet fails, softphones and desk phones on that VLAN may lose dial tone entirely — including emergency dialing. Design failover intentionally: secondary WAN links, LTE backup, or retained analog lines for alarm and elevator circuits where required. Run the same failover drill you use for production apps and confirm whether 911 still routes correctly on the backup path.
Pre-go-live checklist
- 01Confirm your provider supports emergency calling for every Canadian site on the contract.
- 02Register a civic address for each location where users can dial 911 — not just the billing address.
- 03Test 911 routing with your provider’s recommended test number or process (never dial live 911 for testing).
- 04Document who updates locations when employees move, sites open, or remote users are provisioned.
- 05Verify softphone and mobile apps inherit the correct emergency location — not a default HQ entry.
- 06Define failover if primary internet fails: cellular backup, analog line, or alternate path for emergency calls.
- 07Train staff that VoIP 911 may behave differently than a desk phone on legacy POTS.
- 08Include 911 location accuracy in your onboarding and offboarding checklists.
- 09Review provider SLA language for emergency service availability — separate from general uptime.
- 10Schedule an annual audit of registered locations against your active site list.
Questions to ask during procurement
How are emergency locations updated — API, admin portal, or ticket to support? Slow update paths become stale data. Prefer self-service with audit logs.
What test process does the provider recommend before production cutover? Never place live 911 test calls. Use provider-approved validation methods.
How does the platform handle nomadic users and mobile apps? Mobile clients often need explicit location permission or manual ERL selection.
What happens to emergency calling during a platform or WAN outage? Document the answer in your runbook, not just the sales deck.
Reviewed by the SwitchU procurement desk — last reviewed August 2026.