For Teams Direct Routing a wildcard such as *.contoso.com matches sbc1.contoso.com but not customer10.sbc1.contoso.com; multiple subdomain levels under one wildcard are not allowed.
Checked 2026-10-02
- Vendor
- Microsoft
- Product
- Teams Direct Routing
- Subsystem
- SBC certificate
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- SBC connectivity issues — Microsoft · tier 2 current vendor documentation · Issues related to SIP OPTIONS: 'The FQDN doesn't match the contents of CN or SAN in the provided certificate'
Cite this note
APA
WarmTransfer. (2026, October 2). SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-teams-dr-wildcard-one-level. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-wildcard-one-level
BibTeX
@misc{warmtransfer-claim-sip-trunk-authentication-models-teams-dr-wildcard-one-level,
title = {SIP trunk authentication: registration and static IP and mutual TLS: source note sip-trunk-authentication-models-teams-dr-wildcard-one-level},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-authentication-models-teams-dr-wildcard-one-level},
note = {Source note sip-trunk-authentication-models-teams-dr-wildcard-one-level, checked 2026-10-02}
}