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