Document operational dependency
Identify which calls, devices and workflows support safety, control, dispatch and service continuity.
Protect operational voice and modernize legacy systems across distributed, safety-sensitive sites.
Secure operational voice and modernize legacy services across distributed, safety-sensitive sites without treating phones, alarms, intercoms and control-room workflows as ordinary office endpoints.
Identify which calls, devices and workflows support safety, control, dispatch and service continuity.
Use Sentinel to establish a protected SIP boundary and Mediatrix gateways for validated legacy interfaces.
Test endpoint behavior, power, failover, monitoring and acceptance before each site cutover.
Download the PDF files directly. Use the documentation portal for configuration guides, installation procedures and release-specific information.
A starting point for your project. Review the model data sheet before ordering.

A compact SBC for a branch or a dedicated SIP edge.

A modular voice edge for sites with mixed telephony interfaces.

An SBC deployed on your virtual infrastructure.
The M5 layer sits between what must be preserved and the destination architecture, making security, translation and failure behavior explicit.
Local phones, a local IP PBX, Mediatrix gateways and Sentinel can exchange SIP calls entirely inside the organization. The voice path can remain on a private LAN, VLAN, campus network or isolated operational network.
An external connection is used only when calls must reach public numbers, remote sites or hosted services. If the required call path is entirely local, the system can stay on the private network.
Local users and systems require an explicit primary call path.
Operational communications need their own priority, security and recovery rules.
Legacy or safety endpoints remain isolated until compatibility is proven.
Sentinel, Mediatrix and DGW controls are selected around the actual communications dependency.
Central call control, Teams or management services connect through a protected route.
External reachability includes a tested alternate path where continuity requires it.
Reference flow — carrier, platform, jurisdiction and field requirements determine the production design.
Use these checkpoints to evaluate a critical infrastructure communications 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 |
Share the product, deployment and target outcome. M5 will identify the right technical and commercial path.