Source note · Setting up CUBE as a Microsoft Teams Direct Routing SBC
Microsoft recommends generating the SBC certificate from a CSR on the SBC; the certificate should carry the SBC FQDN as CN or SAN, be signed by a CA in the Microsoft Trusted Root Program and include the Server Authentication EKU, and RFC 2818 wildcards are supported.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone
- Subsystem
- Direct Routing certificates
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · Public trusted certificate for the SBC
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-cert-requirements. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cert-requirements
BibTeX
@misc{warmtransfer-claim-cube-teams-direct-routing-setup-cert-requirements,
title = {Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-cert-requirements},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-cert-requirements},
note = {Source note cube-teams-direct-routing-setup-cert-requirements, checked 2026-09-30}
}