Source note · Setting up Microsoft Teams Direct Routing
Microsoft forces TLS 1.2 on the Direct Routing SIP interface, and the SBC must support TLS 1.2 with one of four ECDHE-RSA cipher suites: AES256-GCM-SHA384, AES128-GCM-SHA256, AES256-SHA384 or AES128-SHA256.
Checked 2026-09-24
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone
- Subsystem
- direct-routing-tls
- 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 · Considerations, TLS1.2 bullet
Cite this note
APA
WarmTransfer. (2026, September 24). Setting up Microsoft Teams Direct Routing: source note teams-direct-routing-setup-tls12-cipher-suites. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-setup-tls12-cipher-suites
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-setup-tls12-cipher-suites,
title = {Setting up Microsoft Teams Direct Routing: source note teams-direct-routing-setup-tls12-cipher-suites},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-setup-tls12-cipher-suites},
note = {Source note teams-direct-routing-setup-tls12-cipher-suites, checked 2026-09-24}
}