Verba Release Notes

BT ITS trader voice recording integration: - Certified BT ITS recording solution - IPSI based recording, no TDM support - 2N and N+1 recorder configurations - 2N CTI resiliency deployment option - Compatible with trader voice recording data model (only) - Support for VAD (voice activity detection) and media segmentation for long calls - All types of recording mix layouts are supported - Support for TMS file and/or LDAP based configuration read - Scalable, resilient architecture using the standard Verba Recording Director and Media Recorder configurations - learn more

Migration from Verint v11.x FT platform allowing importing of historical recordings: - Support for archived calls only - Supported archive mediums: SMB folder or EMC Centera (tapes, DVDs or any other removable media is not supported) - Storage targets are automatically created based on the archive configuration in Verint - All Verint v11 file formats and codecs are supported: wave file using G.729, G.723.1 or G.726 - Encrypted calls are not supported - Both back office and front office (trader voice) calls can be imported - Migrated calls are assigned to users defined in Verba based on their associated recorded extensions (Trader ID / Extension or Phone Number / SIP URI)

Summary

Certain calls between Skype for Business and Teams or Azure VoiceMail cannot be recorded

Am I affected?

All Sykpe for Business recording installations are affected where the recorded users can call Teams users or place voicemail messages in Azure VoiceMail.

Impact

Certain Skype for Business calls cannot be recorded when a recorded Skype for Business user is calling a Teams user and one of the participants is outside of the corporate network, or a recorded Skype for Business user is placing an Azure VoiceMail message. This limitation is caused by the new call setup procedure, and specifically in ICE negotiation, introduced in Teams and Azure VoiceMail, which prevents the recording system to redirect and force the calls to the Skype for Business Edge Server where the Media collector can fork the related media streams. Since the system is not able to capture the media streams related to these calls, these calls are not recorded. No alerts are raised unless CDR reconciliation is enabled.

Workaround

Currently there is no workaround other than disabling Teams or Azure VM calling entirely for the recorded users. We are actively working on implementing a new solution which extends the capabilities of the Proxy Server to be able to relay these type of calls too. It requires a major change in the architecture by allowing the Proxy Server to relay calls with external participants through a public interface. It also means that that calls which are currently routed through the Skype for Business Edge Server and forked by the Media Collector Service will be routed through the Proxy Servers that same way as calls with internal or PSTN participants. We are currently targeting July 2020 with the enhanced version of the Proxy Server.

New server security configuration to enable or disable TLS versions: TLS v1, TLS v1.1, TLS v1.2 to restrict secure connections to system components

Openssl library is updated to the latest v1.0.2s

SIP activity watching period in Filter takes into account server local time instead of UTC, also we can define on which days of the week this should be active.

When no Media Recorder is available at session establishment, the service responds with service unavailable (SIP 503 response code), in order to order to force the remote peer to move the session to the next available recorder/trunk

BT ITS dashboard displaying TTP status, CTI status, etc.

New Call Type metadata field to store the call types: Click to Call, Ring Down, Shout Down

All conversation participants are displayed in the player under that conversation details tab

Auto-complete is disabled on forms to avoid the accidental saving of ambiguous data

Allows adjusting media during playback to help users cope with time synchronization issues. Lack of accurate server time synchronization could cause that CDR-only records reference media inaccurately.

New authentication options: - Azure Active Directory (AAD) - Active Directory Federation Service (ADFS) New Identity Providers (IdP) configuration through Roles to enable/disable the new authentication modes in addition to the existing Database Credentials, Integrated Windows Authentication (IWA) and Active Directory (LDAP) options.

The Web Application supports SMB encryption for storage targets where direct playback is available

New Upload Status widget showing the status of upload queues on the recorders

New HTTP Business API call to mark ongoing calls for deletion (finished calls can be deleted too)

Voice Activity Detection (VAD) is now enabled for all trader voice integrations by default

Additional IPv6 support added: - Web based silent monitoring - Desktop agent (screen capture, mute) - Storage and export targets - Import sources

New license usage reports for reporting on historical license usage: - License Usage Details (historical daily usage information with monthly summary for peak usage) - License Usage Summary (historical monthly usage information per tenant)

Support for WAVE files with large metadata in the header added for migration and import from 3rd party platforms

Improved performance for export jobs, in some cases export can work 100% faster than before

SMTP export performance improvements: - Persistent SMTP connections introduced to avoid connection handshake overhead - Base64 encoding performance improvement

Integration with DELL EMC Unity File Level Retention (FLR) storages

Install Kit updates: - Microsoft SQL Server 2017 Express Edition - Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Microsoft ODBC Driver 17 for SQL Server - OpenJDK Java Runtime 11.0.4

Generic import source now supports absolute media file path when defined in the CDR data. It also tries to locate the media files without the folder information.

Imported overlapping trader voice media records (e.g. duplicate recordings) are not filtered out during stitching to avoid echo during playback

Generic Import Source: Verba 8 Instant Message import improvements

Database password was logged as clear text in the Content Server and Media Streamer, and the Import Service log file

Cross-site scripting (XSS) vulnerability fixes for multi tenant environments

Web Server Universal XSS vulnerability resolved for the internal Web Application API

If the directory number started with #, the system could not determine the caller and called parties properly and user assignment did not work properly either

SIP proxy between Cisco Voice Portal (CVP) and CUCM fails when multiple proxies are defined for high availability on the CVP side

Incoming calls to a Response Group or Call Park service did not work when recording announcement was configured

