Sentinel Mini SBC
A compact SBC for a branch or a dedicated SIP edge.
- Selection criterion
- Required sessions, network ports, power supply and license.
Use Case
Emergency Calling & NG9-1-1
Validate emergency routing, location, carrier and interoperability requirements before production cutover.
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.
CALL-PATH SCHEMATIC
Trace the emergency calling & ng9-1-1 path end to end.
Every device and service is part of a live operating workflow. The diagram makes the translation point, trust boundary and acceptance target visible.
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.
Use-case model — field validation remains mandatory for endpoints, carriers and safety-related workflows.
VALIDATION MATRIX
The checks that prevent a silent failure after cutover.
A emergency calling & ng9-1-1 design should answer each question before rollout, not after the first incident.
Safety, emergency, alarm and regulated services require approval from the responsible authority and service provider for the actual deployment.| Validation layer | Question to answer | Evidence to collect | Owner |
|---|---|---|---|
| Endpoint | Does the real device behave correctly over the new path? | Dialing, media and feature test | Customer / integrator |
| Network | Are latency, jitter, NAT and QoS controlled? | Capture and quality baseline | Network team |
| Service | Does the carrier support the required call or data behavior? | Carrier-accepted test result | Carrier / service owner |
| Failure | What happens during power, WAN or platform loss? | Failover and recovery test | Operations |
| Lifecycle | Who owns updates, certificates, backups and escalation? | Approved runbook and entitlement | Service owner |
FREQUENTLY ASKED
What to know before the next step.
The most common risk is assuming endpoint, carrier or network behavior instead of validating it in the actual call path.
Use a repeatable reference architecture, but confirm site-specific power, WAN, interfaces, endpoints, local routing and operational constraints.
The pilot should prove real workflows, not only dial tone: features, media quality, exceptional routes, failover, monitoring and recovery.
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.