After successful upgrade, the Preview Outbound seat count will not
be carried forward in case of an upgrade from Unified CCX 7.0(2)ES03 to Unified
CCX 9.0(1). By default, the Preview Outbound seat count will be initialized
with the maximum supported value for the given hardware type. You need to
manually modify the seat count in the System Parameters Configuration page of
the Unified CCX Administration according to the usage.
Table 1 Maximum Preview Outbound seat count
Maximum Preview Outbound Seat Count
After successful upgrade, HTTP trigger will work on port 9080 in
Unified CCX 9.0(1). Also, applications using the HTTP port 8080 should be
changed to 9080.
To change this, choose System > Applications on the Unified CCX 9.0(1) Administration interface, and then change the port in the applications using them.
Manually add the e-mail templates (configured on Cisco Desktop
Administrator) on the Unified CCX 9.0(1) after the upgrade since these are not
If you have set the default password in Cisco Desktop
Administrator to blank in Unified CCX 7.0(2)ES03, the default password changes to
"crsadmin" after your system is upgraded to Unified CCX 9.0(1).
If reason code '0' has been defined in Unified CCX 7.0(2)ES03, it
automatically changes to 1001 when upgraded to Unified CCX 9.0(1).
To support installation of Express Gateway in GEL-Express
deployment (ICM Parent with Unified CCX child) on your upgraded Unified CCX
9.0(1) system, modify the existing RmCm port 42027 to the new RmCm port 12028.
Build second node in HA setup
To build the second node in an HA setup after the upgrade is
complete on the first node, do the following:
Add the second node information to the first node using the
Unified CCX 9.0(1) Administration web interface before you install
the second node.
If you are upgrading Unified CCX (old version) setup having
multiple device pools (for Call Control Groups) to Standalone Unified CCX
9.0(1), delete all device pool rows, choose a single device pool from device
pool drop down list and click update to proceed.
If you are upgrading a two-node Unified CCX (old version)
setup having multiple device pools (for Call Control Groups) to Unified CCX
9.0(1), performing initial setup configuration on the second node after the
upgrade would merge all multiple device pools to a single default device pool.
However, you can manually assign a different device pool to the Call Control
Group if the default device pool is not the intended one.
Run configuration tool
After you complete upgrading the second node, you must run the
Unified CCX Desktop Client Configuration Tool to create correctly-configured MSI files for the client applications. The Automated Update feature uses these MSI files to update the client desktops the next time users launch a Cisco Agent Desktop application.
Log in to the Unified CCX Administration web interface.