Guys - I really hope I'm not being really thick here (but its possible!) as I have done this lots of time in the past, but has anyone had issues upgrading to 18.104.22.168900-4 using the joined UCSInstall_UCOS_22.214.171.124900-4.sgn.iso file? I am upgrading from CUCM 126.96.36.19900 and CUCXN 188.8.131.520 (as this file supports both upgrades) but the upgrade process cant see the file from the sftp / ftp server. I have verified checksum, the sftp / tftp credentials are fine and debug doesnt report any errors, I can also see other (locale) files available to install from both CUCM and CUCXN but just cant see this file?
We have seen something like this before. Basically, in our case, we had to put the 184.108.40.2069000-4 file in its own directory on the SFTP server (no other files in the directory). Once we did this, then we could see the file. We haven't seen this issue every time we have done the upgrade. But we have seen it and the fix was a new directory on the SFTP server with just the 7.1(3b)SU2 file in said directory.
Bill is 100% correct here. We've seen this a few times and I actually encountered this just last week during a CUC installation for a customer. When I tried to upgrade to 220.127.116.11900-4, the upgrade manager could not see the file even though it was in the same folder as other upgrade files that were seen. I moved the file to it's own folder location and specified that as the file path. Example, /home/upgrades/cuc/713bsu2/ ... no issues from there.
Guys - I cant think you enough, you have saved me another day of looking into the UC upgrade abyss!
Also found that the CUCM and CXN parts are named slightly differently in the downloads page:
CXN is called UCS_Install_UCOS_18.104.22.168900-4.sgn.iso_part1of2
CUCM is called UCSInstall_UCOS_22.214.171.124900-4.sgn.iso_part1of2 (no underscore after UCS)
If (like me) you think you can just cut and paste the merge command into notepad by ammending the end of the filenames, if using the CXN filenames you also have to remove the underscore after UCS for the merged file or else neither CXN or CUCM will see the files.
btw the CUC release notes do refer to the output file as having no underscore after UCS, so I guess as alway its all in the detail.
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...