05-23-2024 12:20 PM
I need some help determining the process and impact of changing my Call Manager names under System > Server.
For reference my cluster is version 14. All nodes within the cluster were installed with a host name and the domain name is configured. Additionally, all of the hostnames are in DNS and resolvable forward and reverse.
It appears the only change necessary is to update the Call Manager names under System > Server from IP Address to FQDN.
When I make this change what is the impact? My Call Manager certificate is self-signed. Will it be regenerated by actioning this change? Is there any danger to the ITL files? Should I enable pre8.0?
I think I found the documentation for this change but the wording is a bit muddy. Any thoughts?
Solved! Go to Solution.
05-23-2024 12:45 PM
Changing the Call Manager names from IP Address to FQDN under System > Server in a Cisco Unified Communications Manager (CUCM) cluster version 14 should have minimal impact if your DNS setup is correct. The self-signed certificate should not be affected by this change, as it is tied to the server's hostname rather than its IP address.
There shouldn't be any danger to the ITL (Initial Trust List) files, as they are associated with devices rather than server names. Enabling pre8.0 compatibility mode might be necessary if you have older devices in your network that do not support FQDN for call manager names.
Ensure that after making this change, you thoroughly test your system to confirm that all endpoints can still register and communicate properly. If your documentation feels muddy, reaching out to Cisco support or consulting with a CUCM expert could provide clarity tailored to your specific setup.
05-23-2024 12:37 PM
For reference, my cluster is also in mixed-mode.
05-23-2024 12:45 PM
Changing the Call Manager names from IP Address to FQDN under System > Server in a Cisco Unified Communications Manager (CUCM) cluster version 14 should have minimal impact if your DNS setup is correct. The self-signed certificate should not be affected by this change, as it is tied to the server's hostname rather than its IP address.
There shouldn't be any danger to the ITL (Initial Trust List) files, as they are associated with devices rather than server names. Enabling pre8.0 compatibility mode might be necessary if you have older devices in your network that do not support FQDN for call manager names.
Ensure that after making this change, you thoroughly test your system to confirm that all endpoints can still register and communicate properly. If your documentation feels muddy, reaching out to Cisco support or consulting with a CUCM expert could provide clarity tailored to your specific setup.
05-23-2024 01:01 PM
Thats a good point that the certificates are based upon the hostname vs the IP address under System Server. Thanks for the help.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide