Source note · SIP TLS handshake failures on trunks
Microsoft's Teams Direct Routing troubleshooting article says an SBC that does not trust the SIP proxy certificate should install the Baltimore CyberTrust root.
disputed · Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- trust store
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- article updated 2026-06-30
- Status
- disputed
- Checked
- 2026-09-25
Sources
- SBC connectivity issues — Microsoft · tier 2 current vendor documentation · TLS connection issues > SBC doesn't trust SIP proxy certificate
Cite this note
APA
WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-baltimore-root-advice. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-baltimore-root-advice
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-dr-baltimore-root-advice,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-dr-baltimore-root-advice},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-dr-baltimore-root-advice},
note = {Source note sip-tls-handshake-failures-dr-baltimore-root-advice, checked 2026-09-25}
}