I have a call manager 6.1 and i will upgrade it to 8.5.
the issue is that i have a ctl installed in my version 6 and secured ip phone and i want to work with the same CTL in version 8 without upgrading it. i don't want to have go through each phone and upgrade the CTL. can upgrade my CUCM to 8 without modifying the CTL and what's the procedure.
can upgrade my CUCM to 8 without modifying the CTL and what's the procedure.
As long as you do not renew or regenerate any of the certificates included in the CTL (CUCM, TFTP, CAPF, etc) you can upgrade the cluster without rebuilding the CTL. Also, as long as a new version of the CTL is signed by at least one of the tokens that was included in the version already downloaded, the phone will automatically download a newer CTL version.
The CTL Client on your workstation would have to be upgraded the next time you need to modify the CTL though.
Lastly, be sure that you understand the new TVS and ITL mechanisms in CUCM 8.0+. Both of them interact with CTL if you have a mixed mode cluster.
when I upgrade the cluster, and i take a phone directly from version six to my new version 8 it doesn't want to register and is rejected (security issue) , when I remove the security profile from the phone then the phone moved from the version 6 to version 8 works.
the issue is that I have 4000 ip phone to move from the version 6 to version 8 and need the security to be set.
Moving a phone from one cluster to another, as opposed to upgrading the same 6.x cluster to 8.0 is an entirely different matter.
If you are changing clusters and both are in mixed mode than the new CTL must be signed by one of the tokens that was included in the 6.x CTL; otherwise, the phone will not accept the new CTL nor the ITL and by extension it's TFTP config file.
If you're migrating to UCS the way this should go is:
Upgrade the MCS servers to 8.0(2) or newer so that it supports UCS.
Install the exact same upgraded version on UCS.
Perform a DRS backup of the MCS cluster and restore it to the UCS install one node at a time.
Upgrade the UCS cluster to 8.6 or beyond (which MCS likely didn't support).
If you do a DRS backup and restore the certificates and the CTL file should come forward with it. I'm confused why you're talking about building a new 8.x cluster and moving toward it.
If you're deadset on doing a new cluster then you would want to reuse the same security tokens to sign your 8.x CTL file. Since those tokens are already trusted in the 6.x CTL the phone will accept the new CTL.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...