Snom interoperability issues resolved in UCMA B2B calls involving the Verba proxy

The recording announcement got into a loop in case of delegate/team call/simring when the call was coming in through a gateway where SIP refer was enabled

Users could not stop call recording in the Lync/SfB Window Extension in some cases

The Lync/SfB Window Extension didn't check if the call was assigned to the user or not and in case of supervisors, it could start recording for other users.

Skype for Business - Acano calls were recorded with artifacts when Edge Server was involved

The connection between the Recording Director and the Media Recorder was intermittently lost and alerts were raised due to improper handling of messages in very rare cases

CDR records were not created after call segmentation when recording was configured with Remote Media Recorder(s). In this case, the Recording Director is connected to a Media Recorder running on another server. Media records were still created, but corresponding CDR records were not. In case of TPO based recording, the recordings could not be found when searching by users. This error generates a Call Processing alert: cannot update/terminate recording.

If Voice Activity Detection (VAD) is enabled for stereo recording, media was not recorded and start time became invalid leading to SQL errors

Invalid LDAP query was generated when just a single Recorder Cluster ID was configured

Memory leak in checking the BT Heartbeat and Directory Service status on Media Recorder servers

Physically disconnected BT ITS turret's media channels carry 0xFF which decoded as A-law which triggered constant Voice Activity Detection (VAD) which started media recording

IPC Unigy CDR event feed might be stuck after network connection issues, leading to loss of CDR records

IPC Unigy N+1 Recording Director redundancy created CDR records on both active/passive Recording Director servers

Cloud9 Media Foundation alert was falsely triggered while the feature was installed on the server

Screen and voice recording multiplexer generated invalid VF files

Daily Active Directory synchronization did not run in case it was disabled on one of the Media Repository/Application Servers, because this server logged that AD synchronization was executed even though it was disabled.

Send Authorization Requests Permission did not give access for the Search menu when the user had no access to conversations otherwise

The Active Directory synchronization did not invalidate such users in Verba whose login name was modified in the AD

Deleting the recording rule while it was still assigned to an extension caused an error

If a marker is added without selecting a timeframe in the player, then the marker is created with NaN:NaN-NaN:NaN interval

The delete button was visible for conversation records under retention and error was shown when the user attempted to delete the record. The button is no longer displayed for records under retention.

Duration filter did not work when the minute was greater than 59

Cancel filter for related media search issue: canceling a search for the related media records always jumped back to page 1 instead of the last visited page

The BT ITS Source Platform was not available in the Search and Data Management Policy features

Saved query search audit log entry was logged as different event type for each saved entry and did not contain the name of the saved query

Azure AD secret was visible on the Active Directory synchronization configuration page

Date values on the dashboard were displayed in the wrong timezone

Dashboard snapshots did not work due to a missing configuration file on the server

Communication Policies' Regex field did not support items longer than 256 characters

The Lync/SfB announcement did not work when the domain name contained a mix of lower case and capital letters

REST import API did not work for SMS data when the SMS text was delivered as a CDR field instead of a file

Provisioning Web Service CreateExtension threw NullPointerException when the requester user did not belong to the Reference Environment

The system did not send all recorded extensions to the servers after Active Directory synchronization in very rare cases

Changing the logging properties (Maximum Log File Size (bytes), Maximum Number of Log Files) of the Verba Unified Call Recorder Service, the Media Collector & Proxy Service, the SMS Recorder Service, the Communication Policy Server Service, the Cisco Announcement Service, the Centile Connector Service, the MediaSense Connector Service, the Screen Capture Service did not trigger service restart and were not applied.

Database upgrade script threw an error when creating Roles in a Multi-Tenant environment

Media stitching: if media is to be mixed from a media file starting from more than the 7.6 minutes offset, the stitching was incorrect

Automatic Gain Control (AGC), which maintains the output volume level of the audio signals for the voice recordings, is now configurable separately for each integration supported by the Unified Call Recorder service

System Monitor might refer the server by hostname instead of FQDN in alerts

Database connectivity check did not work after connection failures (services can send alerts on database connection issues)

Non-UTF8 characters in the metadata fields, received from the signaling protocols, were not stored properly

When SFTP server did not return authentication mode, the service could crash

Custom port settings were ignored for S3 Compatible storage targets

Bloomberg Vault voice export generated invalid recSiteId values which resulted in failed exports

Voice Quality Check configured total score alert threshold was ignored and the default value (75%) was used only

Deduplication, encryption and signing data management policies were not automatically filtering out records under retention and raised errors during policy execution. The system does not allow executing these policies on records under retention.

If multiple Media Repositories are available in the home Verba instance (cluster), shared recorders did not terminate ongoing CDRs in some cases

Do not show upload policies in "Execute Only After Another Policy Executed" because the system was unable to support this criteria

The installer did not insert the value of the SQL failover partner into the registry

Microsoft ODBC Driver 17 could not be selected in the installer and in the server configuration

Desktop Recorder/Agent installer opens the Windows Certificate Store when browsing server certificates

Cisco Reconciliation: when a call was not established but the duration was greater than 0, the system considered the call to be imported and disregard the 'Do not import not answered calls' option

Reconciliation re-check did not work for Cisco calls

Import service might crash at termination/shutdown

CSV column header fields were not case sensitive in generic import

Import policy scheduler was not disabled for API based import sources and could interrupt API calls: Cloud 9, REST API and Verint

REST Import API did not handle 'fileshare' modality correctly