NG911 in Canada, what businesses must do this year

October 3, 2025

Admin

Last reviewed: September 30, 2025

TL;DR: If your business uses VoIP, an MLTS (multi-line telephone system), or hosts public-facing locations in Canada, you must verify caller location data, confirm MLTS dial plans route 9-1-1 directly, ensure your telecom supplier complies with CRTC NG9-1-1 expectations, and add network/power redundancy for voice paths. Start by updating civic addresses, test a live 9-1-1 call with your vendor during a supervised window, and document retention and access rules for any recordings under PIPEDA or applicable provincial laws. We recommend a small pilot at one site, then a phased roll across other sites.

At-a-glance checklist: What businesses must do this year

Confirm your service type: fixed VoIP, nomadic VoIP, or traditional wireline with your provider.
Update and validate civic addresses for every fixed endpoint and MLTS location.
Set MLTS so 9-1-1 dials without a prefix and routes to the local PSAP.
Schedule a supervised NG9-1-1 test call with your carrier and document results.
Ensure battery/UPS and secondary internet (LTE or second ISP) for failover.
Review call recording and retention policies against PIPEDA or provincial laws.
Keep written rollback and contact procedures for cutover and porting.

Quick reference table (compact)

Situation	Must-do this year	Typical impact
Single-site retail	Confirm civic address, test 9-1-1, add LTE failover	Lower risk of misrouted calls
Multi-site with MLTS	Map endpoints to location identifiers, enable direct 9-1-1 dialing	Correct PSAP routing, faster dispatch
Remote/seasonal sites	Nomadic VoIP? Use clear signage and alternate devices	Plan for B9-1-1 limits

Image alt text suggestion: “Checklist table comparing single-site, multi-site MLTS, and remote site NG9-1-1 actions.”

What is NG911 in Canada and why it matters for your business?

NG9-1-1 (Next Generation 9-1-1) moves emergency calling from legacy phone networks to IP-based systems that can carry voice, text, photos, and video. Canada’s regulatory bodies and emergency services are moving toward NG9-1-1 architectures based on the NENA i3 standard so PSAPs can receive richer caller data and more accurate location information. CRTC guidance for VoIP providers explains obligations for local VoIP services, and the Commission has signalled NG9-1-1 adoption and GIS data work in recent decisions. NENA’s i3 documentation describes the architecture used for NG9-1-1 systems.

For businesses, the practical gap is simple: legacy 9-1-1 assumed fixed billing addresses. NG9-1-1 can route and dispatch using precise civic or X/Y coordinates — but only if your systems and supplier provide accurate location data. If you run a clinic, hotel, warehouse, or multi-floor office in Edmonton, Calgary, Red Deer, or Cranbrook, mis-mapped endpoints can send responders to the wrong floor, suite, or building. That’s avoidable with a short set of checks.

Sources and method note: Key technical and regulatory points below reference the CRTC and Public Safety Canada for obligations and NG9-1-1 direction, NENA for architecture, and the Office of the Privacy Commissioner for privacy/retention requirements. See Sources at the end for links.

How to prepare this year: a practical, role-by-role runbook

Start with discovery, then test, then remediate. Below is a 7-step runbook you can run in a single site in 7–14 days.

Inventory — List all endpoints that can call 9-1-1: desk phones, softphones, lobby phones, POS lines, alarm panels. Note MAC, extension, and physical civic address for each. Assumes a mid-market MLTS and common VoIP providers.
Confirm provider obligations — Ask your voice provider if they offer E9-1-1/NG9-1-1 services and how they populate location data. Ask for documentation of how they register endpoints with PSAPs. (CRTC requires notification and specific obligations for local VoIP providers.) CRTC: 9-1-1 Obligations of Local VoIP Service Providers.
Validate civic addresses and location IDs — For MLTS, ensure each extension maps to a unique civic address or civic + sublocation (floor, suite). If your system uses Automatic Location Identifier (ALI) or PS-ALI-like data, export and verify it against local MSAG/GIS where possible. The CRTC’s MLTS best practices explain the need for unique identifiers. CRTC MLTS best practices.
Network & power resilience — Ensure UPS on onsite voice gear and a secondary internet path (LTE modem or second ISP) for survivability. VoIP 9-1-1 can fail during power/outage; your provider’s documentation should warn about these limits. CRTC: VoIP 9-1-1 considerations.
Test call with carrier and PSAP — Schedule a supervised test. Record the PSAP response, whether they received the correct civic/sub-location, and any callback number. Log the test results and corrective items. Do not place unscheduled or prank 9-1-1 calls; follow your local PSAP test-window rules.
Fix and retest — Update MLTS dial-plan, endpoint location fields, or provider records based on test failures. Retest until PSAP confirms correct routing and location data.
Document and train — Publish a one-page 9-1-1 runbook for staff: how to call 9-1-1 from every device, who to notify internally, and where to find floor plans. Include a contact for PSAP/telecom escalations.

Diagram (text): Caller (phone or app) → Provider SBC → ESInet (NG9-1-1 network) → PSAP. For legacy interop, a Legacy PSAP Gateway bridges IP calls to TDM PSAPs. (See NENA i3 architecture.)

Image alt text suggestion: “Simple call-flow diagram: Caller → Provider → ESInet → PSAP with legacy gateway.”

