Microsoft forces TLS 1.2 on the Direct Routing SIP interface, and the SBC must connect using one of four listed ECDHE-RSA AES-GCM or AES-CBC cipher suites.
Checked 2026-09-24
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- SBC pairing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Checked
- 2026-09-24
Sources
- Connect your Session Border Controller (SBC) to Direct Routing — Microsoft · tier 2 current vendor documentation · Connect the SBC to the tenant, Considerations
Cite this note
APA
WarmTransfer. (2026, September 24). Building a hybrid Unified CM and Teams Phone environment for a phased migration: source note cucm-teams-hybrid-build-sbc-tls12. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-teams-hybrid-build-sbc-tls12
BibTeX
@misc{warmtransfer-claim-cucm-teams-hybrid-build-sbc-tls12,
title = {Building a hybrid Unified CM and Teams Phone environment for a phased migration: source note cucm-teams-hybrid-build-sbc-tls12},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-teams-hybrid-build-sbc-tls12},
note = {Source note cucm-teams-hybrid-build-sbc-tls12, checked 2026-09-24}
}