Source note · CUCM to Teams Phone migration
Microsoft forces TLS 1.2 on the Direct Routing SIP interface and the SBC must be able to connect with one of four ECDHE-RSA cipher suites using AES 128 or 256 in GCM or CBC mode.
Checked 2026-09-21
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- direct-routing-security
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-21
- Checked
- 2026-09-21
Sources
- Connect your Session Border Controller (SBC) to Direct Routing — Microsoft · tier 2 current vendor documentation · Use PowerShell > Connect the SBC to the tenant > Considerations, TLS bullet
Cite this note
APA
WarmTransfer. (2026, September 21). CUCM to Teams Phone migration: source note cucm-to-teams-phone-sbc-tls12-ciphers. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-sbc-tls12-ciphers
BibTeX
@misc{warmtransfer-claim-cucm-to-teams-phone-sbc-tls12-ciphers,
title = {CUCM to Teams Phone migration: source note cucm-to-teams-phone-sbc-tls12-ciphers},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-sbc-tls12-ciphers},
note = {Source note cucm-to-teams-phone-sbc-tls12-ciphers, checked 2026-09-21}
}