2.8.0

Gatekeeper CLI offers the following new command to update all Kibana dashboards at once, for all scopes:

update-all-kibana-dashboard

New scope-level configuration parameters for post call activities are added to the Contact Center Post Call tab:

• PostCallWatchlist
• PostCallWatchlistVoiceprintTag
• PostCallAudioSpoofingDetectionOnEnroll
• PostCallAudioSpoofingDetectionOnLockedOrOptedOut
• PostCallAudioSpoofingDetectionOnMatch
• PostCallAudioSpoofingDetectionOnMismatch
• PostCallAudioSpoofingDetectionOnOptingOut
• PostCallAudioSpoofingDetectionOnRiskySession
• PostCallAudioSpoofingDetectionOnSuspicious

Note: PostCallWatchlist and PostCallWatchlistVoiceprintTag configuration parameters support using a different watchlist for post call activities. If the values of these configuration parameters are set as Empty, the related runtime configuration is used for the post call too.

New scope-level configuration parameters for audio spoofing are added to the Contact Center tab:

• PerformAudioSpoofingDetectionOnEnroll
• PerformAudioSpoofingDetectionOnLocked
• PerformAudioSpoofingDetectionOnMatch
• PerformAudioSpoofingDetectionOnOptedOut
• PerformAudioSpoofingDetectionOnOptingOut
• PerformAudioSpoofingUsingMediaSegment

New scope-level configuration parameter for contact center are added to the Contact Center tab:

• ExternalPersonIdCtiEventTypes

New operational-level configuration parameters for post call activities are added to the Post Call tab:

• PostCallDetectChannelPlaybackOnOrphanEnabled
• PostCallDetectSyntheticSpeechOnOrphanEnabled

The following export data fields related to call duration are renamed:

Old name	New name
call_duration	call_handle_time
call_duration_until_authentication	time_to_authenticate_from_call_start
call_duration_until_authentication_from_person_id_provided	time_to_authenticate_from_person_id
call_duration_until_enrollment	time_to_enroll_from_call_start

• Support added for the audio spoofing detection based on additional events, such as:
  • On Enrolled
  • On Locked
  • On Match
  • On Opted Out
  • On Opting Out
• Support added for using the media segment ID related to the audio spoofing processing. Default is to reuse existing processed audio ID from previous biometric factor.
• Support added for the post call related to the audio spoofing detection based on events, such as:
  • On Enroll
  • On Locked or Opted Out
  • On Match
  • On Mismatch
  • On Opting Out
  • On Risky Session
  • On Suspicious

Custom webhook headers are supported as part of the webhook configuration. This is an optional feature. Use httpHeaders as array where each entry has:

• name: A property name.
• value: A static value.
• sessionVariableKey: A value based on session variable, such as ctiCallIId.

If a person ID is identified based on the CTI event field, Gatekeeper accepts the new external person ID value only for selected call event types, such as to avoid processing a person ID as part of the End Call event type.

Improved security measures to enhance system protection against potential exploits.

Several operations, such as Enroll or Train, are removed from the WebUserReadOnly factory role.

The left and top navigation bars in the Gatekeeper web portal UI are updated.

The scope-level configuration parameters in the Contact Center tab are split into the following new tabs:

• Contact Center
• Contact Center Integration
• Contact Center Post Call

Login is now supported directly through URL query parameters, such as wac_login_tenant, wac_login_test, in addition to the current mode where the parameters are included in the URL path.

The Amazon Connect Contact Control Panel (CCP) Connector transforms Amazon Connect specific contact or agent events into Media Manager call or agent events. It then sends those call or agent events to Media Manager located in the Gatekeeper cloud. For more information, see the Amazon Connect CCP Connector SOG documentation.

The RecordingIdentifierKey scope-level configuration parameter in Gatekeeper can now be left empty for Amazon Connect deployments as the recordingId parameter is now present in CALL_STARTED events. This feature is particularly convenient when a Gatekeeper tenant has a single scope with multiple Media Manager realms or platforms.

The RecordingIdentifierKey scope-level configuration parameter in Gatekeeper can now be left empty for Five9 deployments as the recordingId parameter is now present in CALL_STARTED events. This feature is particularly convenient when a Gatekeeper tenant has a single scope with multiple Media Manager realms or platforms.

The Web Agent Console now correctly displays the progress in the progress bar when only one checkpoint is configured.

The examples in the REST API documentation now use URL query parameters instead of including the parameters in the request’s body.

Issue Description	Issue ID
Export Data doesn’t support exporting the custom session data.	XSUPPORT-10842
ProcessText returns an error when more than 180 seconds of audio are used for the conversation print processing.	XSUPPORT-12514
Incorrect URLs with empty curly brackets for REST APIs.	XSUPPORT-12434
An issue between coordinators and risk engine results in errors unable to propagate.	XBIOMETRICS-32920
The Amazon CCP login pop-up doesn’t appear if initially closed without completing the authentication process.	XCONNECTORS-3630
The recording fails to restart after a conference call.	XCONNECTORS-925
Lack of authentication for Media Manager Media URLs	XBIOMETRICS-32100

Enabling spoofing detection on orphan calls is considered beta.

Avoid the scientific notation, such as 1.15785E7, for long numbers in exported CSV.

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

Gatekeeper supports NVSL 10 engine but:

• NVSL 10 can’t be used with the factory framework of the Risk engine 1.4 version.
• NVSL 10 frameworks are only used as baseline for the creation of new custom calibration model.

Deviceprint Public APIs are considered beta.

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

Neustar Factor integrated to the risk engine is considered beta.

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 Session Person data (session grid) displays the person from the verify or identify voiceprint (not from convoprint), only if there is a match in those factors.

Possible misalignment between the text segment and the convoprint quality check.

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.

NVSL TI_9 and TD_9 frameworks aren’t supported by the following bootstrap NRSL models:

• FACTORY_TI_RISK_ENGINE_BOOTSTRAP_1_2
• FACTORY_TD_RISK_ENGINE_BOOTSTRAP_1_2
• FACTORY_TI_RISK_ENGINE_DEMO_1_2
• FACTORY_TD_RISK_ENGINE_DEMO_1_2

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.

The following services require manual horizontal scaling:

• data-query-manager
• voiceprint-coordinator
• fraud-analytics-manager
• biometrics-supervisor
• transcription-coordinator

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.