Source note · Avaya Aura to Teams Phone
Microsoft forces TLS 1.2 on the Direct Routing SIP interface and lists the ECDHE-RSA AES-GCM and AES-CBC cipher suites the SBC must support.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Direct Routing SBC pairing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Connect your Session Border Controller (SBC) to Direct Routing — Microsoft · tier 2 current vendor documentation · section 'Connect the SBC to the tenant', Considerations TLS bullet
Cite this note
APA
WarmTransfer. (2026, September 30). Avaya Aura to Teams Phone: source note avaya-aura-to-teams-phone-sbc-tls12. WarmTransfer. https://warmtransfer.net/knowledge/claims/avaya-aura-to-teams-phone-sbc-tls12
BibTeX
@misc{warmtransfer-claim-avaya-aura-to-teams-phone-sbc-tls12,
title = {Avaya Aura to Teams Phone: source note avaya-aura-to-teams-phone-sbc-tls12},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/avaya-aura-to-teams-phone-sbc-tls12},
note = {Source note avaya-aura-to-teams-phone-sbc-tls12, checked 2026-09-30}
}