Map the call flow
Document endpoint identity, location, routing, carrier handoff and on-site notification requirements.
Solutions
Emergency Calling & NG9-1-1
Design secure voice interconnection for emergency calling while validating location, routing, carrier and regulatory requirements.
Emergency route validation
Location-aware planning
Operational testing
EMERGENCY CALLING & NG9-1-1
What you can do with it
Design and validate emergency call routing across Teams, SIP trunks, PBXs and legacy endpoints with explicit attention to location, carrier behavior and operational testing.
Locationrouting-critical data
Validatedcarrier call flow
Resilientoperational path
CAPABILITIES
Capabilities that matter for your project
Control the SIP boundary
Use Sentinel routing and normalization to connect enterprise platforms with the selected emergency services path.
Test acceptance
Validate normal, failover and migration behavior with approved test procedures and responsible stakeholders.
DEPLOYMENT FIT
Best suited for
- Teams emergency calling
- NG9-1-1 interconnection
- Campus and facility phones
- Critical infrastructure
- Legacy emergency endpoints
KEY SPECIFICATIONS
Important selection data
Core controlsRouting, SIP normalization and secure interconnection
Required inputsLocation, carrier, jurisdiction and endpoint data
AcceptanceDocumented test and escalation plan
DOWNLOADS
Brochures and technical documents
Download the PDF files directly. Use the documentation portal for configuration guides, installation procedures and release-specific information.
Products to compare
A starting point for your project. Review the model data sheet before ordering.
Sentinel Mini SBC
A compact SBC for a branch or a dedicated SIP edge.
- Selection criterion
- Required sessions, network ports, power supply and license.
Sentinel 400 SBC & Gateway
A modular voice edge for sites with mixed telephony interfaces.
- Selection criterion
- Interface modules, session license, power and resilience requirements.
Sentinel CS Virtual SBC
An SBC deployed on your virtual infrastructure.
- Selection criterion
- Supported hosting environment, CPU resources and licensed capacity.
SOLUTION BLUEPRINT
How Emergency Calling & NG9-1-1 changes the voice path.
The M5 layer sits between what must be preserved and the destination architecture, making security, translation and failure behavior explicit.
NO PUBLIC INTERNET REQUIRED
Private LAN / isolated IP network
Local endpoints, gateways, notification devices and an on-site call server can communicate on the private network. Local survivability must be designed and tested for the actual site.
REQUIRED TO REACH EMERGENCY SERVICES
Approved carrier / emergency route
A completed emergency call still requires the approved external route, correct location information and service-provider availability. Local operation alone does not provide public emergency reachability.
LOCAL / ISOLATED OPERATIONAL NETWORK
Calling endpoint
Local users and systems require an explicit primary call path.
Location & policy
Operational communications need their own priority, security and recovery rules.
Emergency destination
Legacy or safety endpoints remain isolated until compatibility is proven.
PRIVATE OPERATIONAL IP NETWORKLocal SIP signaling + RTP media
INTERNALSECURE + SURVIVABLE
Resilient M5 voice boundary
Sentinel, Mediatrix and DGW controls are selected around the actual communications dependency.
Site-local continuityApproved phones, gateways and call control can stay inside the site network. Internet is not inherently required for internal communications.
CONTROLLED EXTERNAL ROUTES
Cloud / central services
Central call control, Teams or management services connect through a protected route.
Carrier / public network
External reachability includes a tested alternate path where continuity requires it.
Primary routeLocal continuityEncrypted interconnectTested failover
READING THE DIAGRAM
What must remain available in emergency calling & ng9-1-1
- Calling endpoint
- The physical location, users and local equipment that depend on voice during normal operations.
- Location & policy
- The operational workflow—not just the telephone—that defines priority and recovery time.
- Sentinel SBC
- Secures and normalizes SIP between voice domains, controls media and routing, and hides the internal network.
- Mediatrix gateway
- Converts analog or digital voice interfaces into SIP/IP while preserving validated legacy equipment.
Reference flow — carrier, platform, jurisdiction and field requirements determine the production design.
BEFORE / AFTER
Turn an uncontrolled migration into an engineered transition.
Use these checkpoints to evaluate a emergency calling & ng9-1-1 project before product selection or cutover.
The recommended design depends on the deployed carrier, PBX or UC platform, interfaces, call volume, failure modes and regulatory context.| Decision area | Uncontrolled approach | M5 architecture | Acceptance evidence |
|---|---|---|---|
| Interoperability | Assume systems will connect | Normalize signaling and media at a defined boundary | Documented end-to-end call tests |
| Security | Expose internal voice domains | Apply identity, topology and transport controls | Approved routes, certificates and logs |
| Continuity | Cut over every site together | Preserve required services and phase migration | Failover, rollback and exception tests |
| Operations | Treat go-live as the finish line | Assign monitoring, updates and escalation ownership | Runbook, backups and support entitlement |
FREQUENTLY ASKED
What to know before the next step.
Document every carrier, PBX or UC platform, endpoint class, site, interface, call flow, security boundary and failure requirement.
Yes. A phased architecture can preserve approved services while routes, sites and users move in controlled stages with rollback criteria.
Normal and exceptional calls, encryption, routing, media, failover, monitoring and operational ownership should all pass documented tests.
READY FOR THE NEXT STEP?Request a free review
Build the right voice architecture.
Share the product, deployment and target outcome. M5 will identify the right technical and commercial path.