Verba Release Notes

Lync/SfB contact list blocking feature which can prohibit a user to add a blocked contact to the address book or to retrieve/list blocked contacts from the central directory

New Cisco recording announcement service supporting both inbound (existing capability) and outbound call scenarios using External Call Control Profiles and CURRI

CyberTwice eRecorder HD recorded conversation import integration, a new type of storage target is also available to provide media playback/download capabilities when the media file is not imported

Cloud9 C9 Trader integration to allow importing recorded conversations sent by the soft-turrets

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.

OpenSSL library is updated to the latest v1.0.2l

Enhanced routing rules can be defined for the SIP proxy, routing rules can be based on source IP address, source URI, destination URI

Support for shared server configurations using Cisco network based recording

SfB conference hosts can now be identified in conference participant information

Support for Huawei UC platforms using the dial-in recorder based integration

SRTP and TLS support for the dial-in recorder

Search hit highlight for instant messaging conversations and speech transcriptions to show search hits with contextual information

Data management events are listed under Conversation Audit Log on the Conversation Detail screen

Phone number/address masking capability to hide sensitive information, such as customer phone numbers, on the search screen

Observer Group and Observer User added to the Active Directory synchronization, Bulk User Update and Bulk User Import features

Awareness notification on the number of affected records for data management policies (e.g. deletion)

Ability to add up to 10 custom user fields (previously it was 5)

Verba servers can be deactivated to disable features such as applying recording rules, configuration, etc.

New menu structure to reflect recent changes and provide better usability with simpler and cleaner structure

Audit Log report displays conversation export filter criteria

On-Demand Conversations Buffer page is now using the standard search page

Advanced Search: The following fields will support "Defined" and "Undefined" operators from now on: Storage Folder, Encryption, Signature, Forward Reason

New Agents Scoring Classifications report showing scorecard classification summary information grouped by agents and projects

New Roles, Permissions and Users report showing permission configuration for roles with listing users with the given role

New N/A option for multiple choice questions, allowing to select an answer, which does not affect the score value

Invalidated agents are listed at the end of the list and marked with (*) when creating a project

The SfB/Lync Announcement Service can selectively turn off the notification for team calls. If the original callee is not recorded then there won't be an announcement during the call even if someone is recorded from the callee's group. This feature is turned off by default.

New HTTP Business API call: GetLocations to retrieve the list of Verba servers

Merge capability for Active Directory synchronization profiles allowing a single user to be synced via multiple profiles by merging/combining the configuration (extensions, groups, roles) from each matching profile

Data source configuration allowing to select one or more Recorded Platforms and/or Import Sources for recorded extensions/addresses, so that certain numbers/addresses are recorded only on selected platforms

Optimized storage format for instant message conversations in the database to reduce storage requirements

New audio/voice codec file formats available for recorders: - PCM A-Law 8KHz - PCM U-Law 8KHz - MSADPCM 8KHz - Speex 8KHz - Speex VAD 8KHz

New Notification alert level, data management policies now send alerts with the new notification level for policy execution results

Log masking capability to filter out sensitive information from service log files such as customer phone numbers

Active Directory based authentication and authorization option for Hitachi Content Platform

Transcoding related settings are no longer directly available under Speech Indexing policies, separate transcoding policies can be defined

Transcription export capabilities: - [Transcription] placeholder for SMTP targets - VTR and native transcription file export for file based export targets

New Powershell Deployment Toolkit cmdlets for certificate generation: New-VerbaCertificateRequest, New-VerbaSSLCertificate, New-VerbaCACertificate, New-VerbaServerCertificate

New version number format: major_version.minor_version.service_release_version.build_number (earlier service release versions were only reflected in build numbers)

New installer parameter SKIPREGISTRATIONCHECK, to skip the server registration check and force the server name registration format with the SERVERNAMEFORMAT parameter, where 0 = NETBIOS, 1 = FQDN

If Skype for Business QoE report is available then the RTP counters are now stored in the Verba database. QoE query has been optimized to run faster.

New service configuration settings for Cisco CDR reconciliation to filter based on specific Cisco CDR fields (e.g. device ID and IP)

New import sources: SfB/Lync and Cisco CDR to allow CDR import and reconciliation using the new import framework, previous server/service level configuration is removed

In case of several (100s) large SIP NOTIFY messages (e.g. large contact list), the Proxy service did not respond in time causing Filter and Media Collector timeouts which led to increased SIP processing queues on the SfB/Lync Front-End servers. SIP NOTIFY message processing was enabled inadvertently in certain v8.9 builds only.

