Cisco Finesse Release 11.5(1) ES02

Transcription

1 Cisco Finesse Release 11.5(1) ES0

2 Contents Cisco Finesse Release 11.5(1) ES0... Critical Note... Valid Upgrade Paths... Installing Finesse Release 11.5(1) ES0... Rollback... 4 Resolved Caveats and Feature Updates in Release 11.5(1) ES TLS 1. Support in Notification Service... 6 IE 11 Native Mode for Finesse in Unified CCE... 6 Context Service Serviceability (CS)... 6 Security Vulnerability Fixes for Struts Bug Search Tool... 7 Release Caveats... 7

3 Cisco Finesse Release 11.5(1) ES0 File Name finesse-cce.1151.es cop.sgn finesse-cce.1151.es.rollback.cop.sgn MD5 Checksum e4:ba:a:e1:44:e6::59:1f:be:1f:04:5e:9:e9:d a:f6:0e:70:6:9d:1d:9e:8:c1:bd:7:47:9b:70:4f Critical Note These are the critical changes in ES0: In ES0, only TLS version 1. is supported without which Finesse Desktop will not function as expected. To enable TLS1., follow further instructions in the section - Resolved Caveats and Feature Updates. Finesse desktop should only be used with Native mode as compatibility mode is no longer supported on Internet Explorer 11. Valid Upgrade Paths Cisco Finesse Release 11.5(1) ES0 is delivered as a Cisco Option Package (COP) file. The supported upgrade paths for 11.5(1)-ES0 are: 11.5(1) FCS 11.5(1) ES01 NOTE: 11.5(1) ES0 can be applied irrespective of whether the language COP is installed. Installing Finesse Release 11.5(1) ES0 You must perform the following procedure first on the primary Finesse node and then on the secondary Finesse node. IMPORTANT: You must use the CLI to perform this upgrade. Do not use the Cisco Unified Operating System Administration page to perform this upgrade or the installation may not proceed. 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. 1. Download finesse-cce.1151.es cop.sgn to an SFTP server that can be accessed by the Finesse system.. Use SSH to log in to your Finesse system with the platform administration account.. 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.5(1) FCS 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.1151.es cop.sgn 6. After installation is complete, restart the system using the command:

4 utils system restart 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 Ensure that finesse-cce.1151.es cop is listed as an Optional package. Otherwise, contact Cisco TAC. 8. Check that the installation is successful by signing in to Finesse ( or hostname of Finesse server/desktop). Clear the browser cache to avoid Context Service gadgets from being displayed. 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.1151.es.rollback.cop.sgn to an SFTP Server that can be accessed by the Finesse system.. Use SSH to log in to your Finesse system with the platform administration Account.. Access the CLI and run the following command: utils system upgrade initiate 4. Download the file finesse-cce.1151.es.rollback.cop.sgn to an SFTP Server that can be accessed by the Finesse system. 5. Follow the instructions that appear on your screen. When prompted, provide the location and credentials for the remote file system (SFTP server). 6. When presented with the list of available upgrade options, select finessecce.1151.es.rollback.cop.sgn 7. After rollback is complete, restart the system using the command: utils system restart 8. 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.1151.es.rollback.cop is listed under Optional packages. Otherwise, contact Cisco TAC. NOTE: The Finesse Rollback COP file restores your system to the base Finesse Version (in this case, Cisco Finesse Release 11.5(1) FCS). Clear the browser cache to avoid outdated Context Service gadgets from being displayed. Resolved Caveats and Feature Updates in Release 11.5(1) ES0 Defect ID Description Severity CSCvb19751 Due to Tomcat failing on Finesse Side A, agents logging in using IE 11 are unable to failover to Finesse Side B. CSCvb0767 Openfire closes session to CTISRV when receiving non-xml symbols. CSCva780 Finesse Tomcat and Openfire crash due to invalid XML characters. CSCux8810 CSCvb9964 Finesse server crashes if there are any non-printable characters in Openfire. In Finesse 11.5(1), authentication fails when HTTP workflows are executed.

5 CSCva1067 Finesse displays ConnectionDeviceID instead of ANI during a transfer. CSCvc51650 In Finesse 11.5(1), during queue statistics sort, the live data disappears completely with no data or any display of error message. CSCvb99474 Finesse does not allow more than characters for Non-SSO login. CSCvc1476 CSCvc611 CSCvc705 CSCvc971 CSCva9010 Finesse cfadmin page shows de-registration failed even if deregistration is successful. Finesse-CS De-Registration & Registration Tasks should be Event based instead of Fixed Timers. Error Payload for APIs in Fusion Management Connector does not return JSON (only XML). CS SDK API returns 404 error message when Context Service is not registered. Finesse IPPA screen stays dominant when going off-hook in ready state. 6 6 CSCux7046 Finesse IPPA call transfer is blocked by the call variable screen. CSCvb567 CSCvb8890 Call transfer screen is blocked on Finesse IPPA due to call variable layout. In Finesse 11.5(1) users are unable to navigate to the Platform Serviceability page. CSCvc910 Finesse automatic failover does not work intermittently. CSCvc90686 In Unified CCX deployments, Finesse Tomcat shows a high CPU due to which agents are unable to login or logout. CSCvb19751 Authentication fails for Finesse notification service after PG failover. CSCvd0614 CSCvc65975 CSCvc9095 CSCvc4167 CSCvd9807 Context Service Status API should return all fields as returned by CS SDK API. Finesse IPPA allows multiple logins of the same agent across same/different phones simultaneously. Team performance gadget show no agents in the team after a CTISVR failover. Context Service Logback logs are displayed in catalina logs. These need to be displayed only in application/webapp specific logs. During agent login for load, number of agents are unable to login due to notification service issues. 6

6 TLS 1. Support in Notification Service In Notification Service, only TLS version 1. is supported. The following TLS versions are disabled: 1, 1.1 with ES0 In Internet Explorer v11, Options->Advanced -> Settings must have Use TLS 1. checked in order to get a functionally working desktop. IE 11 Native Mode for Finesse in Unified CCE Finesse desktop should only be used with Native mode as compatibility mode is no longer supported on Internet Explorer 11. Context Service Serviceability (CS) Cisco Finesse includes the capability to retrieve Context Service status by invoking CS SDK API. It retrieves the Context Service SDK version that is being used in Finesse, registration status, and ping latency of CS services and logs them in Fusion Management Connector log (/opt/cisco/ccbu/logs/fusion-mgmt-connector). Cisco Finesse has implemented the capability to invoke Context Service Statistics Summary and Reset Statistics API in order to poll CS JMX counters and log the resulting information periodically in Finesse Authorization log. Path of the Log file(/opt/cisco/desktop/logs/finesseauth). Cisco Finesse provides dynamic re-initialization of the Context Service SDK so that there is no downtime or disruption with respect to the Context Service management operations.

7 Security Vulnerability Fixes for Struts.. This release also includes security vulnerability fixes for Apache Struts... Bug Search Tool To access the Bug Search Tool, go to and log in with your Cisco.com user ID and password. Release Caveats Defect ID Description Severity CSCvd87 Few call parties randomly do not get displayed in the call control gadget after a PG failover. CSCvd8779 Pending states are not applied on the Agent Desktop after a client side failover. NOTE: When Finesse Desktop is accessed on Google Chrome with protocol HTTP, browser automatically redirects Finesse to HTTPS even though HTTPS Redirect is disabled using Finesse Admin CLI. Finesse 11.5 supports 000 HTTPS agents, and this redirect has no impact on scaling and performance of the system, for more details, visit the Finesse Installation guide here.