2.33.0

For the IVR BOT service, the maximum length of the recording identifier in the StartIVRSession API Request has been increased from 64 to 512 characters.

Issue Description	Issue ID
When a WAV file is uploaded, the duration RIFF header is erroneous.	1407138
In the web agent console, fraud decision isn’t transferred to agent 2 screen, when the event from the server has no previous session decision set.	1997461
When a caller opts out and the call is transferred, the caller’s information doesn’t display when the agent clicks Opt-In in the web agent console.	2114934
When call is transferred, the fraud session decision isn’t displayed when the voice print is locked or if the person opted out.	2168304
Unable to search phone numbers using the quicksearch by phone feature.	2199235
On the web agent console UI, the French localization is missing for the Login with Entra ID text.	2202473
When there is a session with excluded factor, the GetSessionDecision API doesn’t return the first_excluded_factor_details value.	2207668
User is unable to save the data on the Edit person app data pop-up dialog due to validation errors on the First Name and Last Name fields, even when valid data is entered.	2208080
On the web agent console UI, timestamp is incorrectly displayed for fraud in a group flow.	2208609
API latency in all regions affected due to poor authentication mechanism to resources.	2212225
Issue with Data-Loader to handle errors and perform retries on zip files closure.	2216406
In DataQueryManager, the PIT timeout isn’t enough to allow long lasting query to be executed and isn’t configurable.	2220879
For the IVR BOT service, the StartIVRSession API returns an INVALID_REQUEST error indicating that the ‘recording_id’ string exceeds the maximum allowed length of 64 characters.	2226711

If the fraudster was deleted but was still in the cache, it’s possible that the export services might still show it up as empty string. However, when the context-manager tries to get gk_fraudster_id by gk_voiceprint_profile_id, it gets NOT_FOUND as the voiceprint was deleted.

In the Gatekeeper web admin portal, when you add comma to the autocomplete in the search box, it’s used as a separator (like space), and search of only a comma returns no results.

When Contact Center Flow version is set to v2 and Detect Fraudsters is enabled on enroll, the Detect Fraudster widget doesn’t show a pass label.

WAV header duration value is unreliable when fetching media through GetMedia API, GetMediaUnmasked API, or through /media URL obtained from the PublishMedia or PublishUnmaskedMedia API.

Use duration provided by the GetMediaInfo API instead of relying on the duration of the WAV header.

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 Backward 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 Backward 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.