Source note · SIP TLS handshake failures on trunks
For a CUCM-to-CUBE SIP TLS trunk, the X.509 subject name in the CUCM SIP trunk security profile must match the peer certificate's subject name, and the trunk destination port changes from 5060 to 5061.
Checked 2026-09-25
- Vendor
- Cisco
- Product
- Cisco Unified CM
- Subsystem
- server identity validation
- Deployment
- on-premises
- Region
- not restricted
- Release range
- as published 2020-04-21
- Checked
- 2026-09-25
Sources
- Configure SIP TLS Between CUCM-CUBE/CUBE-SBC With CA Signed Certificates — Cisco · tier 2 current vendor documentation · Configure section, CUCM SIP trunk security profile and SIP trunk destination steps
Cite this note
APA
WarmTransfer. (2026, September 25). SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-cucm-x509-subject. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-cucm-x509-subject
BibTeX
@misc{warmtransfer-claim-sip-tls-handshake-failures-cucm-x509-subject,
title = {SIP TLS handshake failures on trunks: source note sip-tls-handshake-failures-cucm-x509-subject},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-tls-handshake-failures-cucm-x509-subject},
note = {Source note sip-tls-handshake-failures-cucm-x509-subject, checked 2026-09-25}
}