Certified voice edge
Use a Sentinel SBC as the controlled boundary between Microsoft Teams Phone, the carrier and enterprise voice systems.
Solutions
Microsoft Teams Direct Routing
Connect Teams Phone to carriers, PBXs and existing voice systems while retaining routing, security and interoperability control.
Connect Teams to the voice systems you use
Start with your current telephony, carrier and migration scope. Validate the Sentinel configuration and supported software release for your Direct Routing design.
Discuss a Teams ProjectMicrosoft-listed Sentinel Series
Carrier and PBX connectivity
Architecture validation
MICROSOFT TEAMS DIRECT ROUTING
What you can do with it
Connect Teams Phone to carriers, PBXs and existing voice systems through a Microsoft-certified Sentinel SBC while retaining routing, security and interoperability control.
CertifiedSentinel SBC family
TLS / SRTPprotected signaling and media
Hybridcarrier and PBX integration
CAPABILITIES
Capabilities that matter for your project
Interoperability
Normalize SIP, manipulate headers, route calls and anchor media between Teams, trunks, PBXs and analog gateways.
Phased migration
Retain selected PBXs and legacy endpoints while users and sites move to Teams in controlled stages.
DEPLOYMENT FIT
Best suited for
- Teams Phone carrier connectivity
- PBX coexistence
- Analog endpoint continuity
- Multi-site migrations
- Operator-managed Teams services
KEY SPECIFICATIONS
Important selection data
Core platformSentinel CS, Mini, 100 or 400
SecurityTLS, SRTP, topology hiding and certificate management
Legacy interfacesThrough Sentinel or Mediatrix gateway architecture
DOWNLOADS
Brochures and technical documents
Download the PDF files directly. Use the documentation portal for configuration guides, installation procedures and release-specific information.
Products 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 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.
SOLUTION BLUEPRINT
How Microsoft Teams Direct Routing changes the voice path.
The M5 layer sits between what must be preserved and the destination architecture, making security, translation and failure behavior explicit.
NO PUBLIC INTERNET REQUIRED
Private LAN / isolated IP network
The on-premises PBX, Mediatrix gateways and local endpoints can retain an internal call path. This local path does not become dependent on the public Internet simply because Teams is added.
REQUIRED FOR TEAMS & PUBLIC CALLING
Microsoft 365 and SIP carrier connection
Teams Phone, Direct Routing and calls to the public telephone network require working connectivity to the applicable Microsoft and carrier services. The diagram shows that external path separately.
PRIVATE CUSTOMER NETWORK
Existing PBX
Can coexist during a phased Teams migration.
Mediatrix gateway
Preserves approved analog phones, fax, modems and legacy trunks.
Teams & legacy users
Users communicate across one engineered dial plan during transition.
PRIVATE IP NETWORK / LANLocal SIP signaling + RTP media
INTERNALIndependent local pathLocal PBX, gateways and extensions can keep communicating even though the cloud route is shown separately.
CONTROLLED EDGE
DIRECT ROUTING
Certified Sentinel SBC
Translates Teams requirements into controlled SIP signaling, media and routing.
EXTERNAL SERVICE NETWORK
Microsoft Teams Phone
Hosts users and calling features in Microsoft 365.
SIP carrier
Provides numbers and public telephone access.
SIP over TLSSRTP mediaE.164 routingCoexistence
READING THE DIAGRAM
Follow one call from the cloud to the telephone network
- Cloud voice platform
- Hosts communications services such as Microsoft Teams Phone or CCaaS outside the customer site.
- 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.
Reference flow — carrier, platform, jurisdiction and field requirements determine the production design.
BEFORE / AFTER
Turn an uncontrolled migration into an engineered transition.
Use these checkpoints to evaluate a microsoft teams direct routing project before product selection or cutover.
The recommended design depends on the deployed carrier, PBX or UC platform, interfaces, call volume, failure modes and regulatory context.| Decision area | Uncontrolled approach | M5 architecture | Acceptance evidence |
|---|---|---|---|
| Interoperability | Assume systems will connect | Normalize signaling and media at a defined boundary | Documented end-to-end call tests |
| Security | Expose internal voice domains | Apply identity, topology and transport controls | Approved routes, certificates and logs |
| Continuity | Cut over every site together | Preserve required services and phase migration | Failover, rollback and exception tests |
| Operations | Treat go-live as the finish line | Assign monitoring, updates and escalation ownership | Runbook, backups and support entitlement |
FREQUENTLY ASKED
What to know before the next step.
Document every carrier, PBX or UC platform, endpoint class, site, interface, call flow, security boundary and failure requirement.
Yes. A phased architecture can preserve approved services while routes, sites and users move in controlled stages with rollback criteria.
Normal and exceptional calls, encryption, routing, media, failover, monitoring and operational ownership should all pass documented tests.
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.