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/Lync Call Filter service is able to restore the original transferor if an inbound PSTN call is transferred to another recorded extension with inbound announcement

Tango Networks Mobile Recording integration

New radio platform integration: Zenitel AlphaCom SIP recording

New user location field to store the geographical location of the user, can be automatically populated through Active Directory synchronization

New login/authentication option by providing Active Directory credentials, new permission: Windows Login and Password Authentication Enabled

Timezone of date/time metadata is configurable for conversation export

Ability to define the validity period for label sharing and override the “Unable to Access Conversations Older than”' permission

Updated chart library with HTML5/Javascript chart support, Adobe Flash is no longer required

Group logo feature is removed from the user interface and from reporting

Start DateTime and End DateTime columns GMT variants added to the search list layout displaying timezone for the date/time columns when exporting the search results to xls/csv/pdf

French and Russian language support added

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

HTTP Business API: Search call API now supports multiple "anynum", "anyname" parameters

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

Multiple SNMP trap targets can be defined to support redundant configurations where the system sends traps to all defined targets

Unique alert IDs and alert levels are now reflected in Windows Event Log entries

New user based retention option which can override policy based retention period settings, the field can be populated through Active Directory synchronization

Disposal log which collects summary information for deleted conversations, disabled by default

New storage target: Microsoft Azure Storage using the Azure Storage REST API (in addition to the existing SMB based integration)

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 data import framework to standardize and support existing and new import capabilities, new import source and import policy configurations

New import source: Verba to allow importing recordings from other Verba systems using the new import service framework, web based import option is removed

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

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

Open line ports were closed unintentionally due to unreliable network connections, recording stopped on these open lines

Playback did not handle storage location properly, always considered files to be on the local drive

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

Not Recorded and Incorrect Conversations Details report fixes: - missing property files caused empty lines in the report - SQL error when media length field was 0 - incorrect data was shown due to changes in the database fields

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

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

Increase retention time policy did not get applied on archived conversations

Export to external Verba system failed when the conversation had markers

In some cases, the service user account group membership validation in the AdditionalRoles.msi did not work due to Windows language dependency issues

Never Record setting was not taken into account during import or CDR reconciliation

SfB conference participants were not properly updated in existing records during CDR reconciliation