2.23.0

Contact center integration BusinessLogicWebhookConfig now supports OAuth 2.0 JWT profile.

Added a support of diagnostics codes when errors occur. The diagnostics code gives you meaningful and enough details in the errors to better understand and mitigate the issue.

Note: This is a beta feature.

The Gatekeeper web portal now displays diagnostics codes when errors occur. The diagnostics code has been inserted into Elastisearch (ES) at session level and displays in the web portal at the session and factor levels.

Note: This is a beta feature.

The Gatekeeper web portal now shows localized unknown phone number when the phone number is configured to be unknown.

The Gatekeeper web portal now shows a localized unknown phone number when the phone number is configured to be unknown from the web agent console. In addition, the validation regular expression (regex) for the phone number has been updated to include the following characters:

• at sign (@)
• colon (:)
• semi-colon (;)
• forward slash (/)
• question mark (?)
• ampersand (&)
• dollar ($)
• comma (,)
• exclamation mark (!)
• tilde (~)
• apostrophe (')
• pipe (|)

New public API named get_voiceprint_profiles_status_url has been added to pull all persons and voiceprints status from the scope.

Note: This is a beta feature.

To keep tracking of who accesses the audio, new audit events have been added in the WEB_APP_EVENT:

• webAppListenToAudioEvent
• webAppDownloadAudioEvent

The existing auditing was refactored:

• For listenToAudio instead of AUDIO_SEGMENT_ID, it now shows MEDIA_ID.
• Webbff audit enum is updated to have UNSPECIFIED at 0, and refactored naming to answer gRPC uniqueness.

The validation regular expression (regex) for the phone number has been updated to include the following characters:

• at sign (@)
• colon (:)
• semi-colon (;)
• forward slash (/)
• question mark (?)
• ampersand (&)
• dollar ($)
• comma (,)
• exclamation mark (!)
• tilde (~)
• apostrophe (')
• pipe (|)

CTI event message has been updated to have a new optional field consumed_timestamp. It contains the date and time when the event was consumed by the service.

Issue Description	Issue ID
Web Agent Console displays “Enrolling” instead of “Capturing Audio” when the person was opted in and didn’t have a voice print.	XSUPPORT-15854
Unable to search persons by their first or last names in the Gatekeeper web portal.	XSUPPORT-15976
Missing linkage between fraudster enrolled from the Cluster View and Engagement where the fraud took place.	XSUPPORT-16151
The ‘Add to print’ feature for an existing person throws authorization exception for clustering results.	1545970
Issue with ‘Add to print’ feature when enroll voiceprint status isn’t OK.	1556611
Audit extractor service export APIs lacks support for text events. The extract records with person information decrypted has empty values for the context (for any record type).	1595321

In the web agent console miniature view, language prompts aren’t localized to match the miniature view.

In web agent console, some Dutch prompts aren’t localized, and they default to the English locale.

Any NVSL frameworks at 16 kHz don’t work, as Gatekeeper doesn’t support 16 kHz audio yet:

• FACTORY_TI_16kHz_10
• FACTORY_TI_16kHz_9
• FACTORY_TI_16kHz_8_2
• FACTORY_TI_16kHz_8
• FACTORY_TI_16kHz_7_2

Rarely it may happen that a post call session is isolated in a separate engagement and not aggregated with the other live sessions.

DEMO and Bootstrap risk engine calibration models might not work properly and they show poor accuracy. Use these models only for non-production use.

Gatekeeper Web administrator applications don’t officially support Private Browsing Mode. Without them, the Console may display an authorization error. This isn’t required for agents authorized for a single scope.

The autocomplete for first name and last name doesn’t work when using special character, such as ‘@’ or ‘_’.

Web Admin Portal has a time zone selection issue related to browser updates.

Kibana Dashboard – The Generate PDF feature doesn’t work when Optimize for Printing is enabled.

A Clustering or Backwards Search action may time out due to the memory required for media collection exceeding configured limits. This is likely due to a collected engagement containing more than an expected number of sessions but could have another cause.

Clustering and Backward Search have the following limitations:

• No estimations available for media collection.
• Clustering and Backwards Search require manual scaling.

Audio streaming for transcription is limited to one realtime (this value isn’t configurable).

For Stereo audio, the redacted overlay interval applies on both channels in the audio viewer.

Realtime redaction isn’t supported when Transcribe API is used.