Verba 8.1 Release Notes (build 8.1.4633.0)

Verba Release Notes

Releases

 

Current Release

Releases

3.0
3.5
4.0
5.0
6.0
7.0
8.0
   8.1
   8.2
   8.3
   8.4
   8.5
   8.6
   8.7
   8.8
   8.9
9.0
   9.1
   9.2
   9.3
   9.4
   9.5
   9.6

Build Search

 
Find your build:

(e.g. 7.0.4548.0)

Verba 8.1 Release Notes (build 8.1.4633.0)

 
This document lists new features and fixes released in Verba 8.1 Release Notes (build 8.1.4633.0).

Release Date2014-12-10
PDFDownload
Previous8.0 (build 8.0.4628.0)
Next8.2 (build 8.2.4675.0)

Release highlights

ID
Component
Description
RI-005042UI - Web Interface
New Background Task page shows state of storage/upload/labeling/speech analytics and other tasks
RI-005343UI - Web Interface
Contact Center Agent View - learn more
RI-005071Platform - Storage Management
Compliance Store support - NetApp SnapLock - learn more
RI-005072Platform - Storage Management
Compliance Store support - EMC Isilon SmartLock - learn more
RI-005073Platform - Storage Management
New data retention policy: upload allowing moving recordings from the Recording Servers to multiple storage targets based on data retention policy configuration - learn more
RI-004979Integrations
Luware Contact Center integration

Known Critical Issues

ID
First Affected
Status
Description
KI-00024.0
(4.0.0000)
Resolved in 8.3.4675.0
Summary
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.

Impact
- 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)

Workaround
- Set higher call inactivity/timeout threshold (def 180 sec -> 600 sec) - Restart recorder service every weekend
KI-00007.0
(7.0.4314.0)
Resolved in 8.3.4668.0
Summary
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.

Impact
- 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

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

Impact
- 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

Workaround
- Currently there are no known workarounds
KI-00037.0
(7.0.4314.0)
Resolved in 8.3.4693.0
Summary
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.

Impact
- 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

Workaround
- include (ObjectCategory=person) in the search filter to reduce search time - increasing the timeout value on the AD side might prevent this issue
KI-00087.0
(7.0.4314.0)
Resolved in 8.4.4696.0
Summary
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.

Impact
- 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

Workaround
- configure SMTP server settings
KI-00147.0
(7.0.4314.0)
Resolved in 8.6.4809.0
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
KI-00167.0
(7.0.4314.0)
Resolved in 8.7.4831.0
Summary
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

Impact
- 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

Workaround
- currently there are no known workarounds
KI-00187.0
(7.0.4314.0)
Resolved in 8.8.4874.0
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
KI-00307.0
(7.0.4314.0)
Resolved in 8.8.4966.0
Summary
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.

Impact
- 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

Workaround
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. https://quickview.cloudapps.cisco.com/quickview/bug/CSCvb32957
KI-00477.0
(7.0.4314.0)
Resolved in 8.9.5075.0
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
KI-00457.0
(7.0.4314.0)
Resolved in 9.0.2.5381
Summary
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.

Impact
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.

Workaround
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 https://demo.verba.com/verba/test/regex.jsp Enter the regexp value in the input box, then press the Test button to verify the expression.
KI-00587.0
(7.0.4314.0)
Resolved in 9.6.0.5944
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.
KI-00018.0
(8.0.4628.0)
Resolved in 8.3.4670.0
Summary
Short extra Lync recording segments in the beginning of Edge calls Routing of media streams might be changed up to 10 seconds into a call by Lync. In case multiple Verba recorders are used with proxy recording, the modified media stream might be process as a new call.

Impact
- effects Lync / Skype for Business recording, in proxy mode and only in redundant recorder setup - effects minor subset of calls going through Lync Edge servers - the beginning of the call might be cut off into a separate short recording

Workaround
- currently there are no known workarounds

Critical Fixes

ID
Component
Description
Fixed in
Date
RI-007734Recording - Lync/SfB
RTCP MUX with RTP was not handled properly in SDP compiling for Skype for Business calls

Impact
- 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
2015-02-17
If you are using the effected components, we recommend a software update.

Feature Improvements

ID
Component
Description
Added in
Date
RI-005103Recording - Passive
Random call recording (call sampling) support introduced
8.1.4633.02014-12-11
RI-005018Recording - Lync/SfB
Optional Route header removing is added before the filter retargets the SIP message
8.1.4627.02014-12-08
RI-005054Recording - Desktop
Desktop recorder installer now supports the Windows Authentication
8.1.4631.02014-12-09
RI-004987UI - Web Interface
New configuration interface for new storage target types (EMC, NetApp, Vantage)
8.1.4623.02014-12-01
RI-004983Platform - Database
New CDR field to store used Contact Center product
8.1.4621.02014-11-30
RI-005060Platform - Monitoring
The System alerts setting is active after installation
8.1.4632.02014-12-09
RI-004949Platform - Storage Management
Alerts are now sent on a per storage policy level
8.1.4618.02014-11-28
RI-005055Platform - Storage Management
Storage configuration on servers is restructured to better reflect new storage features and options
8.1.4631.02014-12-09
RI-005074Platform - Storage Management
Previous data retention policy 'Archive' is replaced by 3 new policies. Move Media policies allow to move media files only from one storage target to another without archiving the records in the database. DB Archive policy allows to archive database records in the database without moving the media files. DB Archive and Move Media policy executes both actions similarly to previous Archive action.
2014-12-10
RI-005075Platform - Storage Management
New storage audit log for all data retention policies
2014-12-10
RI-005076Platform - Storage Management
New retention period feature is introduced for certain data retention policies to allow configuring retention time when placing the file on the storage target. The system also allows automatic deletion after the retention period expires.
2014-12-10
RI-004995Installer - Servers
Visual C++ runtime is added as a prerequisite
8.1.4624.02014-12-02

Fixes

ID
Component
Description
Fixed in
Date
RI-005016Recording - Lync/SfB
Case sensitive comparison is changed to ignore case comparison when the filter compares the announcement service uri with the refer header
8.1.4627.02014-12-08
RI-005017Recording - Lync/SfB
Retarget error handling is added
8.1.4627.02014-12-08
RI-005027Recording - Lync/SfB
SIP Record-Route header fix to allow retargeting SIP messages for announcement
8.1.4628.02014-12-08
RI-005045Recording - Lync/SfB
Duplicated SIP header tags are removed for announcement service
8.1.4630.02014-12-08
RI-004988Recording - Lync/SfB IM
Missing From Info at group Lync IM calls
8.1.4623.02014-11-30
RI-004989Recording - Lync/SfB IM
Meet Now conference recording fix when only one participant in the conversation
8.1.4623.02014-11-30
RI-005040Recording - Lync/SfB IM
The recorder service couln't stop when the DB connection thread tried to reconnecto to the DB.
8.1.4630.02014-12-09
RI-005046UI - Web Interface
A NullPointerException thrown in the Search module when there was no additional search criteria.
8.1.4630.02014-12-08
RI-004994Installer - Servers
The installer tried to execute the update SQL during uninstall phase in some cases
8.1.4624.02014-12-02
RI-004980Integrations
Fixes for EMC and NetApp compliance store integrations
8.1.4622.02014-11-28

Download your software

You can download the latest Verba releases at support.verba.com.

Updates to this document

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

Access to support

Verba customers that have purchased support have access to support through support.verba.com.



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.