Verba 9.6 Release Notes (build 9.6.13.6790)

Verba Release Notes

Releases

 

Current Release

Releases

3.0
3.5
4.0
5.0
6.0
7.0
8.0
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 9.6 Release Notes (build 9.6.13.6790)

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

Release Date2020-09-10
PDFDownload
Previous9.5 (build 9.5.13.6058)

Known Critical Issues

ID
First Affected
Status
Description
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-00609.6
(9.6.13.6790)
Resolved in 9.6.3.6043
Summary
A query error leads to an increasing size of the local database cache on the Media Recorders storing VOX/voice activity events which leads to performance degradation and affects media processing which can cause data loss in recorded conversations. The problem was introduced in v9.6 with the new feature which can avoid creating unnecessary CDRs for long open line calls without any media activity.

Am I affected?
All v9.6 trader voice recording deployments (BT ITS, BT IPTrade, IPC Unigy and Speakerbus) are affected where VOX/VAD triggered media recording is configured and Media Recorders and Recording Directors are deployed on separate servers. Note: v9.6 Unified Call Recorder service executable can be potentially deployed on top of previous installations too.

Impact
- The issue manifests after many weeks or months of deployment (depending on server load and server performance) and once the size of the cache reaches a critical size the issue becomes more and more evident - Parts of affected media records might become choppy/bad quality/some seconds missing -Voice quality check reports packet loss and affected media records in UI/search/call details are marked with packet loss media processing error - In the case of BT ITS integration TTP packet loss alerts are triggered

Workaround
It is recommended to manually delete the local cache database in a maintenance window, every 1-2 weeks depending on server load on Media Recorder servers (Recorder Servers acting as Media Recorder role for Unified Call Recorder service): 1. Stop the Verba System Monitor and Unified Call Recorder services 2. Delete verba_install_folder\work\unified rec\dbcache\voxhistory.db file 3. Start the stopped services

Critical Fixes

ID
Component
Description
Fixed in
Date
RI-021153Recording - Lync/SfB
Certain calls between Skype for Business and Teams or Azure VoiceMail cannot be recorded

Impact
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.
9.6.0.59442020-06-10
RI-024146Recording - Unified Call Recorder
A query error leads to an increasing size of the local database cache on the Media Recorders storing VOX/voice activity events which leads to performance degradation and affects media processing which can cause data loss in recorded conversations. The problem was introduced in v9.6 with the new feature which can avoid creating unnecessary CDRs for long open line calls without any media activity.

Impact
All v9.6 trader voice recording deployments (BT ITS, BT IPTrade, IPC Unigy and Speakerbus) are affected where VOX/VAD triggered media recording is configured and Media Recorders and Recording Directors are deployed on separate servers. Note: v9.6 Unified Call Recorder service executable can be potentially deployed on top of previous installations too. - The issue manifests after many weeks or months of deployment (depending on server load and server performance) and once the size of the cache reaches a critical size the issue becomes more and more evident - Parts of affected media records might become choppy/bad quality/some seconds missing -Voice quality check reports packet loss and affected media records in UI/search/call details are marked with packet loss media processing error - In the case of BT ITS integration TTP packet loss alerts are triggered Workaround It is recommended to manually delete the local cache database in a maintenance window, every 1-2 weeks depending on server load on Media Recorder servers (Recorder Servers acting as Media Recorder role for Unified Call Recorder service): 1. Stop the Verba System Monitor and Unified Call Recorder services 2. Delete verba_install_folder\work\unified rec\dbcache\voxhistory.db file 3. Start the stopped services
9.6.3.60432020-11-13
If you are using the effected components, we recommend a software update.

Feature Improvements

