Source note · Setting up CUBE as a Microsoft Teams Direct Routing SBC
Because Microsoft accepts only four ECDHE-RSA suites and Cisco's CUBE example tls-cipher names are AES128_GCM_SHA256 and AES256_GCM_SHA384, the administrator must confirm from the TLS connection detail that the negotiated suite is one Microsoft accepts.
inferred · Checked 2026-09-30
- Vendor
- Cisco
- Product
- Cisco Unified Border Element
- Subsystem
- SIP TLS
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Status
- inferred
- Checked
- 2026-09-30
Sources
- Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - SIP TLS Support — Cisco · tier 2 current vendor documentation · TLS cipher configuration example, read against ms-learn-dr-connect-sbc Considerations TLS bullet
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-cube-cipher-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cube-cipher-match
BibTeX
@misc{warmtransfer-claim-cube-teams-direct-routing-setup-cube-cipher-match,
title = {Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-cube-cipher-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cube-cipher-match},
note = {Source note cube-teams-direct-routing-setup-cube-cipher-match, checked 2026-09-30}
}