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
Sentinel SBCs secure and interconnect SIP networks across virtual and appliance deployments. Microsoft lists the Mediatrix Sentinel Series for Teams Direct Routing with specified DGW firmware.
Up to 20,000 sessions
Microsoft Teams Direct Routing
Virtual and appliance deployment
Microsoft Direct Routing listing: Mediatrix Sentinel Series
The Microsoft list identifies M5 Technologies (previously known as Media5 Corporation), Mediatrix Sentinel Series, DGW 48.0.2340; DGW 48.5.2718 is recommended. This is a series-level listing for the specified firmware scope, not certification of every model, release or deployment. Confirm the exact configuration against the current Microsoft entry.
Certification scope is specific to the model and software combination in Microsoft's current listing. Do not infer certification for every Sentinel model or release; confirm applicability with the listed configuration and release-specific M5 documentation.
SESSION BORDER CONTROLLERS
What you can do with it
Compare the virtual and appliance profiles against your existing voice architecture, SIP/PBX/carrier interconnections, required interfaces, expected traffic and operational constraints. Confirm model-specific capacity and configuration in current product documentation.
4deployment platforms
20,000sessions on Sentinel CS
TeamsMicrosoft listing is configuration-specific
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 400S5: up to 2,000 SBC 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
Use this comparison as a starting point. Match the model to your existing voice architecture, physical or virtual deployment, SIP/PBX/carrier connections and required interfaces; validate traffic and capacity assumptions against 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
Teams Phone can connect through a Direct Routing boundary when the selected SBC model, software release and deployment match the applicable Microsoft listing.
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 (S5) | 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 Quote
Build the right voice architecture.
Share the product, deployment and target outcome. M5 will identify the right technical and commercial path.
PDF
Product brochures
B2B BUYER GUIDE
Which Sentinel SBC should you select?
Choose by architecture and deployment first: virtual infrastructure or an appliance, with gateway functions where required. Map the SIP trunks, PBX/UC systems, carrier connections, required interfaces and expected traffic. Then validate model-specific capacity, software release, interoperability, power/resilience needs and operational ownership against current product documentation and project acceptance criteria; do not infer that one model or configuration fits every deployment.
| Criterion | Assessment |
|---|---|
| Mini / 100 | Evaluate a physical appliance when its site deployment profile fits your architecture. Confirm model-specific capacity, interfaces, power and operating requirements. |
| 400 | Consider the 400 profile when SBC control and media gateway functions are needed together. Confirm installed modules, licensed capacity, interfaces and site requirements for the exact configuration. |
| CS | Evaluate the CS virtual profile when your organization operates a supported local or cloud virtual environment. Validate host resources, licensing, traffic assumptions and operations against current Sentinel CS documentation. |
Buyer questions
What information is needed for an SBC quote?
Provide sites and countries, expected concurrent sessions and registered users, SIP carrier and trunk details, PBX/UC platform, interfaces, deployment profile, traffic assumptions and operational requirements. Confirm final sizing and configuration with the product documentation and M5.
Can one configuration cover every country?
Do not assume so. Validate carrier interoperability, local dialing and emergency-calling requirements, interface variants, software release and any applicable approvals for each deployment with the responsible providers and authorities.
Prepare a request for your market
Include your country, sites, SIP provider, existing equipment, capacity and timeframe. M5 can identify the interoperability questions, local requirements and evaluation steps to confirm.
Request an architecture reviewRead the reference documentation
Publisher: M5 Technologies (Media5 Corporation). This guide revised: