Canadian local VoIP providers have emergency-service obligations, but the call path and location information depend on whether the service is fixed or nomadic and on the provider’s implementation. A nomadic caller should tell the emergency operator their current location. A registered address may be used as a fallback when the caller cannot provide a location. Confirm the provider’s procedure and maintain the information it requires for your users.
How VoIP emergency calling differs from legacy lines
A fixed line is associated with a service location. A nomadic VoIP user may call from different places over an internet connection. The CRTC says a nomadic emergency operator should first determine the caller’s location verbally; the registered service address is a fallback if that fails. Explain this distinction to users and ask your provider how its specific devices and applications behave.
Stale location information can delay help if a caller cannot communicate their current location. Keep provider records current, and instruct callers to state the emergency location and a callback number when asked.
Source: the CRTC guide to fixed and nomadic VoIP 911 and its local VoIP provider obligations.
Provider obligations vs your responsibilities
What to expect from your VoIP or UCaaS vendor
Ask each proposed provider to document its emergency-call path, the information shown or requested during a call, how location records are updated, and any limitations for softphones, mobile apps or remote workers. Request a demonstration for the sites and user types in your actual order.
What your team must operate
Assign an owner for the location information your provider requires. Update it as branches open, devices move or remote users change their usual location. Include this check in provisioning and deprovisioning, and reconcile records periodically with active users and sites.
Multi-site and hybrid workforce considerations
Map every branch and remote-work use case to the provider’s emergency-calling setup. Do not assume a shared main number or head-office record represents the caller’s location. Give nomadic users clear instructions to state their current location to the operator and to keep any required provider record current. Confirm what happens on each supported device before deployment.
SIP trunking behind an on-prem PBX has its own emergency-routing configuration to verify. 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 service may be unavailable during an internet or power outage. Ask the provider whether its emergency calling remains available over the proposed backup path, what equipment needs power, and which alternative calling method staff should use if it fails. Validate the plan with the provider’s coordinated test process before treating it as dependable.
Pre-go-live checklist
- 01Confirm your provider supports emergency calling for every Canadian site on the contract.
- 02Confirm the emergency-location information and update method for each site and nomadic user scenario — not just the billing address.
- 03Validate emergency routing only through the provider’s documented, coordinated test process; do not make an unarranged 911 test call.
- 04Document who updates locations when employees move, sites open, or remote users are provisioned.
- 05Verify how softphones and mobile apps determine location, including what happens when a user moves.
- 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.
- 10Review location records when sites or users change, and repeat a documented audit on a defined schedule.
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? Do not place an unarranged 911 test call. Follow the provider’s documented validation process and coordinate any test involving emergency services.
How does the platform handle nomadic users and mobile apps? Ask whether the client uses location permission, a registered address, manual selection or another method, and what the caller must communicate.
What happens to emergency calling during a platform or WAN outage? Document the answer in your runbook, not just the sales deck.