Jump to: navigation, search

Recording Cloud Backup Service

Information.png Note: Not all changes listed below may pertain to your deployment.

May 15, 2018 (8.5.295.01)

What's New

Resolved Issues

  • Recording Cloud Backup Service (RCBS) now prints the version number correctly in the logs. Previously, RCBS was printing the version as "DEVELOPMENT-VERSION" in logs.

February 27, 2018 (8.5.290.49)

What's New

  • When started from the command line, Recording Cloud Backup Service (RCBS) now shows incremental progress of the download process by showing the percentage downloaded for the requested backup time period.

Resolved Issues

  • RCBS no longer displays an error when handling multi-part screen recordings. Previously, an error was displayed when renaming the screen recordings from "mp4.bin.part" to "mp4.bin". (GIR-8759)
  • If the configured download period is more than 1 day, the last_recording_endtime.txt file is updated every shardBy day (by default, 1 day) during the download process. This file cannot be viewed on Windows when the download process is in progress, but it can be viewed on Linux during download. (GIR-17788)
  • In the multi-threaded mode, RCBS no longer takes a lot of time for processing the recordings after download. (GIR-17837)

March 29, 2017 (8.5.270.73)

What's New

  • The commons-collection library used by the Recording Cloud Backup Service has been upgraded to version 3.2.2 to address a potential security issue.

December 20, 2016 (8.5.265.71)

What's New

  • Recording Cloud Backup Service (RCBS) supports AWS Signature version 4 for requests sent to Amazon S3 Services. RCBS also supports optional payload signing during the transfer. To enable the payload signing, set the option usePayloadSigning to true. Since payload signing affects performance, set the option to false to disable it if your installation does not require authentication. The default value is false.
  • Recording Cloud Backup Service (RCBS) now supports a query based on the startTime only, and no longer requires the overlap to be specified, when two consecutive runs with two windows adjacent to each other takes place. Previously, an overlap value had to be specified to avoid missing recordings when RCBS used two back-to-back download windows.

Resolved Issues

  • Recording Cloud Backup Service (RCBS) no longer uses the deprecated RFC2109 cookie format. Previously, the RFC2109 cookie format may have caused requests sent by RCBS to be rejected. (GIR-8286)

September 27, 2016 (8.5.260.59)

What's New

  • Recording Cloud Backup Service (RCBS) now supports multi-threaded and multi-instance download. For multi-instance RCBS, the download of the recordings can be shared by different RCBS instances running in parallel. For multi-threaded RCBS, the download tasks and the post-processing tasks can be carried out by multiple threads within the RCBS process.

Resolved Issues

  • Recording Cloud Backup Service (RCBS) now supports the minDate configuration parameter, which allows specifying the minAge with an absolute date instead of an offset value. (GIR-6834)
  • RCBS now supports disabling the download of the screen recording files through the configuration parameter. (GIR-6467)
  • RCBS no longer exports originalMediaDescriptor as part of the metadata export fields. (GIR-6008)

July 14, 2016 (8.5.241.13)

What's New

Resolved Issues

  • Recording Cloud Backup Service (RCBS) now supports the shardBy parameter to resolve deep pagination. This parameter allows the user to instruct RCBS to query recordings during a smaller period of time, using a minAge and maxAge range. The default value is "1" (day). Previously, if a user specified an exceptionally long range using the minAge and maxAge values, RCBS sent the complete range all at once to RWS, causing RWS to occasionally time out and return an empty result due to an Elasticsearch deep pagination issue. (GIR-6429)

March 1, 2016 (8.5.240.80)

What's New

  • Support for muxed screen backup.

October 2, 2015 (8.5.220.91)

What's New

  • This is the initial release of the Recording Cloud Backup Service. The Recording Cloud Backup Service allows you to make a backup copy of your Genesys Interaction Recording voice files (some or all) prior to their automated deletion as per the Cloud retention policy.

Known Issues

  • Recording Cloud Backup Service (RCBS) might terminate unexpectedly if the connection between the RCBS and RWS is broken while RCBS is waiting for the HTTP response. (GIR-6683)
  • If RWS has CSRF enabled, the RCBS might not handle the CSRF token properly and the request might fail. (GIR-6542)
    Workaround
    Disable the CSRF on the RWS side.
  • If awsRecordingPrefix and bucket are configured under the Recording Cloud Backup Service (RCBS) section, but the media file is stored under WebDAV, RCBS will attempt to download the files from Amazon S3 and a 404 error will occur in the logs. Currently, RCBS only supports downloading via Amazon S3. (GIR-4843)
    Workaround
    Remove the awsRecordingPrefix and bucket configuration values. This parameter no longer needs to be specified for RCBS 8.5.240.80 and higher.
  • When the Recording Cloud Backup Service's (RCBS) Web Services and Applications credential is from an EService agent, running RCBS may cause the status of the specific agent to remain Ready, even if the agent has already logged out of the agent desktop. (GIR-4781)
    Workaround
    To create a Contact Center Administrator credential for RCBS, do not assign the specific agent a default place and do not add him to the EService agent group.
  • Genesys Web Services rejects the server settings group configuration values for the Recording Backup Cloud Service exceeding 256 characters. (GIR-3137)
    Workaround
    Specify the configuration parameter in the config.properties file instead of using the server settings group.
  • When specifying a path name for the Recording Cloud Backup Service component in the configuration, use a forward-slash ("/") as the path delimiter for both Windows and Linux OS-es, since the single backslash ("\") is stripped off by the Java property reader. For example, use 'C:/TargetFolder instead of C:\TargetFolder when specifying the targetDir configuration value. Alternatively, a double backslash ("\\") will work on Windows also—for example, C:\\TargetFolder. (GIR-2925)

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 15 June 2018, at 05:05.