Verba Release Notes

New encryption and integrity protection with Windows Certificate Store integration, data retention policy based configuration, support for all types of recordings, encrypt or sign only options, etc.

Support for SfB/Lync persistent chat room recording

New hierarchical group synchronization feature added to allow synchronizing the active directiry organizational units, security groups based on the memberOf attribute.

New SFTP based storage target is implemented to support uploading recordings to standard SFTP servers from Verba. - learn more

Summary

There is one way audio in recordings after SIP re-invites when media bypass is active. The SfB/Lync Filter service does not recognize the SIP re-invite messages properly when media bypass is active, and the call is only partially rerouted through the proxy. This results in one way audio in the recordings after the first re-invite. The re-invite period is controlled by the session timer configured for the connection between the gateway and the SfB/Lync system.

Am I affected?

All 7.0 and later SfB/Lync recording deployments using proxy based recording are affected where media bypass is configured with SIP session timer.

Impact

The Verba SfB/Lync Filter does not recognize SIP re-invite messages properly when media bypass is active and the call is only partially rerouted through the proxy. This results in one way audio in the recordings after the first re-invite. The re-invite period is controlled by the session timer configured for the connection between the gateway and the SfB/Lync system. When the default SIP session timer setting (1800s) is used, the first re-invite is sent after 15 minutes. Thus all inbound or outbound calls longer than 15 minutes are affected. Prior to the re-invite, recordings contain both directions.

Workaround

Disabling the session timer or media bypass completely resolves the issue

Summary

Siren7 decoding problem is causing garbled decoding of voice in certain cases.

Am I affected?

All Lync/SfB recording deployments are affected.

Impact

- Intermittently causes garbled voice recording when Siren7 voice codec is used for the call - The recording quality is varying for the garbled recordings, from light impact to severe degradation of quality - Siren7 voice codec is mainly used for Lync 2010 Windows endpoints and Skype for Business 2015 IOS/Android devices when network is degraded - Siren7 voice codec is also used for Lync 2010/2013 and Skype for Business 2015 meetings during poor network conditions

Workaround

- currently there are no known workarounds

Summary

Lync / Skype for Business IM conversations might not be recorded after recording and processing 10,000 RTF based messages.

Am I affected?

All Lync / Skype for Business IM recording deployments are affected. This issue affects IM conversations which are using the RTF format. Lync 2013 or newer desktop clients are using the RTF format for P2P IM conversation when both participants are using a desktop client. Conferences, mobile, and consumer Skype conversations are not affected by this issue.

Impact

- When the instant message is transmitted using the RTF format, the Verba Lync / SfB IM Filter application (on the FE servers) can use all available Window handles due to the improper deallocation of the RTF parser. - The service stops processing RTF based instant messages after approx. 10,000 RTF messages (after all Windows handles are consumed) - No alert or notification sent when the issue occurs

Workaround

- The RTF message format can be disabled by a client policy, for more information see https://docs.microsoft.com/en-us/powershell/module/skype/set-csclientpolicy, DisableRTFIM

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.2e

Cisco IP Phone Service session timeout raised to 60 minutes, but not allowing duplicate sessions from the same client IP address.

Improved handling of keep alive messages in the SfB/Lync Filter component by using high resolution timers.

Multiple CM / ESS servers can be configured to support CM-ESS failover.

New feature in screen capturing to allow hiding configured windows or control objects on the desktop screen. It can also trigger mute for audio recording.

Every time SMTP settings are changed on the MR, a warning message is displayed until a verification email is sent to the user.

Failed logon attempts are stored in the Audit Log

Active directory synchronization commits transactions after each imported user, so that the dummy SQL Server batch-abortion will not cause issues with multiple users.

When creating a new environment, roles are created based on the roles in the Reference Environment.

Wait after the execution of an AD sync profile so that recently deactivated users will always be considered as inactive (by the next profile).

New configuration values are added to existing configuration templates (even if not default) during an upgrade.

On-the-fly MP4 video encoding during recording

VMF media processing framework was limited to support only 3 audio and video mixing layout. Now any number of streams are supported. Video layout is set dynamically according to current number of active main, presentation and panoramic videos. Lync panoramic video was shown twice in the recording of sender in case of conference call (MCU sent back the same panoramic stream, now this is filtered and not shown).

New alerts are available to monitor SIP trunk state changes.

Memory alert template has been changed to show the list of processes too

Local SNMP port is configurable now. The default port 162 might interfeere with other SNMP agents on the server.

Data retention policies now support operations on IM conversation when transcript files are not generated, the conversation is only stored in the database.

The default CDR Importer Call Length Threshold has been increased from 0 to 5 sec.

Small memory leak caused by OpenSSL as it allocates an error stack for each thread calling any OpenSSL function but does not deallocate it.

Relay module terminated the session if only the callee received the final error or redirecting response (3xx-6xx).

Deadlock occurred when a session operation didn't succeed and another thread tried to open the same session.

Fixed file naming pattern, missing underscore caused storage operation failure.

In case of SfB/Lync double relaying only one stream could be matched with a recording session after ICE finalization and so recorded (stream going to the endpoint was recorded but not the one going to next proxy hop).

When a call was answered by multiple parties and one terminated the call with BYE before media started flowing from any endpoint, recording was not started.

Call ringing state timeout increased from 2 to 5 mins and is made configurable via registry

Memory leak has been found and fixed when the recording server did not delete terminated calls from the internal, in memory object in certain cases.

The service could not move the .im transcript files to the storage folder if the folder did not exist.

Recording may stopped if a non-answered incoming call arrived to the recorded station during another active call.

Recordings could not be deleted on the user interface when the underlying storage did not support file rename. Data retention policies were not affected.

Special characters were not searchable in metadata and markers.

The lack of a primary group membership may caused a user to not be synchronized by AD Sync.

In multi-tenant mode, group modification may threw an exception.

When participant set reached or exceeded 20 items the later additions of the items failed.

Agent View is now working with cloud mode. Minor fixes on the Agent View GUI.

Last search criteria in QM search is now deleted if the SQL query fails.

In QA / Evaluations menu when the user filtered for Score, and there were many results, then some of the matching records were not displayed.

In case of SfB/Lync outbound announcement, announcement legs were imported as failed records

GetExtension method in the provisioning API did not work when only the active extensions were queried.

In the Provisioning API, the Manager attribute was set for the group membership when "null" was data received

If SfB/Lync uses SQL named instances, due to an error in the way an internal file was created, the CDR reconciliation process does not retrieve any calls and it did not send alert or notification.

The system monitor service did not monitor the Verba Lync/SfB IM Filter service due to missing configuration.

The system monitoring wrote duplicate event entries into the Windows Event Log when the email configuration was not correct.

If scheduled archiving policy was executed then the related background task entry was not finalized.

When SQL Authentication is disabled on the SQL Server and Windows Authentication is configured in the installer, the installation failed when the Windows user has no right to create a user on the SQL Server.

Device type is imported from SfB/Lync CDR tables, call parking service calls (MoH) is now skipped (as the system does not record that part).