Revision as of 13:07, January 26, 2016 by Mlevy (talk | contribs) (Advanced Software Installation Tips & Tricks)
Jump to: navigation, search

Deploying the Screen Recording Service - Advanced Configuration

The following sections provide advanced Screen Recording Service installation and configuration steps.
For basic instructions about how to install and configure the Screen Recording Service, see: Deploying the Screen Recording Service.

Enable Screen Recording

Important
Before you can start to capture and play back the screen recordings, you must make sure that you have configured the Web Services components, and encryption specifically for screen recording.

To set up recording conditions, add the recordingWhen parameter to the [screen-recording-client] section of the Web Services Cluster object.

When this parameter is set in the Web Services Cluster object, the recording condition applies to all agents in the environment. You can create the recordingWhen parameter in a [screen-recording-client] section of each agent object to override the settings at the environment level.

The parameter value is an expression of conditions to enable screen recording for each agent. The format is:

  • For Non-voice agents: recordingWhen = condition1,condition2,... where condition1,condition2, etc. are a set of conditions that must all be true in order for the screen recording to be taking place.
  • For Voice agents: Screen recording starts when the voice recording starts except in cases where recordingWhen is explicitly set to off.

Integrating with Workspace Web Edition

If your agents use Workspace Web Edition as their desktop, screen recording must be set up as follows to support single sign on:

Using Genesys Administrator Extension, add the following parameters to the interaction-workspace section of the Web Services Cluster object.

Important
If you are working with HTTP, the Screen Recording Service default port number is 8080. If you are working with HTTPS, the default port number is 443. In addition, verify that the Workspace Web Edition configuration is set to 8080 or 443.
Parameter Name Mandatory Description Default Value
privilege.screen-recording.can-use Y Specifies whether agents can use screen recording. If set to true, the integration module is loaded and sends credentials to the client. false
screen-recording.client.address N Specified the IP address that the Screen Recording Client listens for credentials on. Valid values: 127.0.0.1, [::1] 127.0.0.1
screen-recording.client.port N Specifies the port that the Screen Recording Client listens for credentials on. 8080
screen-recording.client.ping-interval N Specifies the interval, in milliseconds, between ping requests to the Screen Recording Client. 5
screen-recording.client.max-attempts N Specifies the maximum number of attempts to establish communication with the Screen Recording Client. 5
screen-recording.client.server-url N Defines the GWS server address that the Screen Recording Client will use for communication.


Integrating with Workspace Desktop Edition

If your agents use Workspace Desktop Edition as their desktop, screen recording must be set up according to the instructions in the Workspace Desktop Edition Deployment Guide.


Enable Screen Recording for a Contact Center

To enable the screen recording feature for a given Contact Center:

Using the ops account:

POST http://<Web Services-host-prefix>/api/v2/ops/contact-centers/<ccid>/features
{ "uris": ["/api/api-voice-screenrecording","/api/api-multimedia-screenrecording"] }


Advanced Installation Procedures

Configuring During the Installation

If you have made customizations to the config.json file in your environment, you can configure the installer to automatically replace the baseline version with your customized version, using the following command while installing the Screen Recording Service.

setup.exe /VERYSILENT /CONFIG="C:\path\to\config.json"

To verify the version installed, browse to https://127.0.0.1/version or http://127.0.0.1:8080/version.


Creating Self-Signed Certificates

If you did not use the /TASKS="HTTPS" parameter to install the Screen Recording Service, and if you are not using your own certificates, you can create self-signed certificates as follows:

  1. Open a command window as an Administrator.
  2. Navigate to the <install_dir>\Certificates\Self-Signed directory.
  3. Run the create_certificates.bat file. This creates a set of unique self-signed certificates.
  4. Run the install_certificates.bat file. This installs the new self-signed certificates to Windows trusted certificates store.

Installing Your Own Certificates

If desired, you can use your own certificates as follows:

  1. Provide a certificate for the IPv4 host, 127.0.0.1, in the <install_dir>\Certificates\server.pem file.
  2. Install the .pfx form of this certificate to the local certificates store as a "Trusted Root Certification Authority" file.
  3. Provide a certificate for the IPv6 host, [::1], in the <install_dir>\Certificates\serverIp6.pem file.
  4. Install the .pfx form of this certificate to the local certificates store as a "Trusted Root Certification Authority" file.
  5. The PEM certificate files should include both the private RSA key and the certificate itself. [+] Show an example.
Important
When the .pem certificates must be protected by a password, the password is configured in the config.json file using the certificatePassword parameter. The default certificatePassword is genesysscreenrecording. For more details, refer to the Client Side parameters table in step #2 of the Advanced Configuration for the Screen Recording Service section.


Advanced Configuration for the Screen Recording Service

The Screen Recording Clients running on all desktops should be configured when they are managed locally on the system (using config.json), and occasionally when configurations are managed centrally. This configuration should use the GAX Web Services Cluster application object.

  1. If your server uses a self-signed certificate, set the certificate parameter to the path on the file system where the pem file is stored.
  2. Edit the local config.json file on the Screen Recording Client machine, and add the client parameters.
    [+] Show the table describing the parameters.
  3. In the most basic configuration, you will not need to add the following parameters, they are all optional. However, if you intend to use any of the server parameters, install using Genesys Administrator Extension, and following the next steps:
    1. At the Environment level, locate the Web Services Cluster application object that was created during the Web Services installation.
    2. Edit the application object, and create a new section named screen-recording-client. The following figure provides an example of the screen-recording-client section.
      [+] Show the table describing the parameters that can be added to this section.

    Advanced Software Installation Tips & Tricks

    • To debug problems with the installation, check C:\src_setup.log.
    • If a proxy is used for agents to access Workspace Web Edition, make sure 127.0.0.1:443 and 127.0.0.1:8080 (or the appropriate ports, if non-default values are used) are in proxy white list. This lets the agents access Workspace Web Edition directly without the proxy.
    • The recommended installation procedure will install the Screen Recording Client's self-signed PFX certificates to the root certificates store.. For more information, see Creating Self-Signed Certificates.
    • In the default configuration, the recordingWhen parameter is set to false. If you do not enable screen recording as described in the next section, screen recordings will not be captured.
    • During startup, the Screen Recording Client writes the current version to the log file. However, since the log file is periodically cleaned, the version is not always be at the top. Use the following command line to check the version along with other properties of the Screen Recording Client—wmic datafile where name='C:\\<Installation Directory>\\SRC.exe'
    • If you have deployed with a GoDaddy certificate, without including the G2-to-G1 cross certificate (that is, the intermediate certificate), you must perform one of the following manual workarounds:
      • Include the G2-to-G1 cross certificate in the server side certificate (concatenated with the server certificate).
      • Import the G2-to-G1 cross certificate into the SYSTEM (Local Machine) Root CA certificate store.

      The G2-to-G1 certificate can be downloaded from https://certs.godaddy.com/repository/gd_bundle-g2-g1.crt.

    • When a Proxy is used, it may interfere with SRS. SRS runs as an HTTP server and it relies on an incoming socket connection to identify the agent’s windows session correctly. If the HTTP requests are forwarded by a proxy, SRS may not be able to identify the user session correctly in a multi-user environment. In a single user case, SRS will fall back to the currently active windows session. To avoid this it is recommended that localhost (127.0.0.1) connections be excluded. When the proxy is an internal system service (like an Antivirus\Firewall), it is recommended that the SRS related processes (SrsProcess.exe and GenesysServiceHandler.exe) should be added to the security software exception\white list.
Comments or questions about this documentation? Contact us for support!