Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Genesys Cloud CX is a suite of cloud-based services for enterprise communications, collaboration, and customer experience management.

The current Genesys Cloud Integration uses the Genesys Cloud API to provide near real-time ingestion of audio files created by the Genesys system.


Please note: Genesys Cloud CX integration with SBC recording and Genesys Cloud CX integration with AudioHook recording are not currently supported.


For a general description of Verba Import sources, please refer to Import sources.

...

1. Creating a Genesys Import Source


1.1. Pre-requisites

1.1.1. Customer firewall team enables access to: 

  • *.*.*.amazonaws.com on port 443.
  •  HTTPS Genesys Cloud API Authentication URL and port 443 from the VFC server or via the Proxy if required.
  •  HTTPS Genesys Cloud API URL URL and port 443 from the VFC server or via the Proxy if required.

1.1.2. Customer provides TLS Certificate, otherwise standard VFC API certificate will be used.

1.2. Create a Genesys OAuth Integration


Follow these steps in Genesys Cloud before creating a new VFC Import Source:

...

Anchor
Create a VFC Import Source
Create a VFC Import Source

1.3. Create a VFC Import Source

Next, follow the steps in Verba to create a new Import source:

...

Configuration Item

Description

NameName your Import Source. This name will identify the source across the system.
TypeSelect Genesys Cloud Import Source.
Client Id

Mandatory value copied from the Genesys Cloud OAuth Integration.

Client Secret

Mandatory value copied from the Genesys Cloud OAuth Integration.

HTTPS Genesys Cloud API Authentication URL

Mandatory Genesys URL used when the Import Source obtains the Access Token, for example: https://login.usw2.pure.cloud.

Full list available at: https://developer.genesys.cloud/platform/api/ under Auth Server

Customer firewall team must enable access to this URL and port 443 from the VFC server or via the Proxy if required.

HTTPS Genesys Cloud API URL

Mandatory Genesys URL used when the Import Source interacts with the Genesys API, for example to obtain user information.  For example: https://api.usw2.pure.cloud

Full list available at: https://developer.genesys.cloud/platform/api/ under API Server

Customer firewall team must enable access to this URL and port 443 from the VFC server or via the Proxy if required.

TLS Certificate File / Thumbprint

Optional certificate file / certificate thumbprint used for the Genesys Cloud connection.

If not configured, the server certificate will be used.  For more information see Server Certificates

TLS Key FileOptional file system location where the certificate key is stored.
TLS Key PasswordSpecify the password for the file that contains the certificate keys.
TLS Trust ListCertificate chain (or Chain of Trust) is made up of a list of certificates that start from a server's certificate and terminate with the root certificate. If your server's certificate is to be trusted, its signature has to be traceable back to its root CA.
Forward Proxy AddressOptional. IP address or FQDN of the forward proxy. When defined, the system will connect through a forward proxy.
Forward Proxy PortOptional. The port of the forward proxy.
Forward Proxy UsernameOptional. Username for basic authentication for the forward proxy server.
Forward Proxy PasswordOptional. Password for basic authentication for the forward proxy server.
Transcoding by GenesysMandatory codec selection.  Genesys transcodes to the specified codec before delivering audio to the Import Source.
Recording Timezone

Mandatory Import Source timezone as all Genesys times are in UTC.  This ensures recordings are presented with the correct time.

Recording Start Timestamp

Mandatory timestamp of first audio to be recorded by the Import Source.

Import Batch Size (minutes)

Mandatory time to be added to Recording Start Timestamp in order to create a range used for retrieving audio from Genesys.

This creates a sliding window that must always be wider than the longest Genesys call.

Recording Lag (minutes)Maximum delay before audio is ingested after the end of a call.
Genesys Cache Lifetime (minutes)

Mandatory time to store Genesys user information for performance reasons within the Import Source before it is automatically refreshed.

On Completion

Delete Recordings Stored in Genesys Cloud

Optional to make Verba the single recording source for search, replay, archive and analysis.

...

Step 4 - Click Save to save the settings

...

2. Import Policy Configuration

Follow the steps below to configure the Data Import action:

...

Anchor
User and Extension Configuration
User and Extension Configuration

...

3. User and Extension Configuration

Step 1 - In the Verba web interface, navigate to Users > Administration > Users and then click Add New User

...

Anchor
Types of alerts raised by the Genesys Import Source
Types of alerts raised by the Genesys Import Source

...

4. Types of alerts raised by the Genesys Import Source

Alert Message

Explanation

Failed to retrieve next batchUnable to retrieve list of recordings, likely network connectivity issue.

Conversation failed to import

Problem with call metadata or media file.

Could not obtain timezone offsets

Timezone offsets could not be extracted from the VFC database.
CDR placed in retry bufferCall media unavailable for download.
Conversation failed to delete from Genesys CloudPermission issue.

Anchor
Migration Status Reporting
Migration Status Reporting

...

5.Migration Status Reporting

No report files are generated, however at the end of each batch, a notification alert is raised containing details of recordings migrated from Genesys into VFC.  The alert contains the Genesys Cloud Conversation Id, along with the extension that participated in the call and a call participant number.  The alert also contains the VFC conversation identifier and flags indicating whether the recording was successfully imported and media successfully downloaded, for example, it will take a few minutes to become available once the call ends.  Another flag indicates if the conversation was already imported, for example, if the start time of ingestion was reset.  If the switch is quiet, for example, overnight, the notification alert will normally state 'No conversations imported'.

...

Anchor
Genesys Metadata
Genesys Metadata

...

6. Genesys Metadata

The system captures the following metadata specific to Genesys recordings. These fields are available through the standard metadata template.

...