Source note · TLS versions and cipher support across UC platforms
An SBC trunk to Teams Direct Routing that is restricted to TLS 1.3 only would risk handshake failure, because Microsoft documents only TLS 1.2 cipher suites for that interface; such trunks should allow TLS 1.2.
inferred · Checked 2026-10-02
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- SIP interface interop
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- Connect your Session Border Controller (SBC) to Direct Routing — Microsoft · tier 2 current vendor documentation · Connect the SBC to the tenant; Considerations, TLS bullet
Cite this note
APA
WarmTransfer. (2026, October 2). TLS versions and cipher support across UC platforms: source note tls-version-support-uc-sbc-tls13-only-breaks-teams. WarmTransfer. https://warmtransfer.net/knowledge/claims/tls-version-support-uc-sbc-tls13-only-breaks-teams
BibTeX
@misc{warmtransfer-claim-tls-version-support-uc-sbc-tls13-only-breaks-teams,
title = {TLS versions and cipher support across UC platforms: source note tls-version-support-uc-sbc-tls13-only-breaks-teams},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/tls-version-support-uc-sbc-tls13-only-breaks-teams},
note = {Source note tls-version-support-uc-sbc-tls13-only-breaks-teams, checked 2026-10-02}
}