Source note · Unified CM security hardening
A minimum TLS version change made on the publisher replicates to the other cluster nodes. IM and Presence must be configured separately, and all nodes must be restarted for the change to take effect.
Checked 2026-09-25
restart all the nodes in the clusters for the changes to take effect
- Vendor
- Cisco
- Product
- Unified Communications Manager
- Subsystem
- TLS
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 15SU2 and later
- Checked
- 2026-09-25
Sources
- Security Guide for Cisco Unified Communications Manager, Release 15 and SUs - TLS 1.3 Setup (From Release 15SU2 Onwards) — Cisco Systems · tier 2 current vendor documentation · TLS 1.3 Setup > Set Minimum TLS Version > notes
Cite this note
APA
WarmTransfer. (2026, September 25). Unified CM security hardening: source note cucm-security-hardening-tls-min-restart. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-security-hardening-tls-min-restart
BibTeX
@misc{warmtransfer-claim-cucm-security-hardening-tls-min-restart,
title = {Unified CM security hardening: source note cucm-security-hardening-tls-min-restart},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-security-hardening-tls-min-restart},
note = {Source note cucm-security-hardening-tls-min-restart, checked 2026-09-25}
}