I’m glad I did, because apparently I hit another bug. Originally, I thought the issue is a result of the CA inserting a So I have manually added the After multiple retries, I gave up and opened a TAC case. I would get the following error: “CSR SAN and Certificate SAN does not match”. Brand-new deployment of CUCM/CUC/CUPS version 10.5.1 and I’m unable to upload a freshly-generated SAN certificate from Starfield. I’ve been lucky to hit another bug today. Be sure to check patch installation instructions and you may also want to review the CSCur00930 (CUCM) and CSCur05328 (CUC) on the Bug Tracker for more information. The update does not require system reboot, but Cisco advises to make a backup copy just in case. But for now, affected customers should download and install available on CCO under Products > Unified Communications Call Control Cisco Unified Communications Manager (CallManager) > Cisco Unified Communications Manager Version x.x > Unified Communications Manager / CallManager / Cisco Unity Connection Utilities-COP-Files. All future software updates for CallManager/Unity Connection versions that have not reached E-O-M will be released with the patch included. On October 1st Cisco has released bash environment patch for CUCM/CUC versions 8, 9 and 10 to protect these systems from Shellshock bug. Cisco is no exception here, and that’s a good thing. With yet another vulnerability that has become public in the recent week, vendors are scrambling to issue security patches for their systems. I have updated the post to reflect this information. Update: The patch is also applicable to Cisco Unity Connection versions 8.5.1 and up.
0 kommentar(er)
