Source note · Enabling mixed mode and encrypted calling in Unified CM
In the intercluster SIP TLS example, each side's X.509 Subject Name is set to the Common Name of the peer cluster's certificate.
Checked 2026-09-30
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- SIP trunk security profile
- Deployment
- on-premises
- Region
- not restricted
- Release range
- as written (2018)
- Checked
- 2026-09-30
Sources
- Configure SIP TLS Trunk on the Communications Manager with a CA Signed Certificate — Cisco Systems · tier 2 current vendor documentation · Configure > SIP Trunk Security Profile
Cite this note
APA
WarmTransfer. (2026, September 30). Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-trunk-x509-peer-cn. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-trunk-x509-peer-cn
BibTeX
@misc{warmtransfer-claim-cucm-secure-calling-setup-trunk-x509-peer-cn,
title = {Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-trunk-x509-peer-cn},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-trunk-x509-peer-cn},
note = {Source note cucm-secure-calling-setup-trunk-x509-peer-cn, checked 2026-09-30}
}