Secure SIP boundary
Topology hiding, SIP normalization, call admission control, TLS, SRTP and rule-based routing protect the enterprise-to-carrier edge.
Products
Sentinel SBC Series
A Microsoft Teams-certified SBC portfolio spanning virtual, compact and modular appliance deployments, with DGW security, SIP normalization, survivability and rule-based routing.
Up to 20,000 sessions
Microsoft Teams Direct Routing
Virtual and appliance deployment
SESSION BORDER CONTROLLERS
What you can do with it
The Sentinel portfolio provides the same DGW-based secure SIP control plane across virtual, compact and modular hardware platforms. Select the platform by session capacity, deployment model and required telephony interfaces.
4deployment platforms
20,000sessions on Sentinel CS
TeamsDirect Routing certified
CAPABILITIES
Capabilities that matter for your project
Platform choice
Deploy virtually with Sentinel CS, at the compact edge with Sentinel Mini, or on appliance platforms with Sentinel 100 and Sentinel 400.
Operational continuity
SIP failover, registration caching, survivability, monitoring and diagnostic tools support controlled voice operations.
DEPLOYMENT FIT
Best suited for
- Microsoft Teams Direct Routing
- SIP trunk demarcation
- UC and PBX interoperability
- Branch survivability
- Carrier and managed voice services
KEY SPECIFICATIONS
Important selection data
Sentinel MiniUp to 400 sessions / 1,200 registered users
Sentinel 100Up to 120 sessions / 500 registered users
Sentinel 400Up to 2,000 sessions / 6,000 registered users
Sentinel CSUp to 20,000 sessions / 30,000 registered users
DOWNLOADS
Brochures and technical documents
Download the PDF files directly. Use the documentation portal for configuration guides, installation procedures and release-specific information.
Sentinel CS data sheetOfficial product data sheet
OFFICIAL DATA SHEETSentinel 400 data sheetOfficial product data sheet
OFFICIAL DATA SHEETSentinel 100 data sheetOfficial product data sheet
OFFICIAL DATA SHEETSentinel Mini data sheetOfficial product data sheet
OFFICIAL DATA SHEETOpen technical documentationConfiguration, installation and release resources
ONLINEProducts 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 100 SBC
A rack appliance when SIP security and legacy connectivity must share one platform.
- Selection criterion
- Required analog or digital modules and simultaneous calls.
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.
REFERENCE ARCHITECTURE
See Sentinel SBC Series in the complete voice path.
A product decision is only correct when both sides of the interface, the security boundary and the operating model are considered together.
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.
PRIVATE CUSTOMER NETWORK
Enterprise PBX
Existing call control and dial plans remain on the trusted side.
Users & contact center
Approved calls reach phones, agents and business applications.
Mediatrix gateway
Analog phones, fax, modems or PBXs can enter the SIP architecture without bypassing policy.
PRIVATE IP NETWORK / LANLocal SIP signaling + RTP media
INTERNALSECURITY BOUNDARY
SECURE VOICE EDGE
Sentinel SBC portfolio
A common DGW security and routing model across appliance and virtual deployments.
OPTIONAL EXTERNAL SERVICES
Microsoft Teams Phone
Cloud users connect through a certified Direct Routing boundary.
SIP carrier
Public numbers and inbound or outbound calling arrive from the service provider.
SIP over TLSEncrypted mediaPolicy routingLegacy interworking
READING THE DIAGRAM
Why the SBC sits in the middle
- 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.
- Mediatrix gateway
- Converts analog or digital voice interfaces into SIP/IP while preserving validated legacy equipment.
Conceptual architecture — final topology, capacity and interface configuration require validation.
PLATFORM SELECTION
One DGW security model. Four deployment profiles.
Start with scale and deployment model, then validate interfaces, high availability, carrier interoperability and lifecycle requirements.
Published maximums are selection guides, not a substitute for sizing against codec, transcoding, recording, redundancy and traffic assumptions.| Selection factor | Sentinel Mini | Sentinel 100 | Sentinel 400 | Sentinel CS |
|---|---|---|---|---|
| Deployment | Compact appliance | 1U appliance | Modular 1U appliance | Virtual / cloud |
| Concurrent sessions | Up to 400 | Up to 120 | Up to 2,000 | Up to 20,000 |
| Registered users | Up to 1,200 | Up to 500 | Up to 6,000 | Up to 30,000 |
| Legacy voice | External gateway | Optional interfaces | Modular PRI / BRI / FXS / FXO | External gateway |
| Typical fit | Branches and focused edges | SMB and hybrid sites | Large hybrid voice environments | Centralized and cloud voice |
FREQUENTLY ASKED
What to know before the next step.
Confirm deployment model, concurrent sessions, registered users, interfaces, codecs, carriers, resilience and operational ownership before choosing the final model or SKU.
Validate the exact hardware or virtual configuration, DGW release, license, power, interface modules, interoperability and support coverage.
Use the linked M5 data sheet for selection and the Media5 documentation portal for configuration, installation and release-specific guidance.
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.
PDF