One secure voice edge
SBC policy, SIP normalization, topology hiding, TLS and SRTP protect connections between carriers, Teams, PBXs and endpoints.
Products
Sentinel 100 SBC
A 1U SBC and media gateway appliance supporting up to 120 concurrent sessions and 500 users, with secure SIP control, survivability and optional legacy interfaces.
120 SBC sessions
500 registered users
SBC plus gateway
SBC + MEDIA GATEWAY APPLIANCE
What you can do with it
Sentinel 100 combines a session border controller and media gateway in a 1U appliance for small and medium enterprises that require secure SIP control, survivability and optional legacy telephony connectivity.
120concurrent SBC sessions
500registered users
5 × 1 GbEEthernet interfaces
CAPABILITIES
Capabilities that matter for your project
Legacy interworking
Configurable E1/T1 PRI, BRI, FXS and FXO options connect selected TDM and analog systems to SIP.
Survivability and control
Local switching, SIP failover, call admission control, diagnostics and QoS preserve branch operations during service disruption.
DEPLOYMENT FIT
Best suited for
- Microsoft Teams Direct Routing
- SIP trunking
- Branch survivability
- Legacy PBX migration
- Enterprise network demarcation
KEY SPECIFICATIONS
Important selection data
Voice capacityUp to 120 simultaneous voice calls
SecurityTLS 1.3, SRTP, X.509, OCSP and DoS protection
NetworkingIPv4/IPv6, VLANs, QoS, firewall, routing and NAPT
Form factor1U; 48.5 × 19.5 × 4.4 cm
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 100 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
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
SBC + GATEWAY
Sentinel 100
1U SBC and media gateway for a smaller hybrid voice environment.
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.