A request for advice on changing the names of the CUCM sections such as the CM group, Hunt lists, partitions, CSS etc.
The naming convention on our CUCM cluster is really a mess courtesy of the original vendor who configured it.We have a core site and three remote sites and all have them have been configured differently, I kid you not.
There are two things I want to do first thing is to standardise my naming convention. Essentially I have to change everything on the CUCM to do this. The servers themselves are based on IP address so not changing them but everything else I will be standardising.I am not changing the name of the physical server either just the CUCM configuration naming scheme
I have loaded a backup copy into VMWARE to test this out and on certain sections such as CUCM group, regions partitions etc when the name is changed it requires a reset but there is no major issue and all seems to be ok. That's fair enough, but can I do this successfully to a live system (obviously during an outage window) or are there any gotchas with changing the names of everything that I should know about. if this will cause issues then I may leave as is
The second thing is that with the names changed I am wanting to move the line/device approach for the PTs and CSS but again would like to change the naming convention before adjusting this. I am sure all will work but I want to make sure that by changing the convention all will be ok.
The current PTs and CSS setup is yes you guessed it, a mess so want to put it in the Line/Device model to asisst with the growth of adding additional sites.
So any feedback/advise on change the naming convention of the configuration and moving to a Line/Device setup on a live system would be much appreciated