Source note · SIP TLS handshake failures on trunks
Teams Direct Routing treats a self-signed SBC certificate as invalid; the certificate must come from a trusted CA and contain at least one FQDN that belongs to a Microsoft 365 tenant.
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
- SBC connectivity issues — Microsoft · tier 2 current vendor documentation · TLS connection issues > SBC certificate is self-signed or not from a trusted CA
Cite this note
APA
WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-self-signed-invalid. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-self-signed-invalid
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-dr-self-signed-invalid,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-self-signed-invalid},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-self-signed-invalid},
note = {Source note sip-tls-handshake-failures-dr-self-signed-invalid, checked 2026-09-25}
}