An application deadlock could occur in The Cisco JTAPI Service and SQL INSERTS could stop. A restart of the service was required to continue.

Cisco JTAPI Controlled Recording "Start" record did not show the correct MAC Address after a transfer

Mobile Cisco Jabber app could not parse HTML based notification only plain text

Group chat recording notification didn't work for Cisco IM&P 11.5 or later

SfB/Lync call setup fails when an outbound announcement is configured and the user initiates hand-off transfer

If both the caller and the callee had the same number/URI in a recorded session, the conversation was recorded twice

Conversation blocking did not work in the Lync/SfB Call Filter service in case of recorder or media collector failure

CPU usage was increased and log files filled up quickly for the Verba SfB/Lync Call Filter Service on the Front-End Servers when the Verba SfB/Lync Announcement Service was shut down. The issue only affects deployments where the Enable Advanced API Security setting is enabled.

The SfB/Lync IM Filter Service could not add the recording notification message to the message if the endpoint was a UCMA endpoint and it used the plain text message format

High CPU and memory usage when the Verba SfB/Lync IM Recorder Service could not connect to the database for a long time (days)

Recorded voice/video conversations could stuck in ongoing state in the database, because the end time of the recordings is not valid. This issue is related to deployments where the Recording Director and the Media Recorder roles are installed separately, and effects all call flows. A tool is available to update both database and CDR XML with the correct end time information for effected recordings.

IPTrade turret playback: shared line calls placed by other agents were listed

If screen capturing was paused by the user and before the call-end it was not resumed then the state was held for the next call as well and recording was started in paused state

Configuration was not updated when user language was changed

Clicking on 'Find and List Conversation Exports' link led to dead page (when coming from the Background Tasks list)

When creating a new metadata template with an already existing name, the application did not add it, and no error was provided

The Date field on the Group membership history page did not sort correctly

Player showed WMV when MP4 transcoding finished

Error Message was "null" when a call could not be deleted because of the retention rules

New Bulk User Update could not be saved when some update fields were configured

Checkboxes were disabled on the Conversation Export page when the target was SFTP

Marked audio segment download did not work

Agents Evaluation Details, Agents Evaluation Summary, Agents Scoring Classifications, Scorecard Calibration Details reports were showing invalid classification labels after updating the classification settings

Quality Assurance dashboard widgets did not work when text type questions were used on forms

Participants containing special characters were not handled properly, causing errors in rule processing

3rd party notifications were sent only to the first e-mail address

N/A value was not handled correctly when calculating available max point for "Multi Choice Question" on the scoring page

The SfB/Lync Announcement Service ignored the maintenance mode

Search Calls API did not work with metadata filters

Generating server certificates could fail on Windows Server 2008R2

Encrypted database connection could not be configured for the Web Application

If a video call did not contain video or there was a big audio or video gap, MP4 transcoding stalled

Alerts containing '&' character were not inserted into the database

General server alerts (memory usage, disk capacity, service failures) were sent with Critical level instead of Error alert level

Total/processed counter was incorrect in the policy execution report notification alert

SMB storage access stopped working after a while when custom credentials were configured to authorize access to SMB storage folders

Encrypt and Sign policy: if the files have not yet been uploaded and the policy run on these conversations then despite the missing files the processing was considered successful

Download, playback, move and export functions did not work using the Azure REST API due to issues with case sensitivity

Hitachi Content Platform upload failed with "Upload from/to the same location is not allowed" error message

Export to Hitachi Content Platform, EMC Centera, IBM TSM, Amazon S3, Azure Storage, EMC ECS did not follow the YYYY/MM/DD folder structure

SQL script execution failed during installation due to timeout

Windows user account group membership query failed

The Lync / Skype for Business CDR reconciliation process might not process all CDRs when there is at least one missing CDR found. The system uses a batch based processing for each 100 recorded extension. Due to a software bug, the application applies the start datetime of the last missing CDR as the start datetime for the query interval, instead of the original start datetime defined by the process scheduler (start datetime of the last processed call in the previous reconciliation cycle). It could produce false reports for CDR reconciliation, since the process will not query the CDR database with the proper date interval. For instance if the process finds a missing CDR in the 2nd batch, the 3rd and all consecutive batches will use the start datetime of the missing CDR from the 2nd batch, instead of the original query interval.

New configuration options for SfB/Lync CDR reconciliation: P2P, PSTN and conference calls can be switched on/off to adopt to the capabilities of recording method being used