Cisco Finesse Release 11.0(1) ES07

Transcription

1 Cisco Finesse Release 11.0(1) ES07

2 Contents Version 11.0(1) ES Valid Upgrade Paths...3 Installing Finesse Release 11.0(1) ES Installation...3 Rollback...5 Resolved Caveats/Features in this Engineering Special...5 Bug Search Tool...7 Appendix...8

3 Version 11.0(1) ES07 File Name finesse-cce.1101.es cop.sgn finesse-cce.1101.es.rollback.cop.sgn MD5 Checksum b1fd8577abf bd1320cfadb98d ddf7da52a9fcf648f67b135047fdfbc7 Valid Upgrade Paths Cisco Finesse Release 11.0(1) ES07 is delivered as a Cisco Option Package (COP) file. The supported upgrade paths for 11.0(1)-ES7 are: 11.0(1) FCS or 11.0(1)-ES6. In case of any other ES installed, it needs to be upgraded to ES6, or rolled back to 11.0 FCS. Also, note that 11.0(1) ES07 can be applied irrespective of whether the language COP is installed or not. Installing Finesse Release 11.0(1) ES07 You must perform the following procedure first on the primary Finesse node and then on the secondary Finesse node. IMPORTANT: 1. Cisco is withdrawing support for Context Service integration in 11.0(1) version (but, will be available from 11.5(1) version). Therefore, as part of this ES installation, the Context Service integration features will be disabled. Please note that it is an irreversible change - rolling back will NOT restore Context Service integration support. In case, you have registered with Context Service, please de-register before proceeding with ES7 installation. 2. You must use the CLI to perform this upgrade. Do not use the Cisco Unified Operating System Administration page to perform this upgrade as the installation may hang. Installing this ES or performing a rollback stops and restarts certain Finesse services. To avoid interruption, perform the installation or rollback during a maintenance window. Installation 1. Download finesse-cce.1101.es cop.sgn to an SFTP server that can be accessed by the Finesse system. 2. Use SSH to log in to your Finesse system with the platform administration Account. 3. Access the CLI and run the following command: utils system upgrade initiate 4. Follow the instructions that appear on your screen. When prompted, provide the location and credentials for the remote file system (SFTP server). Note: The COP file performs a check to ensure that Cisco Finesse Release 11.0(1) is installed. If this release is not found on your system, an error is displayed and the installation does not proceed. 5. When presented with a list of available upgrade options, select finessecce.1101.es cop.sgn 6. After installation is complete, restart the system using the command: utils system restart

4 7. To verify that Finesse is now running the correct release, access the CLI using the Administrator credentials and enter the following command: show version active Make sure that finesse-cce.1101.es cop is listed as an Optional package. Otherwise, please contact Cisco TAC. 7. Check that the installation is successful by signing in to Finesse ( or hostname of Finesse server/desktop). You will have to clear the browser cache to avoid stale Context Service gadgets showing up.

5 Rollback If there is a problem with the installation, you can roll back to the previous version as follows: 1. Download the file finesse-cce.1101.es.rollback.cop.sgn to an SFTP Server that can be accessed by the Finesse system. 2. Use SSH to log in to your Finesse system with the platform administration Account. 3. Access the CLI and run the following command: utils system upgrade initiate 4. Follow the instructions that appear on your screen. When prompted, provide the location and credentials for the remote file system (SFTP server). 5. When presented with the list of available upgrade options, select finessecce.1101.es.rollback.cop.sgn 6. After rollback is complete, restart the system using the command: utils system restart 7. To verify Finesse is now running the correct release, access the CLI using the Administrator credentials and enter the following command: show version active Make sure that finesse-cce.1101.es.rollback.cop is listed under Optional packages. Otherwise, please contact Cisco TAC. Note: The Finesse Rollback COP file restores your system to the base Finesse Version (in this case, Cisco Finesse Release 11.0(1)). You will have to clear the browser cache to avoid stale Context Service gadgets showing up. Resolved Caveats/Features in this Engineering Special Defects fixed in 11.0(1) ES07 CSCvd93589 Failover testing, Finesse side B takes 8 min to connect 3 CSCvc90295 CSCvf00916 Team performance gadget show no agents in team after ctisvr failover Authentication failure on Finesse Notification after CG and PG failover 2 3 CSCve11977 Finesse Agent State Change getting Delayed. 2 Defects fixed in 11.0(1) ES06 CSCVb19751 CSCux53492 Authentication failure of Finesse notification service after PG failover Finesse 11 Custom Variable layouts not working on secondary node 2 2 CSCuz56205 (CSCva32354) Replication fails after Finesse Restart 1 CSCva92010 FIPPA screen stays dominant when going off-hook in ready state 2

6 CSCvb23567 Call transfer screen is blocked on fippa due to Call variable layout 2 CSCux70426 (CSCux71683) Finesse IPPA call transfer is blocked by the call variable screen 2 CSCvb37331 Finesse CFAdmin Shindig authentication fails if password w colon symbol 2 CSCvb63177 Revert xmpp.httpbind.client.idle timeout to 60 2 Context Service Removal As part of the ES6 installation, apart from the defect fixes listed above, the Context Service Integration functionality will be disabled in Finesse. Please note that it is a irreversible change - once this is disabled, even rollback WILL NOT restore the functionality. Affected functionality is described in the appendix section. Defects fixed in 11.0(1) ES05 CSCuz19136 CLI command to turn off SSRF fails 2 CSCuz38289 Finesse agent can't change state after idling over 30 minutes 1 CSCuz39903 Finesse is showing the wrong Context Service status after registration 2 CSCuy14779 Finesse Supervisor cannot see agent status update after PG failover 2 CSCuz45855 Finesse Default Skill Group visible in Queue Statistics 2 CSCuv28457 Openfire crashes when non-valid XML 1.0 characters are passed to finesse 1 CSCux28810 Non printable character in Openfire crashes Finesse server 1 CSCuw38234 Unrestricted File growth of localhost_access_log.txt fills disk 1 CSCuz34757 CSCuw79085 Finesse gadgets and buttons disappear intermittently when using IE (See Appendix below) Cisco Finesse and Contact Center XMPP Default Account Vulnerability 3 1 CSCux70426 Finesse IPPA call transfer is blocked by the call variable screen 1 CSCuy94569 Cannot turn on Openfire debug logging after 10.5(1) ES7 1

7 CSCuy33974 Finesse is not deleting users in OpenFire when a user is deleted. 1 Defects fixed in 11.0(1) ES04 (This enables integration with Cisco Context Service) CSCuy79023 Incorrect CS SDK Version in Finesse ES 2 Defects fixed in 11.0(1) ES03 CSCuw86623 Cisco Finesse SSRF Vulnerability (See Appendix below) 2 CSCuy36899 Finesse removes connection data on STOPPED connector 2 Defects fixed in 11.0(1) ES01 CSCuw70389 Finesse 3rdparty gadgets cannot be loaded into 3rd party gadgets. 2 Bug Search Tool To access the Bug Search Tool, go to and log in with your Cisco.com user ID and password.

8 Appendix CSCuw86623: SSRF Vulnerability Fix This fix ensures that gadgets that invoke 3 rd party REST APIs proxied via Finesse shindig are authenticated by Shindig. After installation of 11.0(1) ES05, the REST proxy authentication is enabled by default. Finesse provides a new utils commands which can be used to disable / enable the authentication for the proxied REST request. utils finesse rest_proxy_auth enable utils finesse rest_proxy_auth disable utils finesse rest_proxy_auth status NOTE: If HTTPS redirect is enabled, users can set the REST proxy authentication to either disabled or enabled. However, if HTTPS redirect is disabled users must set the REST proxy authentication to disabled. For more details about SSRF, see Also, see the defect notes in the bug search tool. CSCuz34757: Finesse gadgets and buttons disappear intermittently when using IE When IE compatibility mode was changed, the browser automatically refreshed and a blue screen was seen. With this fix, the browser will be redirected to the Finesse login page when compatibility mode is changed and the users can login again and continue their work. Context Service Removal 1. Context Service Admin gadget is removed The Context Service administration gadget will not appear in the Finesse administration console. 2. Context Service desktop gadget in removed The Context Service desktop gadget will be removed in the Finesse desktop both in default and customized team-specific layouts. Also, restoring to default layout does not bring back the gadget. 3. Log control Log generation from Context Service components will be minimal. Also, it will be regulated such that it is pruned faster. Upgrading without De-registering As part of the ES6 installation, Finesse will empty the data (related to Context Service), thereby leaving a dangling registration in the Context Service cloud. Therefore, it is recommended that it is deregistered before installing this ES.