Source note · SIP TLS handshake failures on trunks
For Webex Calling mutual TLS, the peer certificate must be signed by a CA on Webex's approved list, be within its validity period, chain through unexpired and unrevoked roots and intermediates, and carry the Control Hub FQDN in its CN or SAN.
Checked 2026-09-25
- Vendor
- Cisco
- Product
- Webex Calling
- Subsystem
- mutual TLS
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Security requirements for Webex Calling — Cisco Systems, Inc. (help.webex.com) · tier 2 current vendor documentation · Mutual TLS certificate requirements
Cite this note
APA
WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-wxc-mtls-cert-rules. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-wxc-mtls-cert-rules
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-wxc-mtls-cert-rules,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-wxc-mtls-cert-rules},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-wxc-mtls-cert-rules},
note = {Source note sip-tls-handshake-failures-wxc-mtls-cert-rules, checked 2026-09-25}
}