Source note · Microsoft teams direct routing
For a CUCM estate moving users to Teams, Direct Routing lets the organisation keep its carrier SIP trunks behind its existing CUBE, provided the CUBE platform and IOS XE release are on Microsoft's certified list and meet the TLS, certificate and SIP requirements above.
inferred · Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Migration
- Deployment
- multi-tenant, on-premises
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Status
- inferred
- Checked
- 2026-09-30
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · Section 'Why choose Direct Routing?' combined with ms-learn-direct-routing-certified-sbcs table 'Certified SBC vendors', Cisco rows
Cite this note
APA
WarmTransfer. (2026, September 30). Microsoft teams direct routing: source note microsoft-teams-direct-routing-keep-carrier-cube. WarmTransfer. https://warmtransfer.net/knowledge/claims/microsoft-teams-direct-routing-keep-carrier-cube
BibTeX
@misc{warmtransfer-claim-microsoft-teams-direct-routing-keep-carrier-cube,
title = {Microsoft teams direct routing: source note microsoft-teams-direct-routing-keep-carrier-cube},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/microsoft-teams-direct-routing-keep-carrier-cube},
note = {Source note microsoft-teams-direct-routing-keep-carrier-cube, checked 2026-09-30}
}