Source note · SIP TLS handshake failures on trunks
The Azure Communication Services direct routing troubleshooting article tells an SBC that does not trust the SIP proxy certificate to install both the Baltimore CyberTrust root and DigiCert Global Root G2.
disputed · Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Azure Communication Services direct routing
- Subsystem
- trust store
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- article updated 2026-09-23
- Status
- disputed
- Checked
- 2026-09-25
Sources
- Troubleshoot Azure Communication Services direct routing TLS certificate and SIP OPTIONS 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-acs-baltimore-and-g2. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-acs-baltimore-and-g2
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-acs-baltimore-and-g2,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-acs-baltimore-and-g2},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-acs-baltimore-and-g2},
note = {Source note sip-tls-handshake-failures-acs-baltimore-and-g2, checked 2026-09-25}
}