Source note · Enabling mixed mode and encrypted calling in Unified CM
After changing to non-secure mode, the TFTP and Cisco CallManager services must be restarted on all nodes that run them and all IP phones restarted to download the updated CTL file.
Checked 2026-09-30
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- security modes
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 10.x and later
- Checked
- 2026-09-30
Sources
- CUCM Cluster Changed from Mixed Mode to Non-Secure Mode Configuration Example — Cisco Systems · tier 2 current vendor documentation · Configure > after the change
Cite this note
APA
WarmTransfer. (2026, September 30). Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-nonsecure-restart. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-nonsecure-restart
BibTeX
@misc{warmtransfer-claim-cucm-secure-calling-setup-nonsecure-restart,
title = {Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-nonsecure-restart},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-nonsecure-restart},
note = {Source note cucm-secure-calling-setup-nonsecure-restart, checked 2026-09-30}
}