01
Legacy endpoints remain
Elevator phones, alarms, emergency phones and analog devices may still require service.
Emergency Calling & Next Generation 9-1-1
Modern emergency calling for Microsoft Teams, SIP and legacy voice.
M5 Technologies helps organizations modernize emergency calling across Microsoft Teams Phone, SIP trunks, PBXs, analog endpoints and Next Generation 9-1-1 architectures while preserving reliability, routing control and operational continuity.
Microsoft Teams Emergency Calling
Certified Sentinel SBC Models
SIP Emergency Voice
Critical Communications
Microsoft Teams Direct RoutingUse a supported certified SBC model for Teams Phone connectivity.
Legacy device continuityPreserve compatible emergency phones, elevators and analog endpoints.
SIP routing controlApply policy, normalization and secure voice-edge design.
Migration planningMove from POTS and PBX infrastructure in controlled stages.
Emergency voice modernizationUsers and endpoints → secure control → emergency network
9-1-1 architecture
Users and emergency endpoints
Microsoft TeamsPBXElevatorsEmergency phonesAnalog devices
↓
Sentinel SBC and Mediatrix gateway layer
Teams Direct RoutingSIP securityGateway migrationRouting policyContinuity
↓
Emergency communications network
9-1-1 serviceNG9-1-1SIP carrierPSTNPublic safety network
LocateMaintain accurate emergency information.
RouteSend calls through the correct path.
ProtectControl critical SIP traffic.
Microsoft Teams Emergency CallingPlan Teams Phone emergency routing through supported certified SBC models.
Next Generation 9-1-1Prepare for IP- and SIP-enabled emergency communications.
POTS ReplacementModernize analog emergency endpoints without unnecessary replacement.
Critical Voice ContinuityDesign routing, failover and local resilience for emergency calling.
The customer problem
Emergency calling can fail when voice infrastructure changes faster than the emergency architecture.
Organizations migrating to Microsoft Teams, SIP trunks, cloud voice or POTS replacement must preserve emergency routing, location information, endpoint compatibility and continuity.
02
Teams changes call routing
Emergency calling must be included in the Direct Routing and voice migration design.
03
POTS retirement creates risk
Copper-line shutdown can isolate critical endpoints if migration is incomplete.
04
SIP needs governance
Emergency calls require controlled routing, security, failover and testing.
Legacy 9-1-1 vs Next Generation 9-1-1
Emergency calling is moving from fixed circuits to IP-based communications.
| Criteria | Legacy 9-1-1 | Next Generation 9-1-1 |
|---|---|---|
| Network foundation | Traditional telecom circuits and legacy switching | IP- and SIP-enabled emergency communications infrastructure |
| Enterprise integration | PBX, analog and fixed-line dependent | Better alignment with SIP, cloud voice and modern enterprise platforms |
| Migration challenge | Older systems may be stable but difficult to extend | Requires validated routing, security, location and continuity design |
| Best approach | Maintain until a controlled migration is ready | Modernize in phases with SBC, gateway and emergency-routing validation |
Microsoft Teams Emergency Calling
Teams Phone emergency calling depends on a validated voice and routing architecture.
For Direct Routing, Microsoft supports certified SBCs. Certification applies to specific SBC products and software versions, not to the 9-1-1 service itself, Mediatrix gateways or Audiotrix products. Confirm the current supported Sentinel model and software release before deployment.
01
Certified SBC Connectivity
Use a currently supported certified Sentinel SBC model for Microsoft Teams Direct Routing.
02
Emergency Routing
Define calling policies, carrier paths, failover and emergency-location workflows.
03
Legacy Integration
Use Mediatrix gateways for compatible analog and PBX endpoints when required.
Architecture comparison
Gateway, SBC and emergency service each have a different role.
| Component | Primary role | Emergency calling value |
|---|---|---|
| Mediatrix Gateway | Connects compatible analog, PBX, PRI or BRI systems to SIP | Preserves legacy emergency endpoints during migration |
| Sentinel SBC | Controls the SIP border, routing, normalization and security | Supports controlled enterprise and Teams Direct Routing architecture |
| 9-1-1 / NG9-1-1 Service | Receives and processes emergency calls | Provides the emergency network destination and public safety workflow |
| Combined architecture | Coordinates endpoint, gateway, SBC, carrier and emergency service | Best for resilient emergency voice modernization |
Reference architecture
From enterprise endpoint to emergency service.
Users & EndpointsTeams users, PBX phones, elevators and analog emergency devices
→
Mediatrix GatewayLegacy and analog interworking when required
→
Supported Certified Sentinel SBCDirect Routing, SIP policy, routing and security
→
9-1-1 / NG9-1-1 NetworkCarrier and public safety emergency communications
M5 products
Products used within emergency voice modernization architectures.
Deployment priorities
Emergency voice modernization requires more than replacing a line.
01
Location accuracy
Emergency information must reflect the user, device, site and applicable local requirements.
02
Failover planning
Define alternate carrier, SBC, WAN and local emergency calling paths.
03
Endpoint validation
Test analog, elevator, alarm and emergency devices before migration.
04
Operational testing
Document call flows, responsibilities, escalation and recurring validation.
FAQ
Questions about 9-1-1, NG9-1-1 and Microsoft Teams emergency calling.
What is Next Generation 9-1-1?
Next Generation 9-1-1 is the modernization of emergency communications toward IP- and SIP-enabled infrastructure.
Is 9-1-1 certified by Microsoft?
No. Microsoft certification applies to specific SBC products and supported software versions used with Teams Direct Routing, not to the 9-1-1 service itself.
How does Microsoft Teams support emergency calling?
Teams Phone emergency calling uses Microsoft voice policies, location information, supported connectivity and an emergency-service architecture appropriate to the organization and region.
Why is a certified SBC important for Teams Direct Routing?
Microsoft supports Direct Routing with certified SBCs. The certified SBC provides the supported SIP connection between Teams Phone and enterprise telephony infrastructure.
Can Mediatrix gateways help with emergency endpoints?
Yes. Mediatrix gateways can connect compatible elevator phones, emergency phones, analog devices and legacy PBX interfaces to SIP infrastructure.
Are Audiotrix products Microsoft Teams Direct Routing certified?
No. Audiotrix products are not Microsoft Teams Direct Routing certified. They are analog VoIP gateways and ATAs that may be used in a broader architecture when separately validated.
Can POTS replacement affect emergency calling?
Yes. Replacing copper lines can affect power, signaling, location, failover and endpoint behavior. These requirements should be validated before migration.
What should be assessed first?
Inventory emergency endpoints, current carriers, PBXs, SIP trunks, Teams users, locations, failover paths and applicable regulatory requirements.
9-1-1 Readiness Review
Validate emergency calling before changing voice platforms or retiring POTS.
Provide a high-level overview of your environment. M5 can help identify the SBC, gateway, SIP, legacy and continuity questions that should be resolved.
- Microsoft Teams Phone and Direct Routing
- PBX, SIP carrier and emergency routing
- Elevator, alarm and analog emergency endpoints
- POTS replacement and legacy migration
- Failover, continuity and site-level requirements