Source note · Enabling mixed mode and encrypted calling in Unified CM
ITLRecovery was chosen as the CTL signer because it does not change for secondary reasons such as a hostname change; before 12.0(1) regenerating the CallManager certificate could lock endpoints out.
Checked 2026-09-30
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- CTL
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 12.0(1) and later
- Checked
- 2026-09-30
Sources
- Security Guide for Cisco Unified Communications Manager, Release 12.5(1)SU2 - Cisco CTL Client Setup — Cisco Systems · tier 2 current vendor documentation · Cisco CTL Client Setup > tokenless CTL SAST roles
Cite this note
APA
WarmTransfer. (2026, September 30). Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-itlrecovery-stable. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-itlrecovery-stable
BibTeX
@misc{warmtransfer-claim-cucm-secure-calling-setup-itlrecovery-stable,
title = {Enabling mixed mode and encrypted calling in Unified CM: source note cucm-secure-calling-setup-itlrecovery-stable},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-secure-calling-setup-itlrecovery-stable},
note = {Source note cucm-secure-calling-setup-itlrecovery-stable, checked 2026-09-30}
}