Our POV: trade-offs and realistic timelines

Our POV is pragmatic: NG9-1-1 gives better data, but only where location data and network resilience exist. Don’t chase broad replacements just to “be NG9-1-1 ready.” Instead, prioritize places where lives and liability concentrate: patient floors, kitchens, pools, commercial points of sale, and heavy-traffic reception desks.

Trade-offs:

Speed vs accuracy — Quick fixes (update civic address fields) are fast but may not cover complex spaces. Investing in endpoint-level GIS mapping takes longer but delivers correct dispatch by floor/room.
Cloud voice vs on-prem MLTS — Cloud reduces local hardware, but it doesn’t remove the need for internet redundancy and location governance. If you pick cloud, insist the provider demonstrates how they push validated civic/location data to PSAPs.
Cost now vs risk later — The biggest hidden costs show up after an incident: misrouted EMS, extended downtime, or a poor insurance claim outcome. Prioritize the sites where response time matters most.

Assumes: a mix of cloud and on-prem voice, standard MLTS capabilities, and Canadian PSAPs at varying stages of NG9-1-1 adoption.

Checklist: roles and who owns it

IT/Telecom manager — Inventory devices, set MLTS dial plan, run network/power resilience tests.
Facilities/Operations — Confirm civic addresses, floor plans, door numbers; keep them updated.
Security/Front desk — Train staff on how to call 9-1-1 and to report test outcomes.
Vendor/Carrier — Provide E9-1-1/NG9-1-1 capability, registration with PSAPs, and supervised test windows.
Legal/Privacy — Ensure any recordings or enriched data are handled under PIPEDA or applicable provincial laws (PHIPA, PIPA). Office of the Privacy Commissioner guidance.

Application: three short vignettes for typical personas

Facility manager at a medical clinic (persona)

Problem: multiple exam rooms and public waiting areas. Action: map each exam room to a unique location ID in the MLTS, test supervised 9-1-1 calls showing room-level location to the PSAP, and ensure call recording workflows meet PHIPA rules (if health data are included). Result: dispatchers are sent to the right room, reducing time to patient aid.

IT director for a retail chain across Calgary and Edmonton

Problem: lots of POS devices and seasonal kiosks. Action: classify sites by risk (card-terminal sites first), add LTE failover for POS and voice, and run a pilot in one busy store. Result: payment and emergency access remain stable during ISP outages.

Operations leader for a multi-floor office with a hosted PBX

Problem: nomadic softphones and contractors who move desks. Action: enforce fixed-device registration for emergency call paths, place clear signage, and require staff to set their “current location” in the softphone client if they regularly move. Result: PSAPs get clearer location data, and internal drills become effective.

Pros and cons: simple decision matrix

Approach	Pros	Cons
Fix addresses and test only	Fast, low cost	May miss sublocation accuracy
Endpoint-level GIS mapping	Highest location accuracy	More effort, GIS maintenance needed
Cloud provider-managed mapping	Less IT overhead	Depends on vendor processes and SLAs

Common objections and pitfalls

“We already have the address in the account — isn’t that enough?” Not always. Billing addresses often map to a head office, not to each endpoint or floor. MLTS and NG9-1-1 need endpoint-level data when the emergency occurs away from billing addresses. See the CRTC MLTS recommendations for details. CRTC MLTS best practices.

“If we use mobile phones, aren’t PSAPs able to find callers?” Mobile and nomadic VoIP calls can supply location, but accuracy varies by phone, app permission, and whether the provider supplies correct location to PSAPs. NG9-1-1 improves the model, but only if upstream data are accurate and the PSAP supports the capability. For architecture detail, see NENA’s i3 overview. NENA i3.

“Does this change our privacy obligations?” Yes — richer data flowing to PSAPs and any retained recordings create privacy considerations under PIPEDA and provincial privacy laws. Consult the Office of the Privacy Commissioner for PIPEDA, and provincial privacy authorities for region-specific rules (for example, Alberta’s PIPA). PIPEDA guidance and Alberta PIPA overview.

How our company solves this

Outcome: Reduce misrouted or delayed emergency response across your sites. How we do it: We inventory endpoints, validate MLTS-to-PSAP mappings, run supervised test calls, and add layered failover for voice paths. If you want us to check your addresses and test a safe NG9-1-1 call, we can schedule it.

Key takeaways

Update and verify endpoint civic addresses — billing addresses aren’t enough.
Set MLTS for direct 9-1-1 dialing and map each endpoint to a unique location.
Test supervised 9-1-1 calls with your carrier and PSAP before a cutover.
Ensure network and power redundancy for voice paths; VoIP depends on them.
Review recording and retention policies under PIPEDA or applicable provincial laws.

FAQ

Can we test 9-1-1 without alerting emergency services?

No. Always schedule supervised test windows with your provider and PSAP. Many PSAPs publish test-call procedures; follow them to avoid false alarms.

Do we need to replace all phones to be NG9-1-1 ready?

Often no. Many changes are data and configuration work. Some legacy handsets may need adapters for endpoint-level location mapping, but replacing all handsets is not always required.

Who is responsible if 9-1-1 is misrouted?

Responsibility is shared: the business must provide accurate location info and configure MLTS correctly; providers must register accurate records with PSAPs. Document responsibilities in vendor contracts and runbooks.

Sources

“,