Endpoints that already had a bad ITL before regeneration will not re-register afterwards. Cisco's practice is to delete the ITL/CTL on those phones after the process, once the other devices have registered.
Checked 2026-10-01
- Vendor
- Cisco
- Product
- Unified Communications Manager
- Subsystem
- ITL
- Deployment
- on-premises
- Region
- not restricted
- Release range
- current as of 2026-10-01
- Checked
- 2026-10-01
Sources
- Regenerate Certificates In Unified Communications Manager — Cisco Systems · tier 2 current vendor documentation · ITL/CTL deletion guidance section
Cite this note
APA
WarmTransfer. (2026, October 1). Troubleshooting phone trust and ITL failures in Unified CM: source note cucm-itl-trust-troubleshooting-bad-itl-delete-after. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-itl-trust-troubleshooting-bad-itl-delete-after
BibTeX
@misc{warmtransfer-claim-cucm-itl-trust-troubleshooting-bad-itl-delete-after,
title = {Troubleshooting phone trust and ITL failures in Unified CM: source note cucm-itl-trust-troubleshooting-bad-itl-delete-after},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-itl-trust-troubleshooting-bad-itl-delete-after},
note = {Source note cucm-itl-trust-troubleshooting-bad-itl-delete-after, checked 2026-10-01}
}