LA Finesse Gadget Installation and Configuration Guide
LA Finesse Gadget Installation and Configuration Guide
Updated: 2022-06-22
Contact Information
support@cbaliveassist.com
As CBA Live Assist uses the FCSDK for the voice and video capabilities, you can integrate
CBA Live Assist with existing SIP infrastructures such as call centers, PBXs and MCUs.
When a consumer requests support they see a small moveable video window that directly links
them to the agent on the call center. The application does not need to be aware of this window,
as it floats above all other screen content.
The voice and video link exists for the duration of the support call.
Co-browsing
When a consumer requests support, their application view is shared with the agent. The
application does not need to do anything to cause this to happen, because the co-browsing API
works without interaction from the application. The co-browsing session exists for the duration of
the support call.
Document Push
An agent in a support session can push PDF and image documents to the consumer. Both the
agent and the consumer can interact with the shared document, and the consumer’s view of the
document is replicated on the agent’s console.
Acceptable document types are: PDF, and the image formats GIF, PNG, and JPG/JPEG.
Remote Control
When a consumer requests support, their desktop is shared with the agent. The agent can click
on this shared desktop to interact with the consumer’s application. This ability to remote control
Annotation
While a consumer is in a support session, their view is shared. The agent can use the annotation
tool to draw on their shared image of the consumer’s screen. CBA Live Assist transfers these
annotations to the consumer’s application, which draws them on the consumer’s screen so that
the consumer can see them.
The consumer’s application does not need to be updated or aware of this annotation taking
place.
Oracle Java
Cisco Finesse
Fusion Live Assist with all its own pre-requisites (see the CBA Live Assist Overview and
Installation Guide).
CBA Live Assist Finesse Gadget is dependent upon Fusion Application Server (FAS,) Fusion
Client SDK and CBA Live Assist, all of which can either be installed using their appropriate
installers or as part of the pre-packaged CBA Trial Environment. CBA Live Assist must be
deployed to the same FAS instance as Fusion Client SDK.
CBA Live Assist requires the presence of Oracle Java 8 JRE or JDK, which can be obtained
from Oracle:
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Console Installation
You can install the CBA Live Assist Finesse Gadget using the command line by specifying the
required installation configuration in a properties file.
The CBA Live Assist Console installer can install the Finesse Gadget to either a Production or a
CBA Trial Environment; you can run the installer either on the machine hosting the Fusion
Application Server domain controller, or remotely on another machine.
Installer Properties
Property Description
Runtime
Administration Web UI
This only installs the CBA Live Assist Finesse Gadget plugin
cli.dir
to the CLI - the CLI must already have been installed with the
FCSDK plugin.
The CBA Live Assist Finesse Gadgets are configured via the web administration console at:
https://<fas address>:8443/web_plugin_framework/webcontroller/finesse-admin/
where <fas address> is the IP address or host name of the CBA Live Assist server, or via the
CLI.
Parameter Description
The name to use in place of the agent name if Display Agent Name
Fixed Agent Name
is not selected.
Trust All Whether to trust all server certificates, even if their certification chain
Certificates is not trusted.
Whether to trust certificates that the JDK trust store believes are
Trust JDK
valid. This typically includes certificates issued by well-known
Certificates
providers (for example, Verisign)
If the Finesse user’s user name and password match the local user
Local Password name and local password, the user is granted the roles in Local
Roles (for example, Agent and Supervisor roles).
A list of roles granted to the Finesse user if their user name and
Local Roles password match the local user. The Agent Gadget requires the
Agent role and the Supervisor Gadget requires the Supervisor role.
To provide a secure Finesse Desktop, add the HTTPS identity certificate of the cluster hosting
the CBA Live Assist Gadgets to the Finesse Tomcat trust-store:
1. Obtain the FAS certificate by following the Exporting an Identity Certificate section in the
FAS Administration Guide to export the LB’s HTTPS identity certificate:
ii. In the Management Console, from the top-right menu, select Profiles.
iii. From the Profile drop down list, select the management profile.
iv. From the menu on the left, expand Subsystems and Trust Management, and select
ID Certificates.
vi. Select https in the bottom Identity Certificate Group Management table.
vii. With the https row selected, click the Export button.
Refer to the Add Certificate for HTTPS Gadget section within the Cisco Finesse
Administration Guide for details:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/fine
sse_1051/user/guide/CFIN_BK_C3A9BCBC_00_cisco-finesse-administration-guide-1051.pdf
Restart the Tomcat service on all the Finesse nodes after importing the certificate into Finesse.
Configure the Finesse server with the location of the CBA Live Assist Agent and Supervisor
Gadgets.
https://<finesse-server>/cfadmin/container
4. Add a tab for the Agent (replacing the text in green in the diagram above) as follows:
<tab>
<id>LAA</id>
<gadgets>
<gadget>
https://<fas address>:8443/finesse_assist_gadget/FinesseAssist.xml?finesseVersion=x.x.x
</gadget>
</gadgets>
</tab>
Ensure that the finesseVersion request parameter in the URL above is correct for your version of
Finesse. If a value of 10.6.1 or later is used, then Finesse assets (such as finesse.js) will be
loaded from the Finesse server rather than the gadget. The change in where assets are loaded
from should improve compatibility of the gadget when it runs in future versions of Finesse.
5. Add a tab for the Supervisor (replacing the text in blue in the diagram above) as follows:
<tab>
<id>LAS</id>
<gadgets>
<gadget>
https://<fas address>:8443/finesse_assist_admin_gadget/FinesseAssistAdmin.xml
</gadget>
</gadgets>
</tab>
Replacing <fas address> with the IP address or host name of the master FAS node.
6. Click Save.
The Agent tab definition must be added to the Agent role section within the XML; however, it
may also be added to the Supervisor role section, if all Supervisors need Agent functionality.
The example shows the URL used to access the gadgets (hosted on the FAS cluster) as
secure. You can change this to insecure if required. If the URL is secure, the Finesse
servers must be configured to trust the FAS cluster - see the Add Certificates to Cisco
Finesse section on page 13.
After restarting the master node, run the script on all the slave nodes in the cluster, restarting
each node:
/opt/cba/<FAS>/resources/enable-sslv2.sh
/opt/cba/<FAS>/resources/disable-sslv2.sh
See the CBA Live Assist Finesse Agent and Supervisor User Guide for details.
The Agent and Consumer browsers must be separate to avoid WebSocket issues during testing.
To do this, either
open the Consumer browser as an Incognito window from the Agent browser.
The sample website is a convenient CBA Live Assist enabled website to use for testing.
Provide the agent details as a URI encoded parameter, in the form:
https://<fas address>/assistsample/?agent=sip:<tel-num>@<CUBE_IP>
Answering the call should start a two way voice and video call in each browser.