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.
Migration Support
The following modalities are supported: Voice only.
Creating a Genesys Import Source
Create a Genesys OAuth Integration
Follow these steps in Genesys Cloud before creating a new VFC Import Source:
Step 1 - Open the Genesys Cloud Admin Page, navigate to Integrations > OAuth and press the Add Client button:
Step 2 - Select Grant Type Client Credentials. The Token Duration can be adjusted as required because it is renewed automatically by the VFC integration. Then click Save. The Client ID and Client Secret are automatically generated.
Step 3 - From the Genesys Cloud Admin Page, navigate to Admin > Roles/Permissions and create a role for the OAuth integration to run under.
Each recording file is considered an object that is subject to access control at the user level. When a recording file is generated, the access control for the recording file is set based on the following criteria:
- Access control is set based on the agent that was recorded. Agents are organized as an agent hierarchy; for example, the hierarchy can be a reporting structure in an organization.
- Access control is set based on partitions. Partitions are set as a specific attached data in a call, and the attached data is typically set by a routing strategy.
For more details, see https://docs.genesys.com/Documentation/CR/latest/Solution/AccessControl
Create a VFC Import Source
Next, follow the steps in Verba to create a new Import source:
Step 1 - Open the Verba Web interface then select Data > Import Sources from the top menu
Step 2 - Click on the Add New Import Source link on the top right
Step 3 - Complete the configuration according to the requirements in the following table
Configuration Item | Description |
|---|---|
| Name | Name your Import Source. This name will identify the source across the system. |
| Type | Select 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 |
| 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 |
| 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 File | Optional file system location where the certificate key is stored. |
| TLS Key Password | Specify the password for the file that contains the certificate keys. |
| TLS Trust List | Certificate 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. |
| Transcoding by Genesys | Mandatory 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
Import Policy Configuration
Follow the steps below to configure the Data Import action:
Step 1 - In the Verba web interface, navigate to Data > Data Management Policies
Step 2 - Click on the Add New Data Management Policy button at the top-right corner of the page
Step 3 - For the action, select Data Import
Step 4 - Under Available Import Sources, select the Import Source that you created, then click on the Add button just below the text field
Step 5 - Configure the policy details, based on the information that is shown in the configuration items summary table below
Step 6 - Set up how frequently the Import should be run in the Scheduling section
Step 7 - Click on Save
Configuration Parameter Name | Description |
|---|---|
| Enable Recording Rules | Specifies if all data should be processed in the imported data set or just the records of the recorded users as configured in Verba |
| Execute Only on Selected Servers | If enabled, a specific server can be chosen that will run this policy |
Types of alerts raised by the Genesys Import Source
Alert Message | Explanation |
|---|---|
| Failed to retrieve next batch | Unable 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 buffer | Call media unavailable for download. |
| Conversation failed to delete from Genesys Cloud | Permission issue. |
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'.
Genesys Metadata
The system captures the following metadata specific to Genesys recordings. These fields are available through the standard metadata template.
Metadata Field | Description | Template | Available |
|---|---|---|---|
| Start Date | Start date of the conversation | Standard | Yes |
| Start Time | Start time on the conversation | Standard | Yes |
| End Date | End date of the conversation | Standard | Yes |
| End Time | End time of the conversation | Standard | Yes |
| Duration | Length of the conversation | Standard | Yes |
| User | Name of the recorded user | Standard | Yes |
| From | Subscriber / Third Party Phone number | Standard | Yes |
| From Info | User / contact name | Standard | Yes |
| To | Subscriber / Third Party phone number | Standard | Yes |
| To Info | User / contact name | Standard | Yes |
| Direction | Direction of the call from the system perspective, requires configuring internal number/domain patterns | Standard | Yes |
| Direction (User) | Direction of the call from the recorded user perspective | Standard | Yes |
| From (Verba) | Verba user name associated with the From Number | Standard | Yes |
| To (Verba) | Verba user name associated with the To number | Standard | Yes |
| Location | Hostname of the recording server | Standard | Yes |
| End Cause | Normal | Standard | No |
| Audio Codec | Audio codec of the recorded streams | Standard | No |
| Video codec | Video codec of the recorded streams | Standard | No |
| Platform Call ID | Unique conversation identifier received from the recorded platform | Standard | Yes |
| Silence Ratio | Ratio of silence in the conversation | Standard | No |
| Talkover Ratio | Talkover ratio of the conversation | Standard | No |
| Longest Silence | Length of the longest silence present in the conversation | Standard | No |
| User ID / Agent ID | User ID | Standard | No |
| From Device | Device ID of the calling party | Standard | No |
| To Device | Device ID of the called party | Standard | No |
| Dialed Number | Original dialed number | Standard | No |
| From IP | IP address associated with the calling party | Standard | No |
| To IP | IP address associated with the called party | Standard | No |
| Source Platform | Genesys | Standard | Yes |
| Conversation Type | Voice | Standard | Yes |
| Media Length | Length of the media file related to the conversation in hhh:mm:ss format | Standard | No |
| Media Error | Shows the media processing errors during recording | Standard | No |
| Voice Quality | Overall voice quality check score for the conversation | Standard | No |
| Record Type | Standard | Standard | Yes |
| 2N Source | In case of duplicate (2N) recording, records are marked as primary or secondary | Standard | No |