Scale in software
Deploy a compact virtual instance or size for large centralized voice environments using per-session licensing.
Products
Sentinel CS Virtual SBC
A software-based Sentinel SBC for local or cloud virtual infrastructure, supporting up to 20,000 sessions and 30,000 registered users.
Evaluate Sentinel CS for your project
Evaluation terms will be defined with our team based on your project.
- Share your proposed environment, capacity and target schedule.
- Agree on prerequisites, evaluation scope and acceptance criteria before deployment.
- Review the results and production licensing terms with the team.
20,000 SBC sessions
30,000 registered users
Local or cloud virtual deployment
VIRTUAL SESSION BORDER CONTROLLER
What you can do with it
Sentinel CS is the software-based Sentinel SBC for private cloud, public cloud and virtualized infrastructure. It delivers the same DGW secure SIP functions used across the Sentinel portfolio without dedicated hardware.
20,000concurrent SBC sessions
30,000registered users
Virtuallocal or cloud deployment
CAPABILITIES
Capabilities that matter for your project
Carrier-grade SBC control
Advanced rules, call admission control, NAT traversal, codec policy and SIP manipulation normalize diverse voice networks.
Protected signaling and media
TLS 1.3, SRTP, topology hiding, X.509 certificate management, DoS protection and rate limiting secure the boundary.
DEPLOYMENT FIT
Best suited for
- Microsoft Teams Direct Routing
- Cloud and data-center SBC
- Operator and MSP voice edge
- Centralized SIP trunking
- Multi-tenant UC interconnection
KEY SPECIFICATIONS
Important selection data
Minimum CPU64-bit Intel or AMD with hardware virtualization; 1 vCPU minimum
Memory2 GB minimum
Storage4 GB minimum; 16 GB recommended
Network1 interface minimum; 2 interfaces recommended for separation
DOWNLOADS
Brochures and technical documents
Download the PDF files directly. Use the documentation portal for configuration guides, installation procedures and release-specific information.
REFERENCE ARCHITECTURE
See Sentinel CS Virtual SBC 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
Virtual infrastructure
Customer-controlled compute hosts the virtual SBC instance.
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
VIRTUAL SBC
Sentinel CS
Virtual SBC deployed on supported local or cloud virtual infrastructure.
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.