Source note · Setting up an Oracle SBC for Teams Direct Routing

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

Checked 2026-09-30

Vendor: Microsoft
Product: Microsoft Teams Phone Direct Routing
Subsystem: 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 · Connect the SBC to the tenant, Considerations, TLS1.2 bullet

Cite this note

APA

WarmTransfer. (2026, September 30). Setting up an Oracle SBC for Teams Direct Routing: source note oracle-sbc-teams-direct-routing-setup-tls12-ciphers. WarmTransfer. https://warmtransfer.net/knowledge/claims/oracle-sbc-teams-direct-routing-setup-tls12-ciphers

BibTeX

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

Read in context