SIP normalization
Rule-based routing and SIP header manipulation reconcile carrier, PBX and UC implementations at the network boundary.
Products
Sentinel Mini SBC
A compact ARM session border controller supporting up to 400 concurrent sessions and 1,200 registered users for secure branch, UC and Microsoft Teams voice edges.
400 SBC sessions
1,200 registered users
2 × 2.5 GbE
COMPACT SESSION BORDER CONTROLLER
What you can do with it
Sentinel Mini brings the Microsoft Teams-certified DGW SBC software to a compact ARM appliance for secure SIP interconnection at branches, remote sites and focused enterprise voice edges.
400concurrent SBC sessions
1,200registered users
2 × 2.5 GbEEthernet interfaces
CAPABILITIES
Capabilities that matter for your project
Security by design
TLS 1.3, SRTP, topology hiding, certificate management, call-rate controls and a stateful firewall protect signaling and media.
Branch continuity
SIP failover, registration caching, survivability, QoS and remote diagnostics support distributed deployments.
DEPLOYMENT FIT
Best suited for
- Microsoft Teams Direct Routing
- Secure branch SIP trunks
- Remote and mobile users
- Hosted UC survivability
- Compact managed voice edge
KEY SPECIFICATIONS
Important selection data
ProcessorQuad-core ARM Cortex-A55 at 2.0 GHz
Memory / storage2 GB DDR4 / 8 GB eMMC
PowerUSB-C 5 V, 3 A; power supply not included
Dimensions84 × 76 × 33 mm
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 Mini 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
Branch office
IP phones and local users share a compact protected edge.
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
Sentinel Mini
Compact secure edge for branches, focused UC deployments and Teams voice.
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.