UC Cluster Upgrade to 10 including UCCX (Upgrade Order?)
We are going to upgrade a customer to CSR10. Currently customer is running CUCM 8.6 and UCCX 8.5. Also Unity Connection, InformaCast, Xmedius, Calabrio, etc.
Checking the UCCX Compatibility Matrix I can see that UCCX 10.0 is compatible with CUCM 8.6. So I was thinking to first upgrade UCCX to version 10.. Calabrio to version 10 and then wait a couple days and upgrade the CUCM Cluster. Is that the best way? First I was thinking in doing the CUCM Cluster first but no sure how UCCX 8.5 is going to handle CUCM 10 for a couple of days.
Regarding the UCCX compatibility with CUCM, I see that 8.6.2a SU4 is compatible with UCCX 10.0 base and 10.0.1 SU1 version.
If you are on 8.6.2a SU4 version on CUCM, then upgrade on UCCX can be done first. Basically the thumb rule is, ensure that first CUCM is on the compatible version with the UCCX version where we are moving to.
Just to follow up. As per the UCCX compatibility document. UCCX 10 was compatible with CUCM 8.6.2SU4. Customer last week did a maintenance window to upgrade their CUCM Cluster to SU4. Now I'm reading the UCCX compatibility guide again and it is no longer there the compatibility with CUCM 8.6.2SU4. Now it only shows up 9.x and 10.x. That was changed on May 29 2014.
So now we are not sure if we can proceed with the UCCX upgrade to 10.0(1)SU1 and CUCM 8.6.2(SU4). As the upgrade for the CUCM cluster to 10.x is schedule in a couple of weeks.
can you check internally in Cisco why the 8.6.2aSU4 release was deleted from compatibility document for UCCx please? It's very important for us if it is because of some BUG or just because of error when adding UCCx 10.5 into the document.
We went ahead and upgraded the UCCX cluster to 10.0(1) and leave CUCM Cluster running 8.6.2a(SU4) for couple of days. Everything was working fine with the existing configuration. However we went to add an application into the UCCX and UCCX was unable to access CUCM configuration when creating a trigger (DP, Regions, Partitions, Locations, etc). It came back with an AXL API Denied Access message. Maybe that's why they removed the compatibility.
We did upgrade the CUCM Cluster to version 10.0(1) as well and now UCCX is able to create triggers without any problem.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...