Source note · One SBC serving several calling platforms
For the Teams SBC hosting scenario, the carrier requests a certificate with CN and/or SAN of *.base_domain (for example *.sbc1.adatum.biz) to authenticate connections to multiple tenants from one SBC.
Checked 2026-10-14
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Direct Routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Checked
- 2026-10-14
Sources
- Configure a Session Border Controller for multiple tenants — Microsoft · tier 2 current vendor documentation · Register a base domain and subdomains - Overview
Cite this note
APA
WarmTransfer. (2026, October 14). One SBC serving several calling platforms: source note multi-platform-sbc-design-teams-hosting-wildcard-cert. WarmTransfer. https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-teams-hosting-wildcard-cert
BibTeX
@misc{warmtransfer-claim-multi-platform-sbc-design-teams-hosting-wildcard-cert,
title = {One SBC serving several calling platforms: source note multi-platform-sbc-design-teams-hosting-wildcard-cert},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-teams-hosting-wildcard-cert},
note = {Source note multi-platform-sbc-design-teams-hosting-wildcard-cert, checked 2026-10-14}
}