Source note · SIP TLS handshake failures on trunks
For a Webex Calling certificate-based trunk, the Local Gateway certificate must be signed by a public CA, and its subject CN or one SAN must equal the FQDN (or the SRV name, when SRV is used) configured in Control Hub.
Checked 2026-09-25
- Vendor
- Cisco
- Product
- Webex Calling Local Gateway (IOS XE)
- Subsystem
- SBC certificate
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Configure Local Gateway on Cisco IOS XE for Webex Calling — Cisco Systems, Inc. (Webex Help Center) · tier 2 current vendor documentation · Certificate-based trunk requirements, certificate prerequisites and examples
Cite this note
APA
WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-lgw-cert-trunk-fqdn. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-lgw-cert-trunk-fqdn
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-lgw-cert-trunk-fqdn,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-lgw-cert-trunk-fqdn},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-lgw-cert-trunk-fqdn},
note = {Source note sip-tls-handshake-failures-lgw-cert-trunk-fqdn, checked 2026-09-25}
}