Source note · SIP TLS handshake failures on trunks
Microsoft's Direct Routing planning guidance says the SBC certificate should carry the SBC FQDN in the CN or SAN, be signed by a CA in the Microsoft Trusted Root Program, and include the Server Authentication EKU.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- SBC certificate
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · Public trusted certificate for the SBC, bullet list
Cite this note
APA
WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-cert-cn-san-eku. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-cert-cn-san-eku
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-dr-cert-cn-san-eku,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-cert-cn-san-eku},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-cert-cn-san-eku},
note = {Source note sip-tls-handshake-failures-dr-cert-cn-san-eku, checked 2026-09-25}
}