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
SIP Trunking
Interconnect SIP carriers and enterprise platforms with security, normalization and routing control.
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 sip trunking 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 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.
REQUIRED FOR OFF-SITE / PSTN CALLS
Carrier SIP trunk
The carrier path is needed only for calls that leave the private voice domain or arrive from public telephone numbers. Internal extension-to-extension calls can stay local.
PRIVATE CUSTOMER NETWORK
Secondary carrier
Provides an alternate route only when failover is designed and tested.
PBX / UC server
Owns extensions, call features and internal dial plans.
Users & contact center
Place and receive calls through the enterprise platform.
Operations
Reviews alarms, call records, certificates and configuration state.
PRIVATE IP NETWORK / LANLocal SIP signaling + RTP media
INTERNALSECURITY BOUNDARY
TRUST BOUNDARY
Sentinel SIP boundary
Creates a controlled demarcation for identity, routes, media, capacity and failure behavior.
OPTIONAL EXTERNAL SERVICES
Primary SIP carrier
Delivers public calling with its own SIP profile and routing rules.
Normalize SIPHide topologyControl sessionsFail over
READING THE DIAGRAM
The SBC is the controlled border between two voice domains
- Sentinel SBC
- Secures and normalizes SIP between voice domains, controls media and routing, and hides the internal network.
- SIP carrier
- Connects the organization to the public telephone network and supplies telephone numbers and external call routes.
- PBX or call server
- Controls extensions, features and call routing. It may run on-site, in a data center or as a hosted service.
- Operations
- Owns monitoring, backups, certificates, software lifecycle and the response when a route or carrier fails.
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 sip trunking 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.