Source note · Setting up CUBE as a Microsoft Teams Direct Routing SBC

Microsoft forces TLS 1.2 on the Direct Routing SIP interface and requires the SBC to connect with one of four ECDHE-RSA cipher suites: AES256-GCM-SHA384, AES128-GCM-SHA256, AES256-SHA384 or AES128-SHA256.

Checked 2026-09-30

Vendor: Microsoft
Product: Microsoft Teams Phone
Subsystem: Direct Routing SIP/TLS
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 · Considerations list, TLS1.2 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-tls12-ciphers. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-tls12-ciphers

BibTeX

@misc{warmtransfer-claim-cube-teams-direct-routing-setup-tls12-ciphers,
  title  = {Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-tls12-ciphers},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-tls12-ciphers},
  note   = {Source note cube-teams-direct-routing-setup-tls12-ciphers, checked 2026-09-30}
}

Read in context