ID
Component
Description
Added in
Date
RI-024159Security
Apache Tomcat application server hardening: - CBC hash algorithm ciphers have been removed - HSTS Max Age has been increased to one year (was 90 days)
9.6.4.60622020-11-20
RI-025927Security
OpenSSL library is updated to the latest v1.1.1j
9.6.6.63042021-02-18
RI-026723Security
OpenSSL library is updated to the latest v1.1.1k
9.6.9.63912021-03-26
RI-023492Recording - Passive
Passive Recorder does not release/invite conference announcement again at recording segmentation
9.6.0.59692020-08-19
RI-024016Recording - Cisco IM
Cisco Webex Teams chat import and API throttling improvements to avoid API overload
9.6.1.59952020-08-10
RI-023509Recording - Lync/SfB
If the capture interface cannot be recovered then the Media Collector & Proxy service will be automatically restarted and an alert is raised
9.6.0.59712020-08-24
RI-023510Recording - Lync/SfB
A new Call Processing alert is generated when the Media Collector & Proxy service is not able to allocate media ports
9.6.0.59712020-08-24
RI-023637Recording - Microsoft Teams
Recording announcements can no longer be configured for Teams recording due to Microsoft restrictions. Configurable announcement policies for P2P calls are coming later in Microsoft Teams as a built-in feature.
9.6.0.59812020-09-08
RI-024046Recording - Microsoft Teams
Microsoft Teams Bot service supports maintenance mode which allows gracefully draining the server before shutting down the service
9.6.4.61452020-10-15
RI-024175Recording - Microsoft Teams
The Microsoft Teams Bot service is now able to reread the following configuration values without restart: - Log level - Compress RAW audio to G.711 - Bidirectional/Stereo Recording - Number of Recorded Video Participants - Preferred Video Resolution - Preferred Screen Share Resolution - Separated Screen Share Record - Start Recording After Recorded User Joined - Block Calls when Recording Server Unavailable
9.6.4.60622020-10-15
RI-024610Recording - Microsoft Teams
New configuration added 'Record non-configured extensions'. If turned on, the Microsoft Teams Bot service will start recording those extensions too which are not added to the Verba configuration with all modalities. The extensions added to the configuration are interpreted as usual. By default, the setting is turned off.
9.6.4.61542020-12-07
RI-024611Recording - Microsoft Teams
Microsoft Teams Bot Service is now running on .NET 4.8. All dependencies (Teams Calling SDK v1.2, Teams Bot Media SDK v1.19) updated to the latest versions.
9.6.4.61542020-11-19
RI-026918Recording - Microsoft Teams
Microsoft Teams conditional recording for voice/video/screen: - New extension configuration is introduced which adds the capability of recording a user only in the case of meetings where external participants are present. The recording is initiated when the first external party enters the meeting and it is terminated when there are no remaining external users in the meeting. - New extension configuration is introduced which adds the capability of recording only the video stream of external participants. If turned on, the Verba Microsoft Teams Bot service won't subscribe for internal participants' video streams. - New extension configuration is introduced which adds the capability of recording only scheduled meetings (queried via the Graph API). Two additional configurations are added according to this feature. The recording trigger can be the meeting organizer or the meeting subject.
9.6.9.64102021-03-09
RI-026922Recording - Microsoft Teams
The Microsoft Bot Media SDK was updated to 1.20.0.348
9.6.9.64102021-03-09
RI-028148Recording - Microsoft Teams
PSTN number support added to the never record feature for the Microsoft Teams Bot service.
9.6.12.66662021-06-29
RI-026026Recording - Microsoft Teams IM
Microsoft Teams instant message, attachment capture and archiving: - Event/webhook (DLP) based API integration, where the Teams platform sends all updates once the recorder subscribes - Support for on-prem, cloud and hybrid deployments - Supports always-on recording mode only - Supports all instant message scenarios, teams, channels, P2P, and meeting chats - Supports all formatting options, emojis, giphys, stickers, and other apps - Limitation: no selective capturing/archiving support, only tenant-wide capturing - Limitation: chat sessions initiated from external domains won't be captures
9.6.6.63052021-02-18
RI-027864Recording - Microsoft Teams IM
Forward proxy configuration support for Microsoft Teams IM provider
9.6.11.65422021-04-22
RI-028320Recording - Microsoft Teams IM
New service counters for Unified IM Recorder: - Number of new events in last 15 minutes - Number of new events in last 1 hour New service alert for Unified IM Recorder for inactivity alarm (disabled by default) with the following service level settings: - Enable Recording Inactivity Alert - Minutes Between Recording Inactivity Checks - Recording Inactivity: New Message Events Threshold
9.6.12.66662021-07-16
RI-028834Recording - Microsoft Teams IM
Participant cache refresh timer can be configured for minutes (earlier it was hours) to allow more frequent update of the participants for groups and channels
9.6.13.67902021-09-22
RI-028877Recording - Microsoft Teams IM
Conversation Detail Record is no longer created for bot participants
9.6.13.67902021-09-22
RI-027265Recording - Avaya
Avaya Password added to the Active Directory Synchronization and Provisioning API
9.6.10.64562021-04-15
RI-028233Recording - Avaya
Improve the Avaya DMCC Recorder to not try to register non-numeric Extensions, and not go to the next CM in case of InvalidActiveDeviceState and InvalidParameterValue errors
9.6.12.66662021-07-07
RI-021884Recording - Unified Call Recorder
New configuration setting for trader voice recording integrations (Do Not Keep Openline CDRs Without VOX Activity) which can avoid creating unnecessary CDRs for long open line calls without any media activity.
9.6.0.59542020-07-28
RI-024124Recording - Unified Call Recorder
The default value for the "Do Not Keep CDRs without VOX Activity" setting is changed to "Only at Call Segmentation" (from "Yes")
9.6.2.60152020-11-04
RI-024129Recording - Unified Call Recorder
Improved media processing when a large number of recordings (100s) starts exactly at the same time triggered by voice activity
9.6.2.60152020-11-03
RI-026105Recording - Unified Call Recorder
Minimum RTP port range limits are removed when configuring the RTP port range for the service (Media Port Range Begin, Media Port Range End) to allow deployments where the RTP port range has to be kept as narrow as possible. Previously, the RTP port range was limited to a minimum of 64 / CPU core.
9.6.6.63122021-02-23
RI-027771Recording - Unified Call Recorder
E-Dialer integration via REST API for Cisco network based recording and BT ITS recording. The integration allows the creation of CDR-Only records based on the information sent by the dialer to the system.
9.6.11.65262021-05-22
RI-028208Recording - Unified Call Recorder
Integration with the Verizon Meeting platform using SIP based dial-in recording where the meeting host ID and the meeting ID are transmitted using DTMF codes
9.6.12.66662021-07-05
RI-027914Recording - IPTrade
BT IPTrade TPO recording: metadata reflects the TPO side known display name of the recorded party as it might be more valuable for open lines/DDIs (provides line/DDI name instead of trader/username)
9.6.12.66662021-06-10
RI-024237Recording - BT ITS
In the case the trader ID changed from 0 (unknown) to a valid ID midcall, the system stopped all recordings and expected new connections from the new trader. With the improved functionality, the system continues recording and updates the trader ID.
9.6.4.61042020-11-26
RI-025010Recording - BT ITS
In the case of BT ITS integration, which does not enforce recording rules, the recorder still tries to lookup recording rules/recorded extension to support direct upload/export, shared server features
9.6.6.62372021-01-21
RI-027714Recording - BT ITS
Calling number identification in ongoing list is updated immediately after it is received (it was only updated at call end previously)
9.6.11.65422021-03-23
RI-026444Recording - IPC
Local SIP Port can be configured in the IPC Zone configuration widget
9.6.8.63722021-03-12
RI-028299Recording - IPC
IPC Unigy optimized port utilization: the same port is offered for secure and non-secure streams in SDP to make the required port range narrower
9.6.12.66662021-06-30
RI-024202Recording - Cloud9
Improved error handling for Cloud9 Call Data API based import when the service is unable to process the media file, the data is kept (no longer ignored) in a separate failed media folder on the server
9.6.4.60722020-11-18
RI-023491Recording - Dial-in
Dial-in Recorder: add support for call segmentation and improved silence gap filling for silence suppression/DTX
9.6.0.59692020-08-19
RI-026656Recording - SIPRec
Support for Mitel Border Gateway (v11) recording via SIPREC
9.6.9.63862021-03-23
RI-023900Recording - Symphony
Canceled Symphony calls are recognized and no longer marked as failed recordings
9.6.0.59872020-09-15
RI-027408Recording - Genesys
New integration with the Genesys Pure Engage on-premise contact center platform: - Integration with Genesys SIP Server for media stream recording - Integration with Genesys T-Server for CTI - Always-on and selective recording
9.6.10.64602021-02-16
RI-028311Recording - Genesys
New configuration: Skip Duplicate Records. In the case of 2N CTI recording, the Verba Genesys CTI service will only insert the CDR-Only record into the database, if the records were not inserted before. This ensures that only one CDR-Only record is created for every call.
9.6.12.66662021-07-16
RI-028312Recording - Genesys
T-Server connection alert throttling is introduced. The service will send alerts only in the case of a lost connection.
9.6.12.66662021-07-16
RI-029216Recording - Zoom
Integration with the Zoom cloud-based meeting and calling platform: - Archiving Zoom Meetings and Zoom Phones recordings for configured users - Integration with public Zoom APIs - Support for voice, video, and screen & application share modalities - Unaltered download and import of media files (MP3, M4A, MP4) - Import of meeting and phone call metadata - CDR reconciliation with Zoom call/meeting logs to identify not recorded or archived calls - Configurable query intervals through import policy schedule - Multi-tenant support, the ability to configure any number of Zoom tenants as separate import sources in any environment/tenant - Support for forward proxy based configurations
9.6.13.67902021-09-22
RI-023463UI - Web Interface
Apache Tomcat version is upgraded to 9.0.37
9.6.0.59662020-08-13
RI-023592UI - Web Interface
All HTTP traffic is automatically redirected to HTTPS by default in the Web Application
9.6.0.59742020-08-28
RI-023673UI - Web Interface
The duration filter now supports milliseconds to make sure the specified seconds are correctly filtered in the Data Retention Policy, Conversation Export, Labeling Rules, Role features
9.6.0.56772020-09-09
RI-024058UI - Web Interface
Improved group filter performance in Data Retention Policies, Roles Conversation Access Filters etc.
9.6.2.60152020-10-19
RI-024095UI - Web Interface
Start Search Automatically is disabled by default for new installations to improve search performance for large databases. It can be enabled in the service configuration.
9.6.2.60152020-10-19
RI-024134UI - Web Interface
"Search conference participants" renamed to "Search All Participants"
9.6.2.60152020-10-19
RI-024406UI - Web Interface
New Identity Provider (IdP) option: Authentication with Reverse Proxy which allows single-sign-on deployment where the IdP is providing the authentication information in HTTP request headers via a reverse proxy deployed in front of the Tomcat application server
9.6.4.61452020-12-08
RI-024794UI - Web Interface
Two new configuration options for the Cisco Finesse Gadget: - TryAutoLogin (default: true): when the gadget loaded it tries to retrieve a token with the credentials used for logging into Finesse. - ErrorPopup (default: true): if disabled then no error pop up will appear, only the status bar will reflect the error messages.
9.6.5.61872021-01-07
RI-025848UI - Web Interface
Updated Web Application dependencies: Puppeteer (v7.0.4), embedded Chromium (v90.0.4403.0)
9.6.6.62772021-02-10
RI-025918UI - Web Interface
New Identity Provider (IdP) option: JSON Web Token (JWT) based authentication (RFC 7519)
9.6.6.63022021-02-17
RI-025922UI - Web Interface
Apache Tomcat version is upgraded to 9.0.43
9.6.6.63022021-02-17
RI-025925UI - Web Interface
Improved web interface optimized for mobile devices
9.6.6.63042021-02-18
RI-026016UI - Web Interface
Default datetime settings for search: for Today, and Last X Minutes filters use the end of the current day time instead of the current time
9.6.6.63082021-02-19
RI-026778UI - Web Interface
The maximum size of the heap memory of Tomcat web application server is increased from 1GB to 2GB by default
9.6.9.64012021-04-01
RI-027467UI - Web Interface
Updated Web Application dependencies: Puppeteer (v9.0.0), embedded Chromium (v91.0.4469.0)
9.6.10.64652021-04-28
RI-027484UI - Web Interface
Improved configuration validation for bulk extension updates
9.6.11.65102021-04-30
RI-027728UI - Web Interface
Custom legal disclaimer messages can be added to the login screen via the web UI customization/brandind feature
9.6.11.65412021-05-07
RI-028175UI - Web Interface
New configuration available to control the visibility of labels, which is effective for all users including Supervisors
9.6.12.66662021-07-01
RI-028260UI - Web Interface
Updated Web Application dependencies: Puppeteer (v10.1.0), embedded Chromium (v92.0.4512.0)
9.6.12.66662021-07-12
RI-028418UI - Web Interface
The Meeting ID and Technical ID fields added to the Conversation List Layout Configuration, and Meeting ID added to the Conversation Details and the Advanced Search
9.6.13.67902021-09-22
RI-028670UI - Web Interface
The Data Retention Policies showed all Background Task records for a given policy, and that can result in a huge dataset. It will show the last three tasks from now on.
9.6.13.67902021-09-22
RI-028847UI - Web Interface
Apache Tomcat version is upgraded to 9.0.50
9.6.13.67902021-09-22
RI-028862UI - Web Interface
Improvements for built-in accounts: - Verba Administrator user account cannot be deleted (only invalidated) - Verba API User account cannot be deleted - Verba System account cannot be managed through the UI and cannot be used to login into the system
9.6.13.67902021-09-22
RI-028923UI - Web Interface
Video transcoding job monitoring improvements: - Users can view their pending and ongoing transcoding jobs on the Search page - Information about the number of transcoding jobs in the processing queue before the submitted job - Administrators can view all pending and ongoing transcoding jobs on the Background Tasks page - New Retry option for failed transcoding jobs - New Cancel option for pending and failed jobs
9.6.13.67902021-09-22
RI-020986UI - Reporting
Improved CSV report format, all report produces a valid CSV file
9.6.0.59392020-04-20
RI-023933UI - Reporting
New Users Conversation Volume report showing the total number of recorded conversations for users
9.6.0.59872020-09-15
RI-028679UI - Reporting
Several report enhancements: - The Filtering Criteria and Identity Providers are added to the existing Roles and Permissions Report - The "Access Type" ("User" or "Supervisor") and "Roles" fields are added to the Audit Log and Conversation Access reports - Group filter option is added to CDR Reconciliation reports - New report: Announcement Users Configuration showing the announcement related configuration for the users - New Excel Export link for Extensions - New Excel Export link for Active Directory Synchronization Profiles - New Excel Export link for Data Management Policies - Source Platform filter option is added to existing reports - Performance improvements for Voice Quality Check reports - Agent terminology is replaced to User in all reports - Enhanced report selection where user can type the report name to filter the list
9.6.13.67902021-09-22
RI-028849UI - Reporting
Conversation Count Trend widget improvements: - New filtering options: Platform, Import Source - Date filtering did not work
9.6.13.67902021-09-22
RI-028934UI - Reporting
Dashboard date interval settings did not use the calendar units for days, weeks, months, etc. to define the first interval and used the current date and time instead of using the beginning of the calendar unit. E.g. Today: 2021-08-28 Time interval: Last 2 months Time interval: 2021-06-28 - 2021-08-28 Time steps: 6/2021 (4 days were calculated only from the month while it should have been the full month) 7/2021 (full month) 8/2021 (partial, but it is normal because the remaining part of the current month is in the future)
9.6.13.67902021-09-22
RI-027587Solution - Speech Analytics
Server Name Indication support added to TLS for the Speechmatics integration
9.6.11.65422021-04-30
RI-020993Platform - API
All internal and external APIs now use HTTP Basic Authentication by default
9.6.0.59392020-04-16
RI-026251Platform - API
New version (3) of the provisioning API is available with the following key improvements: - Extended attributes for User management: retention, custom fields, announcement settings, etc. - Extended attributes for Extension management: type, recording rule, recorded platform, etc.
9.6.7.63492021-03-05
RI-028256Platform - API
Provisioning API can be used by tenant-level users (previously it was only available for service/hosting providers)
9.6.12.66662021-07-07
RI-020958Platform - Configuration
Performance improvements for Azure AD synchronization to support a large number of users
9.6.0.59392020-04-23
RI-026537Platform - Configuration
New external Recording Server deployment option for environments where the connection between the Recording Serves and the rest of the recorder infrastructure (database server, storage, application servers, etc.) is limited by strict security and firewall rules. A typical use case is when a hybrid architecture is deployed with components on-premise and in the cloud which requires changing the communication between the cloud and the on-premise components from a push to a pull approach.
9.6.8.63782021-03-17
RI-027730Platform - Configuration
Revised NIC/capture interface listing to provide more information and interfaces which might be discarded due to special drivers involved (e.g. NIC teaming)
9.6.11.65422021-05-07
RI-027738Platform - Configuration
Node Manager connection can be optionally encapsulated into HTTPS to support strict firewall and forward proxy configurations
9.6.11.65412021-05-11
RI-020237Platform - Database
Microsoft JDBC driver (used by Java based services such as Web Application, Cisco JTAPI, Cisco IM&P, Avaya DMCC) is updated to version 8.2
9.6.0.59192020-03-25
RI-023512Platform - Database
Upload policy can run during maintenance job execution to avoid long-running maintenance jobs blocking the upload functionality
9.6.0.59712020-08-19
RI-024690Platform - Database
The database Index Rebuild process is automatically stopped after 24 hours to avoid blocking normal operation by the database maintenance process
9.6.5.61782020-12-22
RI-027072Platform - Database
The search was slow in certain cases because the SQL Server has built the wrong execution plan
9.6.10.64562021-04-08
RI-027336Platform - Database
Improved call record insert performance by removing the possibilities for long running queries (e.g. legal hold management)
9.6.10.64562021-04-22
RI-028347Platform - Database
Improved legal hold performance for the advanced voice (incl. trader voice) data model
9.6.13.67902021-09-22
RI-023668Platform - Licensing
Multi-tenant license allocation and enforcement which can be used to allocate licenses to individual tenants from the license pool. License enforcement is also tenant-based when this option is enabled.
9.6.0.59812020-06-29
RI-024996Platform - Licensing
License violation alerts include more detailed information about the current license
9.6.6.62362021-01-25
RI-024195Platform - Monitoring
Customizable alert severities and selective alert sending option added for the System Monitor service on the servers
9.6.4.60722020-11-20
RI-024470Platform - Monitoring
BT ITS TTP packet loss alerts added to SCOM MP and SNMP MIB files
9.6.4.61502020-11-16
RI-024752Platform - Monitoring
The event ID attribute is added to SNMP traps
9.6.5.61832020-12-09
RI-026196Platform - Monitoring
SCOM package and SNMP MIB updated with new alerts for Microsoft Teams Bot, Genesys CTI and Unified IM Recorder services
9.6.6.63182021-02-23
RI-026743Platform - Monitoring
The import service sends an alert when an import source cannot be started due to a bad configuration
9.6.9.63972021-03-30
RI-027474Platform - Monitoring
New system monitoring module which monitors server time and detects and logs abrupt time jumps which might cause issues for other services
9.6.10.64662021-04-29
RI-021944Platform - Storage Management
Microsoft Azure Blob Storage support (in addition to existing Azure File Storage)
9.6.0.59542020-06-22
RI-023901Platform - Storage Management
Filtering of CDRs without media is done in the Storage Service for performance reasons
9.6.0.59872020-09-16
RI-023983Platform - Storage Management
VSFT secure file upload protocol connection timeout is now configurable
9.6.1.59952020-10-08
RI-023993Platform - Storage Management
New SMTP export target fields to display date and time values in the recorded user timezone: [IMTranscript2_InUserTimezone], [UserTimezone], [StartDateTimeInUserTimezone], [StartDateInUserTimezone], [StartTimeInUserTimezone], [EndDateTimeInUserTimezone], [EndDateInUserTimezone], [EndTimeInUserTimezone]
9.6.1.59952020-10-05
RI-023994Platform - Storage Management
New SMTP export target field ISPLATFORM([value], [true], [false] optional) to define conditional values based on the value of the platform field
9.6.1.59952020-10-02
RI-024105Platform - Storage Management
New SMTP export metadata field added for HTML formatted emails: [IMTranscript2_HTML] and [IMTranscript2_HMTL_InUserTimezone]
9.6.2.60152020-11-02
RI-024118Platform - Storage Management
Export task page showed end time as 1 January 1970 01:00:00 for ongoing advanced export tasks. From now on it will be blank. Changed both start time and end time column formatting to match the logged in user locale.
9.6.2.60152020-11-04
RI-024874Platform - Storage Management
The Storage Management can use the "Conversation export direct download target folder" setting of the Web Application to temporarily store the files before it is available for download. If this setting is undefined, it will continue to use the local work directory on the server.
9.6.6.62052021-01-13
RI-025009Platform - Storage Management
Storage upload optimization: if too many records couldn't be found in the database or no upload policy was matching, the upload could be stuck or was slow. These records are not processed separately with lower priority, so other/normal records can be processed faster.
9.6.6.62372021-01-21
RI-026246Platform - Storage Management
Dual archiving feature added which allows storing the recordings on 2 different storage targets. The system can upload/copy 2 copies of the same file to 2 different storage targets when this option is enabled. During playback, download, or export, the system will seamlessly attempt to access the files on the first storage target, and if for some reason that is not available, it will turn to the second storage target.
9.6.7.63492021-03-05
RI-027435Platform - Storage Management
Improved SFTP connection error and timeout handling
9.6.11.65422021-04-28
RI-027601Platform - Storage Management
Integration with iTernity iCAS storage middleware. The system automatically applies the retention period on the files, using the iCAS file level retention feature, when the files are moved/uploaded to iCAS. The system uses the standard SMB protocol for file operations.
9.6.11.65412021-04-16
RI-028420Platform - Storage Management
Significant performance improvement in data retention management for the advanced voice (incl. trader voice) data model which makes the deletion process much faster. After this improvement, the system will not try to check for each Media-Only record if there are related CDR-Only records with higher retention during the execution of the deletion, instead it relies on the retention period configuration of the Media-Only records.
9.6.13.67902021-09-22
RI-029154Platform - Storage Management
Stuck video transcoding handling improvements: - Automatic detection of stuck transcoding jobs, creation of alerts, and crash dump - Set stuck transcoding job to an error state, already started ones back to starting state before service restart - Check available free memory before creating a transcoding job
9.6.13.67902021-09-22
RI-027468Platform - Media Streaming
Vulnerable ciphers are disabled by default for the Media Streaming service
9.6.10.64652021-04-28
RI-023630Installer - Servers
Database partitioning can be enabled during installation (in addition to manual script execution)
9.6.0.59742020-08-26
RI-023913Installer - Servers
Microsoft .NET Framework updated to version 4.8 in the install kit
9.6.0.59872020-09-22
RI-024137Installer - Servers
The installer can check if the Windows user running the installer has local administrator privilege which is required for the installation
9.6.3.60432020-11-05
RI-024793Installer - Servers
Updated Web Application dependencies: Puppeteer (v5.4.1), embedded Chromium (v87.0.4272.0) and Node.js (v14.15.0)
9.6.5.61862020-11-06
RI-026221Installer - Servers
Prerequisite Tool improvements: - the password for the sa user for the bundled SQL Server Express can now be configured from the tool - the Microsoft ODBC Driver 17 is a mandatory prerequisite from now on
9.6.7.63372021-02-26
RI-026200Platform - CDR and Archived Content Import
Skype for Business CDR reconciliation optimizations to allow faster execution time on large SfB CDR databases
9.6.6.63182021-02-15
RI-024002Platform - Import
Playback, download, and export support for legacy calls stored on Hitachi Content Platform and migrated from Verint v11
9.6.1.59952020-09-29
RI-024081Platform - Import
New import source support for O2 mobile recording
9.6.2.60152020-10-22
RI-024110Platform - Import
Verint import (dual consolidation) improvements: - changed metadata parsing - added VOX metadata enrichment from CTI records - added ANI, DNIS hidden number handling - added new metadata fields: Cdm Id, External Call Id, Interaction Type
9.6.2.60152020-10-29
RI-024183Platform - Import
Improved recording rule/recorded extension handling to distribute the SQL Server load over time
9.6.4.60722020-11-23
RI-024402Platform - Import
Migration from Verint v15 WFO platform allowing importing of historical recordings: - Support for archived calls only - Supported archive mediums: SMB folder, EMC Centera, Hitachi Content Platform (tapes, DVDs, or any other removable media is not supported) - Storage targets are automatically created based on the archive configuration in Verint - All Verint file formats and codecs are supported: wave file using G.729, G.723.1, or G.726 - Encrypted calls are not supported - Both back office and front office (trader voice) calls can be imported - Users, Groups, and Extension can be migrated from v15.2 systems. The Users' conversation access scope is not migrated. - Migrated calls are assigned to users defined in Verba based on their associated recorded extensions (Trader ID / Extension or Phone Number / SIP URI)
9.6.4.61452020-12-09
RI-026534Platform - Import
Verba import sources now support Azure Blob and File storages when importing data in Verba format
9.6.8.63782021-03-17
RI-026725Platform - Import
When using the Verint Import Source, the Verint Recorder Addresses configuration field can be used to provide the serial number and Verint recorder server FQDN/IP mapping
9.6.9.63912021-03-26
RI-026941Platform - Import
Verint v11 migration process takes user IDs from traders.traderid for front office calls
9.6.10.64562021-04-09
RI-027660Platform - Import
Verba Import Source has a new option to reinterpret/update recorded participant/owner of a call where it is already set
9.6.11.65422021-05-06
RI-027679Platform - Import
Forward proxy support added to Verba import source when Azure Blob Storage is configured
9.6.11.65422021-05-07
RI-028158Platform - Import
In the case of Verint WFO 15.2 import, the shared line extension information (presented as ext#/MAC) is imported as separate fields (From/To and From/To Device fields)
9.6.12.66662021-07-01
RI-028173Platform - Import
O2 mobile call recording import: allow ingestion of long O2 recordings. Long (> 30 minutes) O2 recordings could not be downloaded due to timeout on the O2 side caused by file size.
9.6.12.66662021-07-02
RI-028988Platform - Import
Integration with TeleMessage mobile archiving system to allow the capturing and archiving of WeChat, Whatsapp, TeleMessage Enterprise platforms
9.6.13.67902021-09-22

Fixes

ID
Component
Description
Fixed in
Date
RI-023459Security
Multiple security and vulnerability fixes and configuration changes for the Web Application: - Cross-site scripting (XSS) vulnerability fixes - Weak ciphers removed from TLS configuration - HTTP security headers updated - Web Application logging changes to hide version and code specific information - 3rd party Javascript library updates - Improved secure cookie handling
9.6.0.59662020-08-13
RI-026617Security
Multiple low or moderate Web Application vulnerabilities, affecting specific pages only, are resolved: - SQL Injection in a single API call - Insufficient Cache Controls - Cross-Site Scripting (XSS), Reflected - X-Forwarded-For Injection for API calls - Vertical Privilege Escalation on a few read-only pages
9.6.9.63832021-03-10
RI-025802Recording - Passive
VLAN decapsulation might have missed the last 2 bytes leading to processing problems
9.6.6.62662021-02-08
RI-026239Recording - Passive
False capture interface up/down alerts were raised for network port mirroring based recording due to sub-optimal detection of deadlocks in the capture threads.
9.6.7.63422021-03-02
RI-024241Recording - Proxy
In the case of Cisco SIP Proxy based recording, when the domain part of the TO URI was invalid, the call setup failed due to strict validation of the destination domain of the URIs
9.6.4.61042020-11-26
RI-026606Recording - Cisco
Database records were not created for calls recorded by Cisco network-based recording if the call was started during daylight saving change in UTC
9.6.9.63802021-03-17
RI-027776Recording - Cisco
Technical/native call ID was not stored in the database when JTAPI integration was enabled for Cisco network-based recording
9.6.11.65272021-05-25
RI-028671Recording - Cisco
Verba Cisco JTAPI service stopped recording in very rare circumstances when the Keep-Alive from the Unified Recorder timed out and at the very same time a new Keep-Alive process started
9.6.13.67902021-09-22
RI-028820Recording - Cisco
Cisco Barge and cBarge calls were not associated with Verba users because the JTAPI did not fill the agent ID field
9.6.13.67902021-09-22
RI-024923Recording - Cisco IM
Participant information was not inserted from Cisco IM&P instant message conversations
9.6.6.62272021-01-21
RI-025786Recording - Cisco IM
The service did not properly close the ongoing sessions during restart after an ungraceful shutdown of the service and generated empty records in the database
9.6.6.62652021-02-05
RI-028819Recording - Cisco IM
The Verba Cisco Compliance Service didn't heal properly the stuck conversations of a previous service run. The stored procedure was executed asynchronously with the database cache processing.
9.6.13.67902021-09-22
RI-024073Recording - Lync/SfB
Video was flickering in Acano meetings with Skype for Business interop when only voice recording was enabled for the user
9.6.2.60152020-10-27
RI-024907Recording - Lync/SfB
The SfB Filter service didn't take into account the keep-alive timeout configuration properly. In the case of a congested network, the proxy could have exceeded 5 seconds response window which caused the filter to drop the connection.
9.6.6.62152021-01-18
RI-025699Recording - Lync/SfB
When RTP Proxy with advanced relaying was enabled, the Teams inbound calls to SfB failed to connect if media could reach the Verba proxy
9.6.6.62522021-01-29
RI-026227Recording - Lync/SfB
If the 183/SDP response arrived before INVITE containing refer-by info, the "original called" entity is not detected and the related recording rule did not trigger recording of the conversation on behalf of original called party
9.6.7.63402021-03-01
RI-026228Recording - Lync/SfB
The From Info field was missing (display name of the caller party) if initial the INVITE did not contain the display name but it was available later in the call setup sequence
9.6.7.63402021-03-01
RI-026485Recording - Lync/SfB
Invalid and empty SIP header/field name caused parsing exception and calls could not be recorded for certain Skype for Business 2015 calls after upgrading to 2021 February CU. The reported issue was related to the following call scenario: Mac users were unable to make outbound calls and receive an RGS call.
9.6.8.63752021-03-12
RI-027475Recording - Lync/SfB
In the case of controlled recording, sporadically the Microsoft Teams Bot service made two control database records when the call was started as video. After the call ended, the control record made first, stuck in the ongoing calls.
9.6.10.64662021-04-29
RI-027783Recording - Lync/SfB
The Verba SfB/Lync Filter Service could not start in the case of wrong Internal Number Pattern configuration. The error while the service was trying to compile the regular expression triggerred a service termination. There was no configuration error alert sent by the service before the service termination was initiated.
9.6.11.65382021-05-27
RI-023997Recording - Lync/SfB IM
The Skype for Business IM recorder could not create an XML file for the conferences when direct export/upload configuration was used
9.6.1.59952020-09-30
RI-028340Recording - Lync/SfB IM
The SfB/Lync IM Recorder Service's cache processing procedure tried to process the whole cache folder instead of processing it in batches.
9.6.13.67902021-09-22
RI-024027Recording - Microsoft Teams
HSTS response headers were missing for HTTPS listeners on 9440 and 10100 ports for the Microsoft Teams Bot service
9.6.1.59952020-10-06
RI-024028Recording - Microsoft Teams
When multi-tenancy was disabled, the Microsoft Teams Bot service used the 0000 environment ID and the recordings were uploaded into the 0000 folder
9.6.1.59952020-10-13
RI-024138Recording - Microsoft Teams
Microsoft Teams Bot service was installed with the wrong default value for the Recording Notification setting and recording was still controlled by the system while it should not have been
9.6.2.60222020-11-05
RI-024177Recording - Microsoft Teams
Transcoding application share recording to MP4/WMV might miss the voice part after the application share is stopped
9.6.4.60722020-11-24
RI-024181Recording - Microsoft Teams
The phone numbers were not parsed properly in the case of conference calls. Therefore, the phone numbers were not added to the participants list.
9.6.4.60722020-11-24
RI-024187Recording - Microsoft Teams
In the case of controlled recording, the ongoing control entry stuck when the call was put on hold and resumed or the P2P call was escalated into conference.
9.6.4.60722020-11-23
RI-024200Recording - Microsoft Teams
The Microsoft Teams Bot Service didn't take into account the recording rule configuration of the delegator in the case of delegated calls. Now the bot service applies the recording rules defined for the delegator for the delegated calls answered or initiated by a delegate.
9.6.4.60722020-11-18
RI-024236Recording - Microsoft Teams
On-premise Skype for Business users were not parsed by the Teams Bot Service. The users were not added as conference participants and caused missing CDR info in the case of P2P calls.
9.6.4.61042020-11-27
RI-024243Recording - Microsoft Teams
When a user configured for recording only audio in Verba, the recording notification was shown in the case of app share only calls too.
9.6.4.61042020-11-25
RI-024687Recording - Microsoft Teams
The Microsoft Teams Bot service automatically started controlled recording if participant change update received during the period when the recorded user has not yet joined but the bot was already part of the call.
9.6.5.61782020-12-23
RI-024826Recording - Microsoft Teams
When the bot was not able to answer a call because of missing parts of the call invite, the bot didn't register the call as a non-answered call. It caused the bot to still allocate resources for handling the call and the allocated resources were not disposed until the service was restarted.
9.6.5.61912021-01-07
RI-024827Recording - Microsoft Teams
Handling of Teams tenant IDs was case sensitive. If the tenant ID came from the environments.xml file then it was uppercase which caused that the bot to skip metadata retrieval (participant UPN lookup) from Azure AD because it didn't find the graph client for the user's tenant ID from the signaling which was lower case.
9.6.5.61912021-01-07
RI-025921Recording - Microsoft Teams
The video stream of the guest users was ignored and the bot never subscribed to them
9.6.6.63022021-02-17
RI-026103Recording - Microsoft Teams
The Microsoft Teams Bot service didn't release resources properly, which caused that the bot could exceed the video socket limit of the Microsoft SDK (1000). After exceeding the limit, the service could not answer calls with video and application share modalities and raised alerts.
9.6.6.63122021-02-23
RI-026735Recording - Microsoft Teams
The Verba Microsoft Teams Bot Service took the Advanced API configuration into account for recorder connections. When the Advanced API was turned off the Verba Microsoft Teams Bot Service didn't start a secure listener and the Verba Unified Recorder Service could not establish a TLS connection.
9.6.9.63952021-03-25
RI-026913Recording - Microsoft Teams
The Verba Microsoft Teams Bot service didn't clear the service state on graceful service stop which could lead to service stuck state if there were ongoing calls before the service restart
9.6.9.64102021-03-29
RI-026917Recording - Microsoft Teams
PSTN participant numbers were not stored in the case of peer-to-peer calls if there was no Teams tenant ID presented
9.6.9.64102021-03-25
RI-026921Recording - Microsoft Teams
The recording notification banner was inconsistent in the case of controlled and controlled auto start scenarios. When the controlled recording was started automatically and stopped by the user the banner didn't reflect recording state properly. It didn't change to stopped state.
9.6.9.64102021-03-09
RI-026932Recording - Microsoft Teams
Microsoft Teams Media SDK generated invalid timestamps for audio leading to media processing issue and continuously growing audio files
9.6.10.64602021-04-06
RI-026942Recording - Microsoft Teams
The Microsoft Teams Bot service could crash when the recorder connection went down. The service ran into an unhandled exception when it tried to assign a new recorder to an ongoing call.
9.6.10.64602021-04-08
RI-027316Recording - Microsoft Teams
When a user started a call with audio modality and added video or application sharing modality later, the Verba Microsoft Teams Bot Service started the controlled recording automatically.
9.6.10.64602021-04-20
RI-027371Recording - Microsoft Teams
Microsoft Teams voice stream might have got out of sync and became inaudible after a while in case of long recordings
9.6.10.64602021-04-27
RI-027652Recording - Microsoft Teams
The Verba Microsoft Teams Bot service did not provide the source or destination caller IDs, when it identified the recorded user's tenant as a non-provisioned tenant.
9.6.11.65422021-05-05
RI-027750Recording - Microsoft Teams
The Verba Microsoft Teams Bot service didn't set the direction of the conversation properly in the case of Luware Nimbus PSTN calls.
9.6.11.65102021-05-14
RI-027752Recording - Microsoft Teams
In the case of controlled recording, the Verba Microsoft Teams Bot service created an additional control record when federated user or guest user entered the meeting.
9.6.11.65102021-05-14
RI-027766Recording - Microsoft Teams
The Verba Microsoft Bot service didn't look up the CurrentUser's certificate store for trusted CA at startup. Therefore the service could not start when a publicly trusted certificate was configured as a Verba Server Certificate.
9.6.11.65232021-05-20
RI-027785Recording - Microsoft Teams
The Verba Microsoft Teams Bot service automatically started controlled recordings in the case of specific extension configuration. When the 'Record Only If External Use is Participating' option was enabled the dominant speaker changed event triggered the controlled recording.
9.6.11.65382021-05-26
RI-027912Recording - Microsoft Teams
The guest users' video content was not recorded due to a video subscription issue.
9.6.12.66662021-06-11
RI-027913Recording - Microsoft Teams
Screen share recording has stopped when a participant has left the meeting, and screen share recording did not continue for recorded users after that point.
9.6.12.66662021-06-11
RI-028106Recording - Microsoft Teams
When an extension was configured to record only in the case of an external user's presence, the video and application share streams were not recorded at all.
9.6.12.66662021-06-28
RI-028248Recording - Microsoft Teams
In the case of an unknown caller ID or UPN, the Phone Number field in the participant information contained invalid characters when non-Latin characters were used for the display name of the participant
9.6.12.66662021-07-08
RI-028446Recording - Microsoft Teams
When call splitting was configured, participant information was only available for the last segment in the database
9.6.13.67902021-09-22
RI-026780Recording - Microsoft Teams IM
In multi-tenant deployments, where multiple providers were configured in the Unified IM Recorder service, the instant messages were stored in other tenants too, in addition to the right tenant
9.6.9.64012021-03-31
RI-027471Recording - Microsoft Teams IM
When a Microsoft Teams tenant was moved from one Verba environment/tenant to another, the ongoing chat messages were kept stored in the original environment, only new conversations were recorded correctly to the new environment.
9.6.10.64652021-04-28
RI-027778Recording - Microsoft Teams IM
The Verba Unified IM Recorder Service might stuck in processing maximizing CPU and memory utilization in the case of invalid HTML content was received.
9.6.11.65302021-05-26
RI-028174Recording - Microsoft Teams IM
The message processing queue was stuck when federated Skype for Business users were participating in the chat room
9.6.12.66662021-07-02
RI-028251Recording - Microsoft Teams IM
The attachment download was not case insensitive and failed to download attachments from SharePoint when the file extension was changed to lowercase
9.6.12.66662021-07-12
RI-028331Recording - Microsoft Teams IM
Stickers could not be downloaded and archived for P2P and group chats
9.6.13.67902021-09-22
RI-028335Recording - Microsoft Teams IM
Unnecessary Microsoft Graph webhook subscriptions when the system attempted to subscribe to an already exiting subscription
9.6.13.67902021-09-22
RI-029358Recording - Microsoft Teams IM
Attachments could not be accessed for standard users, only for system supervisors
9.6.13.67902021-09-22
RI-024033Recording - Avaya
Preferred Codecs list was incorrect in the hint of the Avaya Recorder / Avaya DMCC / Preferred Codec server configuration
9.6.1.59952020-10-12
RI-026634Recording - Avaya
The Avaya DMCC/JTAPI Service did not register subsequent extensions if an extension in the list could not be registered due to "Softphone must be enabled" error was received
9.6.9.63842021-03-21
RI-028673Recording - Avaya
The Avaya DMCC service cannot record after the Unified Recorder service was restarted meanwhile the Avaya DMCC service was communicating with it
9.6.13.67902021-09-22
RI-025887Recording - Centile
The duration of the stereo recordings (AU files) was double the length of the call
9.6.6.62782021-02-10
RI-027584Recording - Centile
Centile Connector/AU audio file processing: the media length was calculated incorrectly if the file was bigger than 6.7 Mbytes (stereo) or 13.4 Mbytes (mono)
9.6.11.65412021-05-03
RI-024122Recording - Unified Call Recorder
If the Recording Director and the Media Recorder is separated and either File Share, Poll/Q&A, Whiteboard or SMS modality was enabled in addition to Voice/Video or Screen Share (but not all modalities), then the recording rule became invalid end the call was not recorded at all. Alerts were raised with "Cannot register call on media recorder" error.
9.6.2.60212020-11-04
RI-024700Recording - Unified Call Recorder
Recovering ongoing calls after recording server crash could not determine the end time of the calls and inserted CDRs with 0 duration which prevented the user from playing back the recordings using the CDRs for trader voice recordings (playback only worked for the media records)
9.6.5.61792021-01-04
RI-024785Recording - Unified Call Recorder
Unified Call Recorder applied call segmentation for video and screen/application share recordings, which led to keyframe/video decoding issues after splitting the record into a new one. Call segmentation is disabled for video and screen/application share streams.
9.6.5.61852021-01-07
RI-025013Recording - Unified Call Recorder
The Unified Call Recorder service no longer creates new records at video escalation when the audio format is set to VMF
9.6.6.62372021-01-15
RI-025906Recording - Unified Call Recorder
If VOX/VAD triggered recording generated invalid start time, it could have led to Unified Call Recorder service crash and memory leak at call segmentation. The system generated call processing and low memory alerts.
9.6.6.62982021-02-15
RI-028301Recording - Unified Call Recorder
In the case of dial-in recording, the From/To Info fields (line display name) was not parsed and stored
9.6.12.66662021-06-28
RI-028426Recording - Unified Call Recorder
Using the E-Dialer integration, the Cisco master call and any non trader-voice recordings where VOX was enabled might have triggered "no media/RTP received" call processing alerts if the call was just pure silence and so no media file was created
9.6.13.67902021-09-22
RI-023895Recording - IPTrade
IPTrade turret based playback was very slow due to the wrong execution plan compiled by SQL Server
9.6.0.59872020-09-24
RI-027647Recording - IPTrade
BT IP Trade turret side playback list recording action was very slow
9.6.11.65412021-05-05
RI-024098Recording - BT ITS
If a second device connected to the same call on the turret, the recorder stopped recording on the first device
9.6.4.61542020-10-19
RI-024154Recording - BT ITS
BT ITS LDAP provisioning queries could take too much time during service start which could prevent the service from starting as Windows considered it a service failure after a timeout and killed the process prematurely
9.6.3.60432020-11-16
RI-025011Recording - BT ITS
If BT ITSLink server sent the dialed number multiple times, the dialed digits were concatenated and appeared multiple times
9.6.6.62372021-01-21
RI-027896Recording - BT ITS
BT ITS CTI recorder might crash if CLI info was received on not IP recorded line or VR ID was not set for recording. It affects v9.6.11 or later.
9.6.12.66662021-06-05
RI-027907Recording - BT ITS
If BT ITSLink server closed the connection, the Recording Director could spike one CPU core and delay the reconnection attempt for 60 seconds. This could lead to the loss of metadata.
9.6.12.66662021-06-09
RI-024786Recording - Speakerbus
In some case, the system sent a false call processing error alerts if a device change happened on the line
9.6.5.61852021-01-07
RI-024100Recording - Cloud9
Cloud9 Recording System API integration did not work and C9 clients were unable to upload data to the Recording Server (affects 9.6.0.5983 or later builds only)
9.6.2.60152020-10-15
RI-024182Recording - Cloud9
In case of short or 0 length Cloud9 Ogg media files the import service could not import the recording using the Cloud9 Call Data API
9.6.4.60722020-11-24
RI-024185Recording - Cloud9
Cloud9 Call Data API import did not use the Work Folder setting and used the default application work folder instead for media files
9.6.4.60722020-11-23
RI-024201Recording - Cloud9
The Enable Media Filtering Workaround could not be changed. From now on it is disabled by default because itis no longer needed due to Cloud9 Call Data API changes.
9.6.4.60722020-11-18
RI-024787Recording - Cloud9
Cloud9 Recording System API based integration did not work intermittently due to an uninitialized connection timeout
9.6.5.61862021-01-07
RI-028249Recording - Cloud9
Cloud9 Call Data API: when a custom work folder was configured, the Import Service used a bad media path and failed to import the data
9.6.12.66662021-07-09
RI-028259Recording - Cloud9
Cloud9 Recording System API based import issues resolved: - import did not work when multiple C9 clients were uploading the media file for the same call (shout down) at the same time - in the case of database errors after database failover, database entries were multiplicated - improved work folder cleanup process - improved network connection error handling - participant information was missing in some call scenarios
9.6.12.66662021-07-13
RI-028826Recording - Cloud9
Cloud9 Call Data API Import Source was looking for the wrong metadata template
9.6.13.67902021-09-22
RI-026230Recording - Desktop
The desktop agent application did not update the status icon after the connection with the Web Application was recovered
9.6.7.63402021-03-01
RI-026596Recording - Desktop
The Auto-Pause configuration was not taken into account properly when the screen was still recorded after the call has ended due to wrap up timer configuration
9.6.8.63782021-03-03
RI-027755Recording - Desktop
Desktop Agent muted recording unexpectedly when the Auto-Pause Recording on URL setting contained an empty line
9.6.11.65102021-05-14
RI-028977Recording - Dial-in
Phone-based playback did not work imported calls where the Audio Codec ID was not set
9.6.13.67902021-09-22
RI-025678Recording - SIPRec
Metaswitch Perimeta: caller/callee was swapped in case of interconnecting calls
9.6.6.62452021-01-28
RI-026110Recording - SIPRec
After a call was put on hold, the Unified Call Recorder stopped recording the call and if the call was resumed, the system did not continue recording the call. The issue affects SIPREC integrations using the generic SIPREC implementation (Sonus SBC, Avaya ESBC, Cisco CUBE).
9.6.6.63122021-02-22
RI-023943Recording - Symphony
Screen/application share modality was not properly determined for SIPREC sessions and the system stored these streams as video recordings
9.6.0.59872020-08-27
RI-024005Recording - Symphony
Symphony calls were not assigned to users
9.6.1.59952020-09-29
RI-024302Recording - Genesys
The Cisco JTAPI Service tried to connect to a T-Server with Backup role
9.6.4.61342020-12-03
RI-023605UI - Web Interface
The player buttons FWD and END, didn't work properly. If not applicable the button will be grayed out.
9.6.0.59742020-08-25
RI-023609UI - Web Interface
Video playback area in Internet Explorer didn't fit properly to screen size. In some cases, when the screen resolution was under 1080p, it overfleww into the conversation details section.
9.6.0.59742020-08-25
RI-023902UI - Web Interface
Selecting the Excel export option on the Alert Management page resulted in a blank page
9.6.0.59872020-09-24
RI-023909UI - Web Interface
Send URL feature did not work
9.6.0.59872020-09-24
RI-023910UI - Web Interface
User group membership will not be updated when the user is primarily synchronized by an AD Profile which should not synchronize users. Membership update incorrectly happened when the user started to be merged by another AD Profile.
9.6.0.59872020-09-23
RI-023915UI - Web Interface
Audio segment download in player did not work for trader voice recordings with stitched media
9.6.0.59872020-09-22
RI-023918UI - Web Interface
Search was very slow for trader voice conversations due to the wrong execution plan compiled by SQL Server
9.6.0.59872020-09-21
RI-023985UI - Web Interface
Ad hoc transcoding jobs were executed by any of the Media Repository / Application Servers (whichever has seen the job first) and the transcoded video was not available for playback on the server where the user was connected to
9.6.1.59952020-10-07
RI-024010UI - Web Interface
The Audit Log details were double-escaped, so "->" strings and HTML tables (Search parameters) were garbled
9.6.1.59952020-09-25
RI-024056UI - Web Interface
The scroll bar was missing in the conversation metadata tab in the player
9.6.2.60152020-10-20
RI-024063UI - Web Interface
When using a direct link to open the Conversation Details, the Protect icon did not work and the Related Calls icon was visible even if it was not working (and now removed)
9.6.2.60152020-10-07
RI-024070UI - Web Interface
The selected Identity Providers were displayed as "Available" too when cloning an existing Role
9.6.2.60152020-10-27
RI-024143UI - Web Interface
If a user did not have the "Customize Conversation Export Target Folder" role then updating an advanced export configuration page caused an error
9.6.3.60432020-11-09
RI-024149UI - Web Interface
Users were able to bypass playback restriction when the multiple playback feature was used
9.6.3.60432020-11-12
RI-024166UI - Web Interface
Home Page setting did not work with Integrated Windows Authentication (IWA)
9.6.4.60622020-11-17
RI-024227UI - Web Interface
Bulk Media download was available even if the user had no "Download a Conversation" permission
9.6.4.61042020-11-30
RI-024235UI - Web Interface
The video player's full-screen button didn't work in browsers other than Internet Explorer. The minimize button on the player's title bar disappeared in case of any error.
9.6.4.61042020-11-27
RI-024239UI - Web Interface
Copy URL icon was not shown on conversations
9.6.4.61042020-11-26
RI-024242UI - Web Interface
In the case of text search, the Unicode characters were not encoded properly in the transcript view
9.6.4.61042020-11-25
RI-024415UI - Web Interface
Advanced Export was visible on the Search screen even if the user did not have the "Conversations List Export" permission. The server threw an error when the user tried to use it without a permission.
9.6.4.61452020-12-07
RI-024417UI - Web Interface
Cloud9 Call Data API import source configuration page did not work
9.6.4.61452020-12-04
RI-024607UI - Web Interface
The newly created users were not put into the groups which were selected on the AD profile's New Users' Properties when the Synchronize Security Groups checkbox was not turned on.
9.6.4.61542020-12-10
RI-024625UI - Web Interface
The Cisco Finesse gadget could not authenticate with HTTP Basic authentication method.
9.6.5.61692020-12-23
RI-024788UI - Web Interface
Media files bigger than 2 GB cannot be downloaded and played back from the web application
9.6.5.61862021-01-07
RI-024789UI - Web Interface
The e-mail generated by the Send URL feature displays question marks for non-ASCII characters
9.6.5.61862021-01-06
RI-024831UI - Web Interface
If the user did not have "Customize Conversation Export Target Folder" permission, then the Direct Download feature did not work
9.6.5.61942021-01-08
RI-024832UI - Web Interface
The bulk media download HTML file playback does not work when the exported media file name starts with one of the following characters: +, -, @, =, ;
9.6.5.61942021-01-08
RI-025781UI - Web Interface
In the case of large voice transcripts (approx. 20k words), the search hit highlight could not process the transcript, therefor the transcript didn't contain any highlighted words.
9.6.6.62652021-02-05
RI-025936UI - Web Interface
Video transcoding did not start in Azure environments because the hostname resolved by the web application did not match the hostname resolved by the Storage Service
9.6.6.63052021-02-18
RI-025938UI - Web Interface
When a Controlled auto-start recording started, only the Administrator was able to stop the recording
9.6.6.63052021-02-18
RI-026238UI - Web Interface
The Cisco Finesse gadget didn't query the ongoing calls properly because it took the extension and user criteria from the 'Search' tab into account which could hold wrong data because the browser considered them as auto-fill fields
9.6.7.63412021-03-01
RI-026241UI - Web Interface
When the Active Directory Synchronization had a custom schedule in a redundant deployment, and Media Repository 1 executed the sync, then Media Repository 2 computed the wrong "Next Time of Execution" and locked the database for a few hours unnecessarily
9.6.7.63422021-03-01
RI-026671UI - Web Interface
The User CSV Export writes a leading quote (') character to avoid CSV injection for extensions starting with a + sign, but that leading quote was not removed during CSV User Import
9.6.9.63882021-03-24
RI-026672UI - Web Interface
The CSV user export did not differentiate the "User/Agent ID" type extensions
9.6.9.63882021-03-24
RI-026673UI - Web Interface
Recording audit checkboxes were updated: - Recorded conversations (media file exists, recording failed flag is not set, end cause is not Caller Gave Up, Busy, Unobtainable, Error, and there is no media error) - Recorded conversations with incorrect media (media file exists, recording failed flag is not set, end cause is not Caller Gave Up, Busy, Unobtainable, Error, and there is a media error) - Not recorded conversations due to error (media file does not exist and end cause is not Caller Gave Up, Busy, Unobtainable, or recording failed flag is set or end cause is Error) - Not answered conversations (end cause is Caller Gave Up, Busy, Unobtainable)
9.6.9.63882021-03-24
RI-026927UI - Web Interface
The silent monitoring button on the Agent View page was added multiple times for each on-hook agent.
9.6.10.64602021-04-08
RI-027323UI - Web Interface
Playback of a Desktop Screen recording was audio-only after the VF file converted to MP4 and got deleted
9.6.10.64562021-04-26
RI-027334UI - Web Interface
Background Tasks page End Time column was converted to the user's timezone two times
9.6.10.64562021-04-23
RI-027586UI - Web Interface
After the VF file was removed by a delete policy, the remaining audio record could not be played back from any browsers except Internet Explorer. This was because the Video Codec ID was still filled in, and so the streamer service was not being used to transcode the audio to a format playable by Chrome.
9.6.11.65412021-04-30
RI-027642UI - Web Interface
Active Directory Synchronization: groups not re-added after the user is re-activated in the same Active Directory Synchronization Profile
9.6.11.65412021-05-04
RI-027644UI - Web Interface
Minor issues fixed: - When the wrong password was entered, then a blank screen was shown - Refresh (F5) always forwarded to the main screen - When using a direct URL and not logged in to the system, then two player frames were shown
9.6.11.65412021-05-03
RI-027653UI - Web Interface
Microsoft Teams Instant Messages could be duplicated when searching for a text for a long time period
9.6.11.65412021-05-06
RI-027657UI - Web Interface
Microsoft Teams Instant Message edit history could not be displayed
9.6.11.65412021-05-06
RI-027749UI - Web Interface
The Verba Web Application Service could not send emails after upgrading Java from jdk-11.0.8+10 to jdk-11.0.11+9 due to wrong default TLS configuration for Java Mail API
9.6.11.65102021-05-14
RI-027753UI - Web Interface
The "Conversation export direct download target folder" server configuration was not used when the user did not have the "Customize Conversation Export Target Folder" permission, so the files were exported to the local disk
9.6.11.65102021-05-14
RI-027772UI - Web Interface
The Verba Finesse Gadget didn't fallback to the legacy API authentication method in the case of Verba Web Application older than version 9.6.
9.6.11.65262021-05-21
RI-027882UI - Web Interface
The Data Management and Export features' Duration Interval filter threw error when there were calls longer than 24 days
9.6.11.65452021-06-01
RI-027885UI - Web Interface
The transcription did not load into the player when the user did not use the Text Search
9.6.11.65462021-06-02
RI-028079UI - Web Interface
Recording rules were always saved to the logged in user's Environment, instead of the selected one (when the user was a Reference Environment administrator)
9.6.12.66662021-06-16
RI-028080UI - Web Interface
When the IWA authentication was used, then the Session Monitor stored the wrong Session ID and so after a Logout and Login, the User saw the "Other user(s) have been already logged in to the system with the same login id" message
9.6.12.66662021-06-16
RI-028157UI - Web Interface
The system allowed duplicating the built-in metadata templates used by the recorder and import services, and it also allowed adding new fields to these templates which caused errors in the respective services (these changes are no longer allowed)
9.6.12.66662021-07-01
RI-028160UI - Web Interface
The Reports / Create New Report menu showed a blank page when using Internet Explorer
9.6.12.66662021-06-29
RI-028234UI - Web Interface
The private flag could be lost when it was set on a conversation that was recorded in the last 24 hours
9.6.12.66662021-07-06
RI-028410UI - Web Interface
The meta XML file for CDR-Only records could not be downloaded in the Conversation Detail File format section, and if the files were stored on non-SMB storage, then no files were shown at all in the File format section.
9.6.13.67902021-09-22
RI-028411UI - Web Interface
Signature verification showed two false errors for trader voice CDR-Only records when the files were stored on non-SMB storage
9.6.13.67902021-09-22
RI-028441UI - Web Interface
The fetch following or previous SMS messages did not work in the Conversation View
9.6.13.67902021-09-22
RI-028443UI - Web Interface
The Conversation Export Metadata Fields always showed the Reference Environment's Metadata Fields in a Multi-Tenant deployment
9.6.13.67902021-09-22
RI-028816UI - Web Interface
Error code 400 was received after opening a new tab when Extensions, Users or Alerts List were clicked (Open in New Tab or CTRL + Click)
9.6.13.67902021-09-22
RI-028827UI - Web Interface
Audit Log Export did not work when there were special characters (0x0) in the detail message (e.g. Microsoft Active Directory error message). The ASCI 0 character will not be inserted from now on.
9.6.13.67902021-09-22
RI-028861UI - Web Interface
When searching for Metadata Fields in the Search feature with a negative operation (Not equal to, Does not match a value in the list, Not like), then the calls where the metadata value did not exist were not shown
9.6.13.67902021-09-22
RI-028925UI - Web Interface
Download of a shared file did not work when there was a + sign in the file name
9.6.13.67902021-09-22
RI-028940UI - Web Interface
Import from Every Source checkbox on the Extension configuration page did not work when no import source was selected and the goal was to not use the extension for any import source configured
9.6.13.67902021-09-22
RI-029354UI - Web Interface
The Authorization Request could not be approved when the requester user requested access to their own conversations, it displayed an "Ooops!" error screen.
9.6.13.67902021-09-22
RI-021162UI - Waveforms
Waveform always showed on peak when static there was noise in the call. Now data is normalized by the visualization script.
9.6.0.59442020-06-09
RI-026509UI - Waveforms
Selective audio download did not work when the wave file is on a network drive with Custom Credentials
9.6.8.63762021-03-16
RI-023937UI - Reporting
The Conversation Access Event Details report supported the English language only
9.6.0.59872020-09-14
RI-024152UI - Reporting
The Server Capacity report did not work and the system generated 0kb reports (no report output) with exceptions in the log files
9.6.3.60432020-11-16
RI-024229UI - Reporting
Server Configuration with Profile report: when there were multiple profiles for the same role, then only one of the profiles' settings were shown
9.6.4.61042020-11-30
RI-024230UI - Reporting
Recorded Users and Extensions report did not show the Distinct Total value in case of the CSV format
9.6.4.61042020-11-30
RI-024399UI - Reporting
Dashboard snapshot schedule was not correct when the creation time converted to UTC resulted in a longer time then 24 hours
9.6.4.61452020-12-09
RI-024400UI - Reporting
Dashboard snapshot schedule was late when the creation time converted to UTC resulted in a negative time. For example, 7:30 AM Hong Kong time should be created at -0:30AM UTC. That was not converted to 11:30PM.
9.6.4.61452020-12-09
RI-024823UI - Reporting
Quality Management Form Custom Field titles and values were not saved
9.6.5.61912021-01-08
RI-024857UI - Reporting
Agents Evaluation Details report's CSV format contained the column headers multiple times
9.6.6.62042021-01-12
RI-027318UI - Reporting
The Recording Server Utilization dashboard widget loaded very slowly if Microsoft Teams instant message capture was used
9.6.10.64472021-04-21
RI-027940UI - Reporting
Minor reporting problems with a few Quality Management and the License Usage Summary reports: - Quality Management reports: when the Available Points or the Weight of a question is zero, then the report is not generated (0 byte file) - License Usage Summary report: when the Database Server's default collation is different from the Verba database's collation, then the report is not generated (0 byte file)
9.6.12.66662021-06-10
RI-029350UI - Reporting
Group name was missing from Users Roles Permissions and Groups report in XLS format
9.6.13.67902021-09-22
RI-028855Solution - Ethical Wall
In the case of Contact List filtering, the Verba SfB/Lync Communication Policy Service did not handle the large requests properly which resulted in a search error in the Skye for Business clients.
9.6.13.67902021-09-22
RI-026761Solution - Quality Management
Non-numeric values were not filtered out in a few Quality Management reports so those reports did not work when a non-numeric value was written to the scorecard. Affected reports are: - Agents Evaluation Details - Agents Skills Performance Summary - Average Score by Question - Question Score Details - Skills Performance Summary - Skills Performance Trend
9.6.9.64002021-03-30
RI-028147Solution - Quality Management
Quality Management agents could not open their own scorecard
9.6.12.66662021-06-29
RI-024702Solution - Speech Analytics
If the case of video recording with mixed audio, the voice transcript included everything twice
9.6.5.61792021-01-04
RI-027737Solution - Speech Analytics
Speech transcription did not work since 9.6.7 due to SQL query errors
9.6.11.65422021-05-11
RI-024231Platform - Announcement
In the case of Cisco announcement, if callee was forwarded from one to other recorded participant, multiple announcements were played (one for each hop)
9.6.4.61042020-11-30
RI-027780Platform - Announcement
Improvements for outbound Cisco Announcement: - Call setup time is significantly decreased - Workaround for intermittent built-in-bridge race condition in case of Cisco Jabber endpoints which might have caused one-way audio recording or no recording at all (Cisco related issue)
9.6.11.65312021-05-26
RI-028447Platform - Announcement
The Skype for Business announcement white list considered the PSTN numbers as internal numbers because of the domain part appended by the mediation server
9.6.13.67902021-09-22
RI-028825Platform - Announcement
In the case of delegated Skype for Business call and outbound announcement configuration, the outbound call leg made by the Verba Lync/SfB Announcement service wasn't impersonated on behalf of the user.
9.6.13.67902021-09-22
RI-023979Platform - API
Provisioning API getStoragePolicies and getStoragePolicy returned a StorageFolder even when the policy had no Storage Folder (then returned a dummy folder with id 0)
9.6.1.59952020-10-08
RI-024613Platform - API
SearchCalls API threw an error when searching for ongoing calls without the end time parameter
9.6.4.61562020-12-13
RI-024846Platform - API
When a User was created via the Provisioning API without a password, then the web application threw an error
9.6.5.61972021-01-11
RI-025691Platform - API
Import REST API did not work intermittently due to an uninitialized connection timeout
9.6.6.62492021-01-29
RI-025726Platform - API
Import REST API fixes and improvements: - the API did not work when user-based authentication was enabled and the user was created with the new password storing/hashing method - the API restricts access for users created in the reference environment/tenant only - the work folder was not cleaned up after successful import - a new work folder setting is introduced
9.6.6.62592021-01-29
RI-027881Platform - API
The Provisioning API v3 GetUsers call did not return the Roles of the Users
9.6.11.65452021-06-01
RI-027894Platform - API
The Provisioning API did not return the expired Users' group memberships
9.6.12.66662021-06-04
RI-027980Platform - API
The Provisioning API passwordExpires was not written into the database, and when querying the User, the workflowId and retentionDays attributes were set to 0 instead of null
9.6.12.66662021-06-15
RI-028096Platform - API
Provisioning API v3 - Extension update without modalities caused NullPointException
9.6.12.66662021-06-22
RI-028674Platform - API
The Business API did not return archived conversations
9.6.13.67902021-09-22
RI-024093Platform - Configuration
Server certificate validation timeout was too short in some rare cases and validation failed during the startup of the following services: Web Application Service, Cisco JTAPI Service, Cisco Compliance Service, Avaya DMCC/JTAPI Service
9.6.2.60152020-10-20
RI-024233Platform - Database
The upload process prevented Maintenance Job from running and vice versa
9.6.4.61042020-11-27
RI-024685Platform - Database
The following deletion functions did not work since 9.6.4.6145: - On-Demand call deletion after call buffer expires (Storage Service) - Deletion of CDRs where there was no voice activity for trader voice recording (Unified Call Recorder Service) - Deleting records during deduplication (Storage Service) - Manual deletion on the Web UI (Web Application Service) In all cases, the related services raised an alert on failed deletion attempts.
9.6.5.61782020-12-31
RI-027956Platform - Database
The call was not associated to the User when the participants were updated at the same time when the record was finished so moved to the finished database table.
9.6.12.66662021-06-14
RI-028211Platform - Database
Recorder and Import service-specific built-in metadata fields were inserted into the reference environment/tenant in the case of multi tenant deployments, instead of the users' tenant
9.6.12.66662021-07-02
RI-024112Platform - Licensing
License Usage was not counted after a Web Application restart until the daily license check or visiting the license screen
9.6.2.60152020-10-22
RI-024689Platform - Licensing
License: Media Monitor (CDR Reconciliation) check counted non-voice Extensions too
9.6.5.61782020-12-22
RI-024141Platform - Media Processing
Transcoded MSRDP based Skype for Business screen/application share recording could not be played back (showed green screen) if the original stream (shared window) height was an odd number
9.6.3.60432020-11-09
RI-026260Platform - Media Processing
Transcoding desktop screen captures (.vf files) did not work
9.6.6.63492021-03-04
RI-028274Platform - Media Processing
Very short (<500msec) video/screen share transcoding might have stuck
9.6.12.66662021-07-14
RI-024007Platform - Monitoring
Unsupported SNMP v3 is removed from configuration dropdown and the default value is to version 2
9.6.1.59952020-09-28
RI-024837Platform - Monitoring
When an SNMP trap was sent successfully it was inserted into the database with unsuccessful SNMP sending status
9.6.5.61952021-01-11
RI-026746Platform - Monitoring
The "Policy Continues After Error" alert had the wrong alert ID set in the storage service
9.6.9.63972021-03-26
RI-027880Platform - Monitoring
System Monitor service at detail level logged the credentials for the API user requests (injecting alerts into the database)
9.6.11.65442021-05-31
RI-023603Platform - Storage Management
Export and import of Skype for Business IM conversations did not work when IM transcript file creating was enabled in the recorder service
9.6.0.59742020-08-25
RI-023896Platform - Storage Management
Media stitching for playback and export was very slow for trader voice conversations due to the wrong execution plan compiled by SQL Server
9.6.0.59872020-09-24
RI-023898Platform - Storage Management
Advanced Export and Export Policy could show invalid records count at the end of the task if new, matching records were inserted to the database while the task was running
9.6.0.59872020-09-24
RI-023899Platform - Storage Management
Advanced Export manifest file contained the temporary file path of the media files if the file was to be transcoded or stitched
9.6.0.59872020-09-17
RI-023982Platform - Storage Management
Recent than/older than filtering for advanced export did not work as expected because the reference date was based on the current time and not on the export schedule
9.6.1.59952020-10-08
RI-023988Platform - Storage Management
In case of data was modified by other processes during executing the deletion transaction in the deduplication policy, the failed transaction was not retried, instead of alert was raised and processing was reattempted only at the next policy run
9.6.1.59952020-10-06
RI-023989Platform - Storage Management
Policy-based upload ignored policy level retention period setting if Prefer User Retention was enabled and the value was empty
9.6.1.59952020-10-06
RI-023999Platform - Storage Management
On-demand conversation processing SQL queries might fail after a long idle time. Alerts were raised and queries were executed again.
9.6.1.59952020-09-30
RI-024014Platform - Storage Management
Recorded Party field parsing caused "stoi argument out of range" errors in the generic import
9.6.1.59952020-09-25
RI-024023Platform - Storage Management
Policy based export ignored the "Encrypt XML metadata" checkbox on UI and encrypted all the time when the media was encrypted
9.6.1.59952020-10-14
RI-024025Platform - Storage Management
Duplicate email attachments were sent during policy-based SMTP export of voice calls when the email template had attachments configured.
9.6.1.59952020-10-14
RI-024032Platform - Storage Management
The system showed wrong export statistics for Bloomberg Voice on the user interface (multiple tasks were checking the same storage target level files and updating their task status). Improved error and SFTP handling.
9.6.1.59952020-10-12
RI-024045Platform - Storage Management
SMTP export sent extra emails while checking for transcipt (.vtr) file
9.6.1.59952020-10-14
RI-024069Platform - Storage Management
The wrong file was played back in some cases in the player in case of Verint v11 migrated calls which were stored on Hitachi Content Platform
9.6.2.60152020-10-28
RI-024139Platform - Storage Management
Connection failed to EMC Centera when secondary server was configured due to wrong connection string parsing
9.6.3.60432020-11-09
RI-024163Platform - Storage Management
When the user tried to replay a media for a trader voice call which was not yet placed on the storage that caused the media to be unplayable for any further attempts
9.6.4.60622020-11-18
RI-024171Platform - Storage Management
Instant message export via SMTP did not work when the default attachment content type was changed. The content type of the email body was always text/html even in the case of plain text content (e.g. line breaks were ignored).
9.6.4.60622020-11-16
RI-024624Platform - Storage Management
The priority of the upload policies was not properly handled and in case multiple upload policies were matching the call the system did not take into account the configured priority setting
9.6.5.61782020-12-16
RI-024751Platform - Storage Management
Improved handling of Increase Retention policy failures in case of EMC Isilon SmartLock
9.6.5.61832021-01-06
RI-024829Platform - Storage Management
Transcript of voice calls could not be exported to an SMTP target
9.6.5.61912021-01-07
RI-024854Platform - Storage Management
The User-preferred data retention setting was not applied intermittently if the upload policy did not have a filter or the call was still in the ongoing table while the upload policy started to process the call
9.6.5.62012021-01-11
RI-024875Platform - Storage Management
Azure Blob based storage target was slow in case of a large number of files in the container (>500K)
9.6.6.62072021-01-14
RI-024878Platform - Storage Management
Storage Management and Speech Analytics services startup failed if there was no SQL connection
9.6.6.62072021-01-14
RI-024879Platform - Storage Management
Advanced Export: CSV metadata was not properly escaped if it contained delimiter, newline, or " characters
9.6.6.62092021-01-14
RI-025787Platform - Storage Management
Incomplete or wrong parameters in the Rename Files option on the Advanced Export configuration page caused an infinite loop and memory leak in the Storage Service
9.6.6.62652021-02-05
RI-025899Platform - Storage Management
When performing a Search of Conversations using for example Singapore time zone and performing an advanced export, the result in the CDR CSV file export displayed the time zone of each call in GMT rather than Singapore time zone
9.6.6.62852021-02-12
RI-026102Platform - Storage Management
When deleting a conversation on the web interface which was stored on an EMC Centera storage, then the CDR data was not deleted from the database
9.6.6.63122021-02-23
RI-026287Platform - Storage Management
Deduplication policy related improvements and fixes: - the policy did not check if the media had been uploaded for all CDR/Media records, so it might have failed to delete or copy the related ones and the processing policy was retried in the next schedule - the policy did not give up processing (committing conversation as processed) conversations that were under retention - processing secondary records might have continued with the next policy before the related primary pair had been processed by the policy
9.6.7.63492021-02-24
RI-026505Platform - Storage Management
If listing a local upload folder failed due to a corrupted file system, the upload policy stuck and couldn't continue
9.6.8.63762021-03-17
RI-026508Platform - Storage Management
In rare cases, when the Storage Management Service was looking for matching policies related to a call, and the call hadn't been updated in the database yet, a Policy processing error: no upload policy alert was raised. The call was processed and uploaded later just fine.
9.6.8.63762021-03-16
RI-026605Platform - Storage Management
Metadata XML files for CDR-Only records were not uploaded to EMC Centera. The system had a workaround during playback and export and it was not noticeable to users.
9.6.9.63802021-03-18
RI-026715Platform - Storage Management
Copy policy failed when the call was not stored on a storage target (it was stored in the local media folder on the Media Repository)
9.6.9.63902021-03-25
RI-026862Platform - Storage Management
Retention information was lost after executing the "Archive in DB" policy
9.6.9.64072021-04-06
RI-026931Platform - Storage Management
Storage Management service crashed due to database connection issues during export
9.6.10.64602021-04-07
RI-026959Platform - Storage Management
MP4 transcoding failed intermittently when the transcoding job was finished
9.6.9.64232021-04-09
RI-027261Platform - Storage Management
Microsoft Azure File Storage playback/download did not work after Microsoft changing the API
9.6.9.64322021-04-16
RI-027274Platform - Storage Management
The Storage Management service kept trying to upload files that were already uploaded and under retention to an EMC Isilon or NetApp Snaplock and files were stuck on the Recording Server
9.6.10.64602021-04-07
RI-027314Platform - Storage Management
Verba Secure File Transfer (VSFT) based upload issues resolved: - Storage Management service crashed when upload failed and retried in the same transaction - High CPU load caused by an infinite loop in SSL error handling - When advanced API security was disabled, the system fell back on the wrong certificates
9.6.11.65422021-04-19
RI-027324Platform - Storage Management
Archive in DB policy did not set the original storage target and the conversations could not be access
9.6.10.64562021-04-26
RI-027372Platform - Storage Management
Storage Management service crashed when voice quality check was enabled for upload and it processed a CDR-Only record
9.6.10.64602021-04-27
RI-027473Platform - Storage Management
Direct Upload/export was not processing calls after dual-archiving was enabled
9.6.10.64662021-04-29
RI-027599Platform - Storage Management
A retention period expiring after 2038 could not be set when using file-level retention based storage integrations (EMC Unity FLR and iTernity iCAS)
9.6.11.65422021-04-21
RI-027690Platform - Storage Management
In the case of a WORM storage and encrypted CDR records, the crypto info files for the related media files were not downloaded and so media records could not be decrypted, and playback/stitching failed with an error.
9.6.11.65412021-04-28
RI-027760Platform - Storage Management
The "Move", "Copy", and "Archive in DB and Move Media" policies could not move the files after upgrading to a version that supports Dual Archiving, because the "Which Copy" was initialized to "Both" (that is 0)
9.6.11.65102021-05-12
RI-027763Platform - Storage Management
Delete did not work for CDR-Only records (trader voice) migrated from Verint v11/v15.2 systems
9.6.11.65202021-05-20
RI-027818Platform - Storage Management
Advanced IM Export (Microsoft Teams) issues resolved: - If the original filename was not specified in the attachment and a random filename was generated, the extension was not properly added during export - If the conversation export did not find any IM or attachment to be exported, the export was not counted as success nor appeared in the total to be exported conversations counter under background tasks - The attachments which has not yet been downloaded or could never be downloaded are marked in the exported messages - The export did not work for conversation where an attachment download failed or was in progress
9.6.11.65422021-05-19
RI-027893Platform - Storage Management
Stitching and playback of Verint v11/v15.2 migrated CDR-Only records (trader voice) did not work since v9.6.7
9.6.11.65512021-06-03
RI-027906Platform - Storage Management
Trader voice export could have contained ongoing, partial conversations
9.6.12.66662021-06-09
RI-027908Platform - Storage Management
Storage service might have crashed after a successfully completed advanced export job when there was an issue with the database connection
9.6.12.66662021-06-09
RI-027962Platform - Storage Management
If a Verint-Migrated call was Archived in Verba, and a secondary copy was deleted, then the deletion was not registered in the database
9.6.12.66662021-06-10
RI-027963Platform - Storage Management
Verint-Migrated tar files were not deleted when the primary copy and the secondary copies of the same call had the same retention period
9.6.12.66662021-06-10
RI-028271Platform - Storage Management
Upload did not work when no matching policy was found
9.6.12.66662021-07-13
RI-028316Platform - Storage Management
Storage service error occurred when the Secret Access Key configuration field was empty for Amazon S3, Amazon S3 Compatible and Verint storage targets
9.6.12.66662021-07-14
RI-028319Platform - Storage Management
Playback, download, and export was slow when using Azure File Share Storage
9.6.12.66662021-07-16
RI-028336Platform - Storage Management
False alerts were generated when a data management policy execution couldn't validate properly if the upload policy for the call has been already executed and might have started processing calls not yet uploaded. The issue affects v9.6.7 or later deployments only.
9.6.13.67902021-09-22
RI-028395Platform - Storage Management
Manifest file for advanced export did not contain the end time of the export job
9.6.13.67902021-09-22
RI-028424Platform - Storage Management
Skype for Business RDP based app sharing recordings couldn't be transcoded when using policy based transcoding
9.6.13.67902021-09-22
RI-028437Platform - Storage Management
Metadata XML files for CDR-Only records were not uploaded to EMC Centera and the generated file based on the database during export did not contain custom metadata, participants, etc.
9.6.13.67902021-09-22
RI-028438Platform - Storage Management
When exporting trader voice CDR-Only records with stitched media, the metadata XML file did not contain the correct reference to the media file and the record type was incorrect
9.6.13.67902021-09-22
RI-028442Platform - Storage Management
Transcoding of application share recordings resulted in a video where the screen share stream was not visible if the aspect ratio of the app share stream was greater than 9:20 (WxH)
9.6.13.67902021-09-22
RI-028745Platform - Storage Management
If policy based export was used and the export target was SMB network folder or local folder, the export transcoding format was not properly taken into account for app share and video calls, they might have been transcoded to MP3 audio
9.6.13.67902021-09-22
RI-029152Platform - Storage Management
Audio transcoding was not available for screen and application share recordings during export configuration. Audio formats are now listed and the audio portion of the VMF files can be transcoded to standard audio files.
9.6.13.67902021-09-22
RI-029360Platform - Storage Management
Using advanced export and an AWS S3 compatible export target, and exporting only the metadata XML (without media) did not work
9.6.13.67902021-09-22
RI-024877Platform - Media Streaming
When both Verba\LocalIP and LocalIP6 were empty, the Media Streamer service started normally but did not start listening on. Now it will throw a configuration error/alert.
9.6.6.62072021-01-14
RI-023716Installer - Servers
The private key of the generated server certificate was not exportable
9.6.0.59832020-09-10
RI-024136Installer - Servers
Test SQL connection in the installer showed an error when the database had already exist
9.6.3.60432020-11-05
RI-027469Installer - Servers
SQL Server Express Edition install script did not work in the prerequisite tool in some cases
9.6.10.64652021-04-28
RI-027798Installer - Servers
The Installer displayed a SQL error when the Genesys Metadata Template was already assigned to Groups. To fix the problem just run the installer/scripts again.
9.6.11.65412021-05-28
RI-028337Installer - Servers
Genesys metadata template database update failed on multitenant systems
9.6.13.67902021-09-22
RI-028880Installer - Servers
Installer did not detect partitioning support on Azure SQL Database and Azure SQL Managed Instance
9.6.13.67902021-09-22
RI-028744Platform - CDR and Archived Content Import
The CDR reconciliation process did not take into account correctly the direction configuration of the extensions
9.6.13.67902021-09-22
RI-023995Platform - Import
Unescaped null character in the input caused SQL errors for generic import source
9.6.1.59952020-10-02
RI-024008Platform - Import
Migration from Verint v11 did not pull all of the Verint "Media" as Verba "Storage Target" so calls possibly could be migrated without a Storage Target property
9.6.1.59952020-09-28
RI-024048Platform - Import
Verint import (dual consolidation) fixes: - fixed direction field parsing - fixed start/end time and duration parsing
9.6.2.60152020-10-22
RI-024120Platform - Import
Generic Import from CSV files showed incorrect information about the total number of importable calls
9.6.2.60152020-11-03
RI-024121Platform - Import
Import Service crashed after service start if Verint Import Source was enabled and if the Verba Server IP configuration was incorrect
9.6.2.60152020-11-03
RI-024135Platform - Import
Verba import did not work for previously exported calls from a Verba system when calls were encrypted originally and were decrypted during export
9.6.1.59952020-10-14
RI-024156Platform - Import
Verint Migration: Back-Office calls were not assigned to Verba users. If a Front-Office call could be assigned to multiple Verba users, then the migration failed.
9.6.3.60432020-11-16
RI-024190Platform - Import
Verba Import did not work for recordings where there was a partial mismatch (e.g. timestamp) in the name of the media file and metadata XML file
9.6.4.60722020-11-23
RI-024205Platform - Import
Verint import (dual consolidation) improvements: - improved timestamp parsing and handling - session ID added to internal cache to handle trader voice records better - Device Type metadata field added - improved connection handling
9.6.4.60722020-11-16
RI-024692Platform - Import
Generic Import XML reading issue in case of single line XML files
9.6.5.61782020-12-21
RI-024905Platform - Import
Migration from Verint 15.2: Back Office Source Records was counted incorrectly, it showed less than the actual number of rows to migrate
9.6.6.62142021-01-18
RI-025841Platform - Import
In the case of multi-tenant setup, the imported media and metadata XML files were not put under the tenant ID specific folder
9.6.6.62712021-02-08
RI-025908Platform - Import
The Import Service configuration reread might have timeout when the policy was initializing at the time when the configuration reread request was triggered
9.6.6.62982021-02-12
RI-026724Platform - Import
Verint Import Source had crashed when a custom metadata field was updated in the database and the database connection was already in use
9.6.9.63912021-03-26
RI-027770Platform - Import
The O2 mobile network stack returns 400 Bad Request when "http://hostname" is present in an HTTP request URL. Downloaded data is now filtered for voice recordings only.
9.6.11.65262021-05-24
RI-027775Platform - Import
When using the Verint Import Source, not all calls were properly assigned/mapped to users
9.6.11.65262021-05-19
RI-028087Platform - Import
Import tasks were stuck in the case of Import Service restart
9.6.12.66662021-05-14
RI-028804Platform - Import
Cisco Webex Teams API authentication token was not refreshed in certain cases and caused the import to stop working, no alert was raised
9.6.13.67902021-09-22
RI-028871Platform - Import
Cisco Webex Teams file attachments could not be downloaded due to HTTP redirect changes in the API
9.6.13.67902021-09-22
RI-028873Platform - Import
Cisco Webex Teams instant message export did not work for malformed database fields
9.6.13.67902021-09-22

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.