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.

...

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:

    1. 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.
    2. 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

...

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.

Genesys Cloud API Authentication URLMandatory Genesys URL used when the Import Source obtains the Access Token, for example: http://login.usw2.pure.cloud
Genesys Cloud API URLMandatory Genesys URL used when the Import Source obtains recordings, for example: http://api.usw2.pure.cloud
TLS Certificate File / ThumbprintOptional certificate file / certificate thumbprint used for the Genesys Cloud connection.
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.
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.
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.

...

Configuration Parameter Name

Description

Enable Recording RulesSpecifies 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 - TBC

Alert Message

Explanation

Could not parse configuration of sourceProblem with Import Source configuration setting.

Unexpected problem with underlying VFC database/filesystem

Could not connect to database or write file to local disc, check firewall and disc permissions.

Failure to process Call Metadata

Unexpected or unavailable ACR Genesys call metadata values.
Failure to communicate with ACRGenesysFirewall or network configuration problem.No more ACR recordings availableBatch start time exceeds the last ACR recording timestamp.
Detected no recorded parties in a recordingNo recording owner found in customer custom metadata.Failed to retrieve media from ACRMedia unavailable or download interrupted.
Unable to find expected ACR call metadataEither standard or ACR extended call metadata could not be extracted.
Could not obtain time zone offsetsTimezone offsets could not be extracted from the VFC database.

Migration Status Reporting - TBC

No report files are generated, however at the end of each batch, a notification alert is raised containing details of recordings migrated from ACR Genesys into VFC.

Image Removed

ACR metadata

Genesys Metadata - TBC

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

Yes

Metadata Field

Description

Template

Available

Start DateStart date of the conversationStandardYes
Start TimeStart time on the conversationStandardYes
End DateEnd date of the conversationStandardYes
End TimeEnd time of the conversationStandardYes
DurationLength of the conversationStandardYes
UserName of the recorded userStandardYes
FromSubscriber / Third Party Phone numberStandardYes
From InfoUser / contact nameStandardYes
ToSubscriber / Third Party phone numberStandardYes
To InfoUser / contact nameStandardYes
DirectionDirection of the call from the system perspective, requires configuring internal number/domain patternsStandardYes
Direction (User)Direction of the call from the recorded user perspectiveStandardYes
From (Verba)Verba user name associated with the From NumberStandardYes
To (Verba)Verba user name associated with the To numberStandardYes
LocationHostname of the recording serverStandardYes
End CauseNormal, Hold, Transfer, Conference, Device Change, From Terminated, To TerminatedStandardNo
Audio CodecAudio codec of the recorded streamsStandardNo
Video codecVideo codec of the recorded streamsStandardNo
Platform Call IDUnique conversation identifier received from the recorded platformStandardYes
Silence RatioRatio of silence in the conversationStandardNo
Talkover RatioTalkover ratio of the conversationStandardNo
Longest SilenceLength of the longest silence present in the conversationStandardNo
User ID / Agent IDUser IDStandardYes
From DeviceDevice ID of the calling partyStandardNo
To DeviceDevice ID of the called partyStandardNo
Dialed NumberOriginal dialed numberStandardNo
From IPIP address associated with the calling partyStandardNo
To IPIP address associated with the called partyStandardNoFrom Proxy IPIP address of the proxy server associated with the caller partyStandardNo
To Proxy IPIP address of the proxy server associated with the called partyStandardNo
Source PlatformACRGenesysStandardYes
Conversation TypeVoiceStandardYes
Forward ReasonForward reason for the conversation (e.g. forwarded, transferred, team call, delegated, etc.) StandardNo
Recording failedIndicates if the recording has failed and the metadata was imported during CDR reconciliationStandardNo
Media LengthLength of the media file related to the conversation in hhh:mm:ss formatStandardNo
Media ErrorShows the media processing errors during recordingStandardNo
Voice QualityOverall voice quality check score for the conversationStandardNo
Record TypeStandardStandardYes
2N SourceIn case of duplicate (2N) recording, records are marked as primary or secondaryStandardNo
UDFsAll standard ACR User Defined FieldsACRYes
AgentsCustomer custom metadataACRYes
ServicesCustomer custom metadataACRYes
SkillsCustomer custom metadataACRYes
Other PartiesCustomer custom metadataACRYes
FingerprintCustomer custom metadataACR