Verba 8.5 Release Notes (build 8.5.4809.0)

Verba Release Notes



Current Release



Build Search

Find your build:

(e.g. 7.0.4548.0)

Verba 8.5 Release Notes (build 8.5.4809.0)

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

Release Date2015-10-15
Previous8.4 (build 8.4.4752.0)
Next8.6 (build 8.6.4831.0)

Release highlights

RI-006559Recording - Lync/SfB
Support for Lync Panoramic Video conferences
RI-006428Recording - Truphone
New mobile phone recording integration with Truphone
RI-006711Recording - Singtel
New mobile phone recording integration with Singtel
RI-006534UI - Web Interface
Updated online knowledge base and context sensitive help
RI-006840Platform - Announcement
Lync / Skype for Business announcer service supports new call scenarios: PSTN outbound and inbound/outbound federated calls - learn more
RI-006661Platform - Storage Management
New Amazon S3 storage target allowing storing recordings in the Amazon S3 cloud service - learn more
RI-006923Platform - Storage Management
New generic SMTP storage target for exporting conversation to SMTP based compliance archives. Flexible configuration parameters to customize email content and metadata - learn more
RI-007123Platform - Storage Management
New WORM storage target, IBM Tivoli Storage Manager is added

Known Critical Issues

First Affected
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.
Resolved in 8.5.4804.0
Network port mirroring based SIP and SCCP recording might suffer from memory leak due to a TCP session cleanup bug found in TCP/IP reassembling

Am I affected?
All 8.4 and 8.5 port mirroring based recording deployments are affected. However Lync/SfB recording deployments are not affected, unless Mediation server based recording is used and standard SIP traffic is captured with the same component.

If the process runs out of memory and memory allocation fails for recorded sessions, then loss of recording might occur until the service restarts. The amount/speed of the memory leak highly depends on the amount of monitored traffic and the number of total TCP sessions monitored.

There is no known workaround.
Resolved in 8.5.4804.0
Data retention policies (except upload and export) using the global schedule (not custom) are not executed.

Am I affected?
All 8.4 and 8.5 versions are affected.

This issue can not lead to data loss, however storage policies with non-custom schedules will not be executed. The following storage policies will only be executed when custom schedules are used: Archive in DB and Move Media, Archive in DB, Move Media, Delete, Export, Transcode, Create Phonetic Index, Delete Phonetic Index. The system does not send alerts or notification messages, there is no indication of the problem other than the policies are not running.

Configuring a custom schedule for your data retention policy will enable the policy.
Resolved in 8.8.4974.0
Lync/SfB Front-End service restart can cause the failure of the Verba SfB/Lync Call Filter, the Verba SfB/Lync IM Filter and the Verba SfB/Lync Communication Policy service. After the FE service restart, these Verba services will not process SIP messages anymore until restarting the affected Verba services.

Am I affected?
All Verba version 8.5 and later deployments are affected where SfB/Lync recording or ethical wall is used.

- Conversation recording will not work after the Front-End service restart on the affected SfB/Lync server - Communication policies (ethical wall) will not work after the Front-End service restart on the affected SfB/Lync server

Restarting the affected Verba services resolves the issue. Until upgrading to a Verba version where the issue is resolved, it is advised to update operational procedures with the following: Restart the Verba SfB/Lync Call Filter, Verba SfB/Lync IM Filter and Verba SfB/Lync Communication Policy services after restarting the Front-End service.

Critical Fixes

Fixed in
RI-007032Recording - Passive
Network port mirroring based SIP and SCCP recording might suffer from memory leak due to a TCP session cleanup bug found in TCP/IP reassembling

- If the process runs out of memory and memory allocation fails for recorded sessions, then loss of recording might occur until the service crashes/restarts. The amount/speed of the memory leak highly depends on the amount of monitored traffic and the number of total TCP sessions monitored. - It affects version 8.4 and 8.5 port mirroring based recording deployments. - Lync / SfB recording deployments are not affected, unless Mediation server based recording is used and standard SIP traffic is captured with the same component.
RI-007181UI - Web Interface
Active Directory synchronization did not work when an extension - user association had to be updated.

- The problem occurs when the user association is changed for an extension, other use cases our not impacted. - It affects version 8.5 deployments only.
RI-007056Platform - Storage Management
Storage policies using the global schedule are not executed Data retention policies (except upload and new export) using the global schedule are not executed. There is no alert or system messages as the system does not try to execute these policies.

- The following data retention policies are affected when the global scheduling is used: Archive in DB and Move Media, Archive in DB, Move Media, Delete, Export, Transcode, Create Phonetic Index, Delete Phonetic Index. - Upload and new export policies are not affected. - The system does not execute these policies, only policies with custom schedule is executed. - All 8.4 and 8.5 versions are affected. - The system does not send alert or notification messages, there is no indication of the problem other than the policies are not running. - Known workaround: configure custom schedules for each data retention policy.
If you are using the effected components, we recommend a software update.

Feature Improvements

Added in
RI-006982Recording - Proxy
Alerts about SfB / Lync and recorder connection drop/reconnection. Earlier these alerts were triggered from filter/recorder side only, which could lead to delayed alerts when these components lost network connectivity or server crashed and did not recover within a short period of time.
RI-006924Recording - Cisco
Service watchdog timer has been added to Cisco GW recorder: it checks XCC connection and media handling threads, if any of them is stucked/in deadlock alert is generated and service is immediately terminated so sysmon can restart the service
RI-006897Recording - Cisco IM
Cisco persistent chat rooms now available as recording rules allowing capturing the entire traffic of the room
RI-007068Recording - Lync/SfB
The target of the announcement retargeting method is configurable now, it can use GRUU or contact address.
RI-007171Recording - Lync/SfB
New alert when Lync / SfB Front-End connection is inactive If the Lync / SfB Front-End service is started after the Verba SfB/Lync Call Filter Service or the Verba SfB/Lync Communication Policy Service or the Verba SfB/Lync IM Filter Service, the Lync / SfB Server API might not start sending messages to these Verba services. This issue can cause loss of recording, because the application will not receive SIP messages from the API connection. This scenario can now be detected and the application automatically tries to reconnect to the server, and sends an alert.
RI-007194Recording - Lync/SfB
New alert is sent when the Lync/SfB Filter reconnects to the Front-End server and it does not receive any messages for a certain amount of time.
RI-006907Recording - Lync/SfB IM
Multi-tenant support is introduced in the Lync IM recorder
RI-006606Recording - Avaya
Do not unregister extensions right after a call ended, but wait 60 seconds. If a new call is delivered right after a call ended, then the new call may was not recorded.
RI-006831Recording - Avaya
Verify station registration every time a recording initiated.
RI-006539UI - Web Interface
New permission: Access Secondary Recordings
RI-006540UI - Web Interface
New permission: Customize own conversation layout
RI-006657UI - Web Interface
Legal hold enhancements: automatic label rules can be initiated from the Search screen.
RI-006746UI - Web Interface
When a user is deactivated manually, the system asks the user if the associated extensions should be deactivated too.
RI-006747UI - Web Interface
Possibility to run single AD sync profile manually even if the user-deactivation threshold is reached
RI-006749UI - Web Interface
Possibility to run single AD sync profile even if deactivated
RI-006751UI - Web Interface
Services can be configured to Automatic (Delayed) startup.
RI-006811UI - Web Interface
New configuration option: "Send email notification on successful AD sync runs"
RI-006512UI - Reporting
New users without any recording report.
RI-006771Platform - Announcement
The announcement service configuration and load balancing has been changed. The announcement servers shouldn't be listed in the filter configuration, just the announcement uri is required. The system is now using the Lync/SfB provided load balancing and failover feature.
RI-006772Platform - Announcement
The announcement starting position has been changed from Establising to Established to avoid missing announcements in early media stage.
RI-006833Platform - Announcement
New service statistics are implemented in the announcement service.
RI-006804Platform - Configuration
Missing registry entries are now automatically created on the server.
RI-006806Platform - Configuration
New extension types: "User/Agent ID" and "Persistent Chat Room"
RI-006838Platform - Configuration
New Never Record option is introduced to allow configuring extensions/addresses where the recording is prohibited in any case.
RI-007182Platform - Database
SQL JDBC Driver updated to version 4.2.
RI-006563Platform - Environment
Shared recorder specific ACL handling and recording has been implemented
RI-006566Platform - Media Processing
Dedicated media IP address can be configured now for the RTP stack, by default if this config is empty it reverts to server IP config
RI-007169Platform - Media Processing
VOX ADPCM support added
RI-006573Platform - Signalling
Media IP and SIP IP can now be configured as different/dedicated one for the stack
RI-007066Platform - Signalling
SIP trunk monitoring, state up/down alerts for any SIP based recording provider supporting OPTIONS pinging
RI-007184Platform - Signalling
SIP reassembling and processing part revised and reorganized to gain more performance
RI-006821Platform - Storage Management
Conversation Export: Manifest File's default extension changed to xml (was ctl)
RI-006855Platform - Storage Management
New authentication option for SMB network folders. In addition to service user based authentication, custom credentials can be configured too.
RI-006892Platform - Storage Management
Transcoding capability added to Smarsh drive (they prefer MP3/MP4 now due to HTML5 playback)
RI-006787Installer - Servers
Java 8 support is introduced and added to the installer, it supports both Java 7 and Java 8. The preferred version is Java 8.
RI-006942Installer - Lync/SfB Filter
Improvements related to service account check for nested groups and the ability skip check completely.
On-demand call handling support is introduced in Lync/SfB extension window. The users are able to keep their recordings (audio/video only) using the Lync/SfB Extension Window.


Fixed in
RI-006641Recording - Passive
TCP reassembling: TCP seq number overflow was not taken into account when current stream byte position was calculated. This could lead to discard subsequent TCP chunks
RI-007037Recording - Passive
If SDP is only present in the 183(Session in Progress)/180(Ringing) messages, but not in the OK message, recording is not initialized as lack of SDP on callee side. Now 200 (call established) triggers recording but SDP in provisional response is used
RI-007039Recording - Passive
When SCCP call caller id is blocked the CDR shows same caller and callee number leading to duplicated recordings as both caller and callee are provisioned for recording. The SCCP parser is fixed and in this case the blocked cid is identified, shown in CDR as anonymus.
RI-007186Recording - Passive
The continuous silence generation to fill DTX gaps are limited to 30 mins to avoid huge files when call stucks in (should never happen due to RTP inactivity detection) or RTP inactivity timer has huge value
RI-006488Recording - Proxy
Lync/SfB PSTN caller from bypass enabled trunk, simulring: in rare cases when someone has already accepted the call but Lync/SfB still forks INVITEs to other parties, the INVITE received in connected state triggers deallocating caller side ports (one negotiated SDP vs 3 new offered in multipart content) and allocating new one leading to media connectivity failure at caller side.
RI-006546Recording - Proxy
Answering the same simring call from multiple endpoints exactly in the same time might lead to disconnected call if due to varying network delay the callee receives OK from the second answering endpoint (from our point of view) earlier. Now the media proxy module follows each forked subleg properly in the same SIP session and so does not deallocate relay ports prematurely
RI-006710Recording - Proxy
Relay session was terminated if BYE was initiated by caller regardless which subsession the BYE was issued to. Now only the related subsession is terminated. If callee sent BYE the service worked properly.
RI-006792Recording - Proxy
In controlled recording mode the proxy forwarded RTP to recorder when recording was not started and stream was not requested. This bug was introduced with the "shared recorders" feature.
RI-006813Recording - Proxy
Invalid STUN messages (length sanity check) were unintentionally discarded which might lead to ICE issues (Polycom Kirk)
RI-006694Recording - Cisco IM
Now we are able to store unlimited number of bad SQL statements in the cache files.
RI-006925Recording - Cisco IM
When the internal pattern was not provided, the recorder could not work properly.
RI-007109Recording - Cisco IM
Reading back conference state at start didn't closed the inputstream properly.
RI-007115Recording - Cisco IM
On session close, the service now checks if the session is already closed. Identification of conference packets is improved.
RI-007119Recording - Cisco IM
Deadlock occurred when a session operation didn't succeed and another thread tried to open the same session.
RI-006617Recording - Lync/SfB
The Lync Filter component handled a SIP request as non-recorded one which has been already relayed on a proxy server and it lead to one way audio issue in simulring, team-call, and delegate scenarios.
RI-006728Recording - Lync/SfB
In case of SfB / Lync conferences, when there are frequent reinvites (300ms-1s during 3-4 minutes in rare conditions), the recorder reinitialized the media stack unnecessarily causing media quality degradation.
RI-006977Recording - Lync/SfB
SfB / Lync RGS Agent anonymity: recorded caller - RGS UCMA B2B agent call legs transferred into each other could not be matched leading to two recordings: one containing only some sec of media, other containing the rest of the call ending with timeout. UCMA B2B - agent leg was handled properly
RI-006978Recording - Lync/SfB
Lync RGS Agent anonymity enabled: when both caller-UCMA B2B and UCMA B2B - agent leg is recorded by the same recorder then after the "technical" leg on the agent side of B2B (first 2-3 sec, agent creates new call to caller replacing the one with caller->agent cdr info which we merge into the same call) the leg from agent's point of view is not recorded properly as the stream directions are swapped leading to no media recording and SRTP media error warning. The caller - UCMA B2B leg is recorded properly.
RI-007193Recording - Lync/SfB
Using mediation based recording, the ACL didn't worked correctly in some cases and led to loss of recording. It does not affect proxy based, edge based and AVMCU based recording.
RI-006598Recording - Avaya
Yet start recording after a transferred event, because if a held connection and the active call transferred, then no established event will be received.
RI-006599Recording - Avaya
Do not start recording after a transferred event, but wait for the Established event instead on conference+park events - if we parked the call, then stop the recording, but do not start a new recording. - if not we parked the call, then do nothing
RI-006602Recording - Avaya
Dynamic Registration is turned off by default. Last error caused by this: if the extension got unregistered while there was an incoming alerting call, or the agent took off-hook the phone, then the new call could not be recorded.
RI-006798Recording - Avaya
Alert was not sent when RTP timeout occurred on an extension.
RI-006854Recording - Avaya
Do not consider very short calls where we did not receive media as RTP failure (and so re-registration should not occur)
RI-007099Recording - Truphone
CDR metadata parsing fix
RI-006496Recording - Desktop
On-demand call handling: keep flag is now checked not just for finished calls, but for ongoing calls as well.
RI-007042Recording - SIPRec
In multitenant environment, tenant matching was always done by BW group id, matching purely based on extension could not be set.
RI-007141Recording - SIPRec
SIPREC SRTP negotiation fixed, it takes now into account local capabilities instead of just accepting and copying the keys from the SDP offer. Similar changes has been done for all SIP specific recording providers
RI-006593UI - Web Interface
Player did not work with IE 10 + Compatibility Mode (because console object is undefined)
RI-006645UI - Web Interface
Environment administrators were not able to save environment parameters.
RI-006647UI - Web Interface
"Time of the day" filter removed from the Search panel
RI-006731UI - Web Interface
Email address validation: allow any characters before the @ character.
RI-006808UI - Web Interface
When the webapp looked for related calls, it may throw an error (SQLServerException: The index 6 is out of range)
RI-006962UI - Web Interface
Invalidate/Make Valid buttons added to extension page. The extension list shows the assigned user for invalidated extensions also.
RI-007024UI - Web Interface
Active Directory Profile's Password was logged in the Audit Log as clear text.
RI-007031UI - Web Interface
Advanced Call Export from the Search screen messed up the Time interval in the query description string.
RI-007055UI - Web Interface
Call Deletion will not create backup files from now on (due to issues with WORM storage systems), instead it deletes the "main" media the last.
RI-007064UI - Web Interface
Regular\Conversation Export permission was not granted to the Legacy Download role.
RI-007070UI - Web Interface
License problems were not sent to users who had permission to see the License screen (the emails were sent to the target email set in the Email Settings, though).
RI-007072UI - Web Interface
On-Demand configuration was not displayed on Media Repositories (was displayed on Combos)
RI-007087UI - Web Interface
Firefox automatically filled the Valid Until and Avaya Password fields on the Extension details screen.
RI-007118UI - Web Interface
Some legacy roles missed the "Personalize Conversation List Layout" permission.
RI-007120UI - Web Interface
After playing back a call that was stored on a storage target accessible through the Storage API, the media might got deleted.
RI-007127UI - Web Interface
Retention fields were missing from conversation detail page
RI-007128UI - Web Interface
When a QA "Auto-Fail" question failed the whole scorecard, then some points were not set to zero
RI-007139UI - Web Interface
If the connection to the SMTP server stuck during email sending, the email sending daemon stopped working (stuck forever).
RI-007144UI - Web Interface
Ethical Wall events were counted in "# of Simultaneous Calls..." and "# of Recorded Hours Per Day..." license usage
RI-007114UI - Waveforms
Waveform and segment export did not work for recordings that could be accessed via the Storage API
RI-006812UI - Reporting
Several report displayed time values in GMT instead of the report timezone.
RI-007129UI - Reporting
Do not count Ethical Wall events in parallel call count report.
RI-006571Solution - Ethical Wall
Improved handling of conference data share modality.
RI-007173Solution - Ethical Wall
Content filter/phrase based redact: only the first occurance of the phrase was redacted
RI-007122Solution - Silent Monitoring
Central Cisco Silent Monitoring: the target party was not highlighted in red and bold style.
RI-006514Platform - API
AddMarker API call didn't allow to add markers wit h the same name but it is not restricted.
RI-006818Platform - API
SearchCalls API returned zero rows when status=ongoing parameter applied.
RI-006607Platform - Database
The node manager agent was not able to register in the database.
RI-007057Platform - Database
Update SQL script threw an error during an upgrade if Full-Text Search was available and the full-text index was already added to the section_chat table.
RI-006510Platform - Media Processing
VMF Lync panoramic video playback fix
RI-006560Platform - Media Processing
VMF header size was limited to 16kb which is too small in case of Lync video conferences with ICE and a high amount of SVC layers for many video streams. Now it is increased to 64kb. Old codec will not be able to decode new VMF and Silent monitoring
RI-006870Platform - Media Processing
MS-ADPCM encoding fatal issue could resulted memory corruption leading to unpredictable behavior (crash) of recording services
RI-007176Platform - Signalling
SIP stack: now the SRTP keys are properly negotiated based on the local capabilities instead of just accepting the first key offered by the remote side
RI-006495Platform - Storage Management
Transcoding did not take into account source storage, defaulted to registry media folder
RI-006703Platform - Storage Management
Old policy based export did not provide proper path for copying media after transcoding
RI-006755Platform - Storage Management
Conversation Export: "Start Time (UTC)" filter was unusable after the filter changed to "Recent Than" and then changed back to "Start Time (UTC)"
RI-006793Platform - Storage Management
Export: filenames are always postfixed with some guid when rename pattern is used to make sure filenames are unique. Now if the rename pattern contains guid elements this postfix is not concatenated
RI-006547Platform - Tools
TLS private key file password was displayed in clear text format in the media streamer service log file.
RI-006796Installer - Servers
Email regex pattern is changed on the email configuration page, and the installation can be continued if the email address is not standard, the installer will just warn
RI-006954Installer - Servers
Missing media folder fix in speech server role installer
When media is not recorded by remote cluster's shared recorder the ongoing call in local cluster db is deleted instead of closed. That way CDR reconciliation can detect the failure if call was neither remotely nor locally recorded
SQL transaction and so database access for the label processing service stuck when connection is lost/timed out after issuing begin transaction since after reconnecting the commit transaction is executed without matching begin transaction.
When a Lync/SfB recorded user was invited into the conference on a mobile/work phone not set for recording (contact card) the CDR caller uri was filled with the recording provisioned Lync uri causing false matches in the CDR reconciliation process.
Call healing: call related files were searched based on path\cdr_id*.ext which turned out to be extremly slow if there are many files (500gbyte). Now the filename is calculated based cdr information as the media processing part of recorders does, so we can directly locate the xml and media part files
Call healing: the process could not be stopped on graceful shutdown leading to wait for processing all the previously stucked calls

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.