Verba 7.0 Update 2 Release Notes (build 7.0.4390.0)

Verba Release Notes



Current Release


   7.0 Update 1
   7.0 Update 2
   7.0 Update 3
   7.0 Update 4
   7.0 Update 5
   7.0 Update 6

Build Search

Find your build:

(e.g. 7.0.4548.0)

Verba 7.0 Update 2 Release Notes (build 7.0.4390.0)

This document lists new features and fixes released in Verba 7.0 Update 2 Release Notes (build 7.0.4390.0).

Release highlights

RI-003398Recording - Passive
Adhoc (start/stop) recording for passive recording
RI-003366Recording - Cisco
Recording redundancy for SIPRec based Cisco gateway recording
RI-004161Recording - Lync/SfB
Integration of SIP/RTP remote capture and proxy services (WinPCAP based remote capture, standard RTP proxy and Lync/SIP controlled RTP proxy)

Known Critical Issues

First Affected
Resolved in 8.3.4675.0
After x weeks of operation recordings are terminated prematurely due to timeout on passive, SPAN-based direct NIC capturing solutions with specific HW/NIC/Virtual env conditions. In some conditions NIC/winpcap and OS clock is out of sync and over time (more weeks) the clock drift can accumulate and reach call timeout threshold.

- only impacts Passive SPAN-port based recording - does NOT affect Media Collector source and remote capturing on Media Collector (most Lync recording deployments) - the issue happens on rare combinations of specific platforms depending on NIC, NIC driver and virtualization environment (cases found in virtualized, but SPAN port based systems) - it might happen several weeks after recorder service has been up and running (depends on hw) - recording sessions terminated prematurely (before call ends) with end cause: call timeout (calls are only partially recorded)

- Set higher call inactivity/timeout threshold (def 180 sec -> 600 sec) - Restart recorder service every weekend
Resolved in 8.3.4668.0
Call length mismatch due to silence suppression If there is no RTP sent in any direction since both side are on mute/do not talk Lync stops sending RTP (or at call start does not start sending RTP). These gaps between voice parts (where RTP is sent) are filled, but the gap (if there is any) between call start - first voice RTP and last voice RTP - call end cannot filled.

- this issue leads to losing silent segments, but not actual voice recording - it leads to time difference between presented recording time and actual recording time of media - mostly conference calls are affected, especially the first participant who is on mute until others arrive

- there are currently no known workarounds
Resolved in 8.3.4669.0
After updating to Skype for Business clients, P2P calls are dropped when proxy server based recording is used.

- P2P calls dropped when the new Skype for Business client is used - effects all P2P calls - all installations are effected where proxy server based recording is used

- Currently there are no known workarounds
Resolved in 8.3.4693.0
Using a very large AD might cause timeout issues in the AD sync process. An AD timeout can lead to unwanted reconfiguration of the recorded users when only a subset of the configured users are retrieved from the AD during the sync process due to timeout.

- if the AD query runs too long, it can lead to unwanted reconfiguration of the recorded users, which can result to loss of recordings - there is no indication or alert if timeout occurs

- include (ObjectCategory=person) in the search filter to reduce search time - increasing the timeout value on the AD side might prevent this issue
Resolved in 8.4.4696.0
Amazon permanently disabled the built-in Amazon SES SMTP account and it can no longer be used to send email alerts from the system. Customers need to configure their own SMTP server for sending emails. This is due to an Amazon policy decision outside of our control.

- all deployments are affected where the built-in Amazon SES based account was configured to send email alerts - the system cannot send any alert until it is reconfigured to use another SMTP server

- configure SMTP server settings
Resolved in 8.6.4809.0
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.

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.

Disabling the session timer or media bypass completely resolves the issue
Resolved in 8.7.4831.0
Recording failure due to new, unsupported RTP header extension in latest Skype for Business 2016 clients.

Am I affected?
Affects all Skype for Business 2016 P2P calls between UCCAPI/16.0.6741.5270 OC/16.0.6741.2021 or newer clients

- media stream processing error causes recording failure due to a new RTP header extension - more information is expected on other affected call scenarios and client/server versions - affects all Verba releases with all types of SfB/Lync recording deployments

- currently there are no known workarounds
Resolved in 8.8.4874.0
Siren7 decoding problem is causing garbled decoding of voice in certain cases.

Am I affected?
All Lync/SfB recording deployments are affected.

- 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

- currently there are no known workarounds
Resolved in 8.8.4966.0
In a HA deployment, when multiple Verba Recording Servers are configured, then if the network connection goes down on any of the Verba Recording Servers, all IM communication stops as some of the Cisco IM&P Servers will not be able to establish the connection to another Verba Recording Server, causing all IM to stop. Cisco IM&P Servers are not able to reconnect to the Verba Recording Server after the connection is broken.

Am I affected?
All Verba deployments configured for Cisco IM recording or ethical wall are affected where multiple Verba Recording Servers are deployed in a failover configuration. All Cisco IM&P versions are affected.

- Recording/Compliance server failover does not work, the Cisco IM&P Server is not able to properly detect Verba Recording Server network failures - All IM communication is blocked by the Cisco IM&P Servers (compliance mode) if Fire&Forget is disabled

Cisco has fixed the issue and released an updated library. Now the library correctly handles OS level TCP keep alive. In addition to replacing the library, two registry entries are required under HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters: KeepAliveTime=10 and KeepAliveInterval=5000. A server restart is required for the new settings to take effect.
Resolved in 8.9.5075.0
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.

- 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

- The RTF message format can be disabled by a client policy, for more information see, DisableRTFIM
Resolved in
In case an invalid regular expression is used for internal number patterns, calls are not recorded.

Am I affected?
All version 7.x or later recording deployments where the Verba Passive Recorder Service, the Verba Media Collector and Proxy Service and the Verba Unified Call Recorder Service are used for recording could be affected.

Calls are not recorded by the related service when an invalid regular expression is applied for one of the following settings: - Passive Recorder \ Basics \ Internal Number Pattern - Media Collector and Proxy \ General \ Internal Domain, Numbers Pattern - Unified Call Recorder \ Recording Providers \ General \ Internal Domain, Numbers Pattern The system uses these configuration settings to identify the direction of recorded calls. The affected services do not raise an alarm, except the Verba Unified Call Recorder Service which will send a CallProcessing alert.

Remove any invalid regular expressions from the following configuration settings: - Passive Recorder \ Basics \ Internal Number Pattern - Media Collector and Proxy \ General \ Internal Domain, Numbers Pattern - Unified Call Recorder \ Recording Providers \ General \ Internal Domain, Numbers Pattern An online regexp validator is available to verify regexp patterns at Enter the regexp value in the input box, then press the Test button to verify the expression.
Resolved in
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.

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.

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.

Critical Fixes

There are no new critical fixes in this build.

Feature Improvements

Added in
Windows SSO improvement to avoid setting DisableNTLMPreAuth registry parameter on Windows clients
RI-003407Recording - Cisco
New configuration parameter (Cisco UCCX IP Addresses) and warning to restart service after changing UCCX Metadata Templates
RI-004158Recording - Cisco IM
Improved configuration tree for Cisco IM Recorder
RI-003375Recording - Lync/SfB
Remote traffic capture service added to Lync filter installer
RI-003402Recording - Lync/SfB
Option not to show Lync Trusted-UCMA users (announcements, music....) in conference participant lists
RI-004169Recording - Avaya
CDR information is now sent to media receiver
RI-003400Recording - Desktop
Option to avoid manual resume during screen capture auto pause
RI-003408UI - Web Interface
New Webapp configuration parameter: continue or Web player can now either continue or pause playback at the end of markers
RI-003406Solution - Speech Analytics
Passive recorders now insert marker for silence and talkover periods if voice activity detection is enabled
RI-004302Solution - Speech Analytics
Additional CDR fields populated with voice analytics results.
RI-003373Solution - Service Provider
Improvements in multi-tenant recording and access control
RI-003397Platform - Database
IM recording related database updates
RI-004168Platform - Environment
Verba web application is now compatible with Tomcat 7, tested with Tomcat 7.0.39, APR 1.1.27 (still compatible with Tomcat 6)
RI-003424Platform - Media Processing
Improvements in silence detection implementation
RI-004300Platform - Media Processing
Support for L8 and L16 RTP/AVP audio and video payload type
RI-004193Platform - Signalling
Improved SIP Subscribe-Notify based conference event handling
RI-003368Platform - Storage Management
New "upload protocol" added to recorders: local file move
RI-003410Installer - Servers
Installer prerequisite tool checks Windows language to avoid incompatibilities
RI-004167Installer - Windows Desktop
Verba desktop recorder installer supports token based user identity configuration


Fixed in
RI-004165Recording - Passive
Rare issue in passive recorder load balancing
RI-004159Recording - Cisco
In certain cases participant list not filled properly when a call was transferred multiple times
RI-003403Recording - Cisco IM
Extra newline at end of Cisco IM sessions
RI-004170Recording - Lync/SfB
Management issue with Lync Filter
RI-003404Recording - Lync/SfB IM
Minor fixes in Lync IM recorder
RI-004264Recording - SIPRec
Cisco SIPREC parsing improvements
RI-004303Recording - SIPRec
Issues with recording and ondemand decisions in multitenant environments when recording SIPREC
RI-003411UI - Web Interface
Fixes on the ongoing calls screen
RI-004209Platform - API
For improved interoperability, HTTP responses from all components now adds Content-Length: 0 if content/body is empty
RI-003413Platform - Database
Multiple events of the same SQL connection error is logged once to avoid flooding the log.
RI-003423Platform - Signalling
Resolved problems multipart content in SIP
RI-004287Platform - Signalling
Resolved potential deadlock in multithreaded SIP processing

Download your software

You can download the latest Verba releases at

Updates to this document

This document may be updated after it is released. Check for updates to this document at

Access to support

Verba customers that have purchased support have access to support through

Copyright © Verba Technologies and/or its affiliates. All rights reserved.

This document is provided under a the Verba End User License Agreement containing restrictions on use and disclosure and is protected by intellectual property laws. Unless expressly provided in any written license agreement from Verba, the delivery of this document does not give you any license to intellectual property.

Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means, or for any purpose (including, but not limited to reverse engineering), without the express written permission of Verba Technologies.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Third party product names appearing in this document may be trademarks of their respective owners.