Source note · Setting up an Oracle SBC for Teams Direct Routing
Because Microsoft forces TLS 1.2 on the Direct Routing SIP interface and Oracle's tls-profile defaults to tlsv13, the Teams-facing tls-profile probably needs tls-version set to tlsv12 or compatibility for the TLS session to establish.
inferred · Checked 2026-09-30
- Vendor
- Oracle
- Product
- Oracle Communications Session Border Controller
- Subsystem
- security tls-profile
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 9.3.0
- Status
- inferred
- Checked
- 2026-09-30
Sources
- ACLI Reference Guide: tls-profile — Oracle · tier 2 current vendor documentation · tls-version parameter, read together with ms-learn-dr-connect-sbc 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-tls-version-infer. WarmTransfer. https://warmtransfer.net/knowledge/claims/oracle-sbc-teams-direct-routing-setup-tls-version-infer
BibTeX
@misc{warmtransfer-claim-oracle-sbc-teams-direct-routing-setup-tls-version-infer,
title = {Setting up an Oracle SBC for Teams Direct Routing: source note oracle-sbc-teams-direct-routing-setup-tls-version-infer},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/oracle-sbc-teams-direct-routing-setup-tls-version-infer},
note = {Source note oracle-sbc-teams-direct-routing-setup-tls-version-infer, checked 2026-09-30}
}