- #Cisco uccx 11.5 nfr update
- #Cisco uccx 11.5 nfr upgrade
- #Cisco uccx 11.5 nfr software
- #Cisco uccx 11.5 nfr download
> was a total unmitigated Cisco disaster. > Secondary Down, and TAC was unable to resolve after hours and hours. > Our entire contact center, which is HA, was entirely down. > the issue for a few minutes, but then fast busy. > The real shocker was 4 hours later when the system stopped accepting calls > still not mentioned in the release notes. > hit a finesse bug which required the ECDSA COP file.
#Cisco uccx 11.5 nfr upgrade
> We recently attempted to upgrade UCCX 10.5 - > 11.5. If so, it could be the browsers sinking the server with a ton of HTTP To find out more visit the Mimecast website. Specializing in Security, archiving and compliance. Providing a safer and more useful place for your human generated data.
#Cisco uccx 11.5 nfr software
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. It is intended solely for use by the recipient and others authorized to receive it. The information contained in this communication from the sender is confidential. I believe at the time, there was not a compatible version of UCCX to go to 11.5 with, but the 11.0-75 was listed as a supported matrix.įrom: cisco-voip On Behalf Of Ayoub,Gregory We didn't have those failures, though we took call manager, IM&P, and unity connection to 11.5 and UCCX to 11.0.1 several weeks ago. If I had to guess, that seems like more of a licensing failure, because TAC even tried replacing our license. But we are at a loss what could be causing this problem. We rolled back and are on 10.5 working fine. And then rolling forward again to 11.5 the system worked great again - but only for 4 hours. It was a total unmitigated Cisco disaster. Primary down, Secondary Down, and TAC was unable to resolve after hours and hours. Our entire contact center, which is HA, was entirely down. Failing over to the secondary would fix the issue for a few minutes, but then fast busy. The real shocker was 4 hours later when the system stopped accepting calls and just handed out fast busys. While minor, it's still not mentioned in the release notes. The upgrade went fairly smooth, and we hit a finesse bug which required the ECDSA COP file. The deployment was HA, and we didn't see much risk. If you have a couple hundred phones, it shouldn't be an issue at all.We recently attempted to upgrade UCCX 10.5 - > 11.5.
#Cisco uccx 11.5 nfr update
Once you have upgraded to version 8.5(2), you can upgrade your IP Phone to version 8.5(2)SR1 or later.ĭouble check all phones are at least 8.5(2), if not, upgrade them then proceed with the install.ĭepending on how big your environment is, you may want to look at the firmware section and pre-update all of your devices to that firmware, this way after you do the upgrade, all the phones aren't hitting CUCM at one time trying to pull down the update which may break the TFTP server or your network.
#Cisco uccx 11.5 nfr download
So if you have 78xx phones, make sure you download the fixed firmware and update them post-install so you don't run into this problem.Īll SCCP and SIP firmware upgrades from firmware release versions earlier than 8.3(3) to version 8.5(2)SR1 or greater, you must first upgrade your firmware to version 8.5(2). The 78xx phone firmware included in 11.5(1)SU7 has been deferred from due to the following: CSCvr54598: Intermittently not ring after upgrade to 12.6 Customers upgrading to 11.5(1)SU7 will need to apply the fixed 78xx firmware following the upgrade in order to avoid hitting this issue. They're pretty scary the first time, but straightforward enough that it shouldn't be a problem. Just make sure you read through the release notes of the version, they basically give you a "hint" as to what to look out for.
0 kommentar(er)
