Sentinel Mini SBC
A compact SBC for a branch or a dedicated SIP edge.
- Selection criterion
- Required sessions, network ports, power supply and license.
Industry
Critical Infrastructure
Secure and modernize communications where voice supports safety, operations and service continuity.
Products to compare
A starting point for your project. Review the model data sheet before ordering.
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.
SECTOR ARCHITECTURE
A voice design shaped for critical infrastructure.
Office telephony, operational communications and field devices have different consequences when they fail. They should not share an undocumented migration assumption.
NO PUBLIC INTERNET REQUIRED
Private LAN / isolated IP network
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.
OPTIONAL FOR EXTERNAL SERVICES
SIP carrier, PSTN, Teams or cloud
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 / ISOLATED OPERATIONAL NETWORK
Operational sites
Local users and systems require an explicit primary call path.
Dispatch / control
Operational communications need their own priority, security and recovery rules.
Safety devices
Legacy or safety endpoints remain isolated until compatibility is proven.
PRIVATE OPERATIONAL IP NETWORKLocal SIP signaling + RTP media
INTERNALSECURE + SURVIVABLE
Critical Infrastructure protected voice core
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 critical infrastructure
- Operational sites
- The physical location, users and local equipment that depend on voice during normal operations.
- Dispatch / control
- 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.
Sector reference model — site policy, regulation and operational authority determine the final controls.
REQUIREMENTS MATRIX
Separate ordinary voice from operationally critical voice.
The critical infrastructure architecture should classify each service by consequence, dependency and recovery requirement.
Classification should be approved by the organization responsible for safety, compliance and service continuity—not inferred from the endpoint type alone.| Service class | Typical examples | Design priority | Proof before production |
|---|---|---|---|
| Enterprise voice | Users, reception, collaboration | Secure connectivity and user experience | Platform and carrier call tests |
| Facility voice | Intercoms, elevators, access points | Endpoint compatibility and local power | Device-level acceptance test |
| Operational voice | Dispatch, control room, field operations | Resilience, priority and clear ownership | Failure-mode exercise |
| Emergency services | Emergency phones and call routing | Location, reachability and supervision | Approved end-to-end procedure |
| Lifecycle | Certificates, firmware, spares, support | Repeatable governance across sites | Runbook and entitlement review |
FREQUENTLY ASKED
What to know before the next step.
The design must reflect the consequence of failure, distributed sites, legacy dependencies, security governance and the owners of critical workflows.
They may share infrastructure, but each service class should have its own compatibility, resilience and acceptance requirements.
Classify sites and services, identify operational dependencies, then pilot the highest-risk call paths before scaling the pattern.
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.