2.18.0

Webhook service OAuth2 authentication is now supported based on client ID and secret.

A new operation Operational.CheckWatchlistConsistency is now available to validate a watchlist.

Caller ID watchlist assesses the risk of a call based on the caller ID by looking it up in a watchlist of known fraudulent caller IDs.

A new UI button to check the watchlist consistency has been added.

A privacy statement link has been added to the login and waiting for next call screens in the web agent console.

Web agent console supports custom text for decisions at call level, which is controlled by webhook or light rules based on the Display Message operation.

A new public API CheckWatchlistConsistency API has been added for gRPC and REST.

This API checks that a given watchlist includes voiceprints that are all compatible with each other, with respect to a selected configuration and a required calibration model.

After a migration of voiceprints to a new calibration model and to prevent the service interruption at runtime, this API is needed to check that the fraudsters included in the runtime watchlist have been all migrated properly and are all consistent with the new calibration model.

Note: This is a beta feature.

Issue Description	Issue ID
Download Engagements report is missing Initial Voiceprint Enroll Status and Final Voiceprint Enroll Status.	XSUPPORT-14211
Inconsistent text on the confirmation dialog in the Gatekeeper web portal.	XSUPPORT-14240
GUI calls GetClusteringJobDetails with a null or invalid ID.	XBIOMETRICS-27897
Data Transformer - In Media Event, there is an issue with updating call parties and redacted intervals.	XBIOMETRICS-30854
User enters absurd dates in the engagement filter and still results are displayed.	XBIOMETRICS-31310
Audio creation timestamp isn’t displayed and populated on the Engagement page in the sessions for enrollment.	XBIOMETRICS-31670
Downloaded CSV from the Engagement page isn’t formatted properly.	XBIOMETRICS-31859
No label displayed after entering data in the Restart Counter, Business Type, and Data Center fields in the engagement filters.	XBIOMETRICS-33622
There is no indicator if a transcript is used to in a convoprint to train it.	XBIOMETRICS-34714
Text creation timestamp isn’t displayed and populated on the Engagement page in the sessions for enrollment.	XBIOMETRICS-34723
For datashare receiver, when failing to train, the TrainReason isn’t shown on the Data Share - Receiving UI.	XBIOMETRICS-34726
The search role operation isn’t working in the Role tab on the Authorization page.	XBIOMETRICS-36771
In AudioManager or ContextManager when enrolling multiple prints with same media ID, the DeleteMediaSegment API succeeds even when permission is denied.	XBIOMETRICS-37403

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.

Convoprint L2 Streaming functions for Business Logic Layer (BLL), Call Session Manager (CSM), and Web Agent Console (WAC) are considered beta.

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.