Verba 9.6 Release Notes (build

Verba Release Notes



Current Release



Build Search

Find your build:

(e.g. 7.0.4548.0)

Verba 9.6 Release Notes (build

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

Release Date2020-09-10
Previous9.5 (build
Next9.7 (build

Known Critical Issues

First Affected
Resolved in
Certain calls between Skype for Business and Teams or Azure VoiceMail cannot be recorded

Am I affected?
All Sykpe for Business recording installations are affected where the recorded users can call Teams users or place voicemail messages in Azure VoiceMail.

Certain Skype for Business calls cannot be recorded when a recorded Skype for Business user is calling a Teams user and one of the participants is outside of the corporate network, or a recorded Skype for Business user is placing an Azure VoiceMail message. This limitation is caused by the new call setup procedure, and specifically in ICE negotiation, introduced in Teams and Azure VoiceMail, which prevents the recording system to redirect and force the calls to the Skype for Business Edge Server where the Media collector can fork the related media streams. Since the system is not able to capture the media streams related to these calls, these calls are not recorded. No alerts are raised unless CDR reconciliation is enabled.

Currently there is no workaround other than disabling Teams or Azure VM calling entirely for the recorded users. We are actively working on implementing a new solution which extends the capabilities of the Proxy Server to be able to relay these type of calls too. It requires a major change in the architecture by allowing the Proxy Server to relay calls with external participants through a public interface. It also means that that calls which are currently routed through the Skype for Business Edge Server and forked by the Media Collector Service will be routed through the Proxy Servers that same way as calls with internal or PSTN participants. We are currently targeting July 2020 with the enhanced version of the Proxy Server.
Resolved in
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.

- 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

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

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

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

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

Feature Improvements

Added in
Apache Tomcat application server hardening: - CBC hash algorithm ciphers have been removed - HSTS Max Age has been increased to one year (was 90 days)
OpenSSL library is updated to the latest v1.1.1j
OpenSSL library is updated to the latest v1.1.1k
OpenSSL library is updated to the latest v1.1.1l
Upgrade to the latest Log4j 2.17.1 version (from Log4j 1.2.17)
The private key password for the SSL certificate configuration can be defined in an encrypted format in the Apache Tomcat server.xml configuration file (previously it was plain text only)
Unused Spring jar files are removed from the web application. These files could be flagged by security scanners due to recent Spring vulnerabilities such as CVE-2022-22965.
OpenSSL library is updated to the latest v1.1.1n
OpenSSL library is updated to the latest v1.1.1o
RI-023492Recording - Passive
Passive Recorder does not release/invite conference announcement again at recording segmentation
RI-030714Recording - Cisco
Optimized handling of asynchronous event processing to determine IP address of the devices using Cisco JTAPI to avoid delays in database inserts
RI-030852Recording - Cisco
Support for multi-fork recording through CUBE Media Proxy to allow 2N recording using Cisco network-based recording
RI-024016Recording - Cisco IM
Cisco Webex Teams chat import and API throttling improvements to avoid API overload
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
RI-023510Recording - Lync/SfB
A new Call Processing alert is generated when the Media Collector & Proxy service is not able to allocate media ports
RI-030718Recording - Lync/SfB
Luware: Call As a Service - Process new metadata information to create proper CDR for these call flows
RI-031685Recording - Lync/SfB
The Verba SfB/Lync Filter Service now can use and prioritize the gateway/SBC's IP address in the case of subnet-based proxy assignment.
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.
RI-024046Recording - Microsoft Teams
Microsoft Teams Bot service supports maintenance mode which allows gracefully draining the server before shutting down the service
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
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.
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.
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.
RI-026922Recording - Microsoft Teams
The Microsoft Bot Media SDK was updated to
RI-028148Recording - Microsoft Teams
PSTN number support added to the never record feature for the Microsoft Teams Bot service.
RI-029858Recording - Microsoft Teams
Microsoft Teams bot grouping feature added for voice recording. The bot grouping allows grouping the recorded streams of the recorded users participating in the same meeting. When enabled, a single audio stream is sent to the bot until the group limit is reached. When the bot grouping is enabled, the following features are not supported for the user handled by the bot grouping: - Video/ Screen Share recording - Controlled recording - Never record (recording mode) - record only if external user is participating - record video only for external participants - record only scheduled meeting
RI-029865Recording - Microsoft Teams
New metadata template added for Microsoft Teams. Available metadata fields: Meeting Subject, Meeting Organizer ID, Meeting Organizer Name, and Compliance Policy
RI-029866Recording - Microsoft Teams
New configuration: Internal Domain, Numbers Pattern - Defines the tenants and number ranges that have to be considered as internal in the case of direction identification of the calls.
RI-030543Recording - Microsoft Teams
The Verba Microsoft Teams Bot service's meeting subject retrieval procedure extended with the Graph.onlineMeetings endpoint. Therefore the application needs an additional permission: OnlineMeetings.Read.All. Also, an Application Access Policy needs to be defined on the Teams tenant please refer to the Knowledge Base for more information. Only applicable if the additional Microsoft Teams type metadata is needed or Microsoft Teams meeting specific recording rules are used.
RI-030766Recording - Microsoft Teams
The Microsoft Teams Bot service now utilizes a counter to track the number of used video sockets. If the number of sockets reaches the limit's 99% it sends an unavailable response to the health probe requests.
RI-030767Recording - Microsoft Teams
The Microsoft Teams Bot service now implements a new algorithm to monitor and close timed out conversations. In various cases, the calls got stuck and still consumed resources which could led resource allocation issues.
RI-031289Recording - Microsoft Teams
The Microsoft Media Platform SDK health status was added to the Microsoft Teams Bot service's health probe so the load balancers can detect if the Media SDK is in a heavily loaded state and the bot should not receive any new invites.
RI-031442Recording - Microsoft Teams
The shared server feature has been added to the Microsoft Teams Bot Service and a single Microsoft Teams Bot and Recorder infrastructure can be shared across multiple VFC instances
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
RI-027864Recording - Microsoft Teams IM
Forward proxy configuration support for Microsoft Teams IM provider
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
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
RI-028877Recording - Microsoft Teams IM
Conversation Detail Record is no longer created for bot participants
RI-029517Recording - Microsoft Teams IM
Improved Microsoft Teams Graph API subscription management and logging to better recognize configuration issues
RI-030973Recording - Microsoft Teams IM
Added support for P2P and Group chat replies
RI-031023Recording - Microsoft Teams IM
Microsoft Teams chat messages (P2P and group chat, excluding channels) are now cached in memory to avoid ignoring messages due to participant query delays. This way we can record those earlier messages as well.
RI-031475Recording - Microsoft Teams IM
Microsoft has changed the license model for chat and channel archiving integrations which have to be defined when using the APIs. The following licensing models are available: - model=A is restricted to applications performing a security or compliance function, and requires a supported license. In the future, apps will also be required to pay for the messages they consume beyond the seeded capacity. - model=B is restricted to applications that do not perform a security or compliance function. model=B is free to use today; however, in the future, apps will pay based on the number of messages they consume. There are no licensing requirements for model=B. - Evaluation Mode (default) enables access to APIs with limited usage per requesting application for evaluation purposes. Change notifications will not be sent if the limit is exceeded.
RI-027265Recording - Avaya
Avaya Password added to the Active Directory Synchronization and Provisioning API
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
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.
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")
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
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.
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.
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
RI-029558Recording - Unified Call Recorder
Verizon SBC interoperability improvement for Veizion conference recording
RI-029782Recording - Unified Call Recorder
In case of a large amount of CTI/CDR records and absolute call splitter timer, the splitting might have taken 1-2 seconds causing such length of gap between termination of previous and starting of current segment's recording
RI-030809Recording - Unified Call Recorder
Verizon conference recording CDR enhancements: - Participant information - Conference bridge name - Employee ID
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)
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.
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
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)
RI-026444Recording - IPC
Local SIP Port can be configured in the IPC Zone configuration widget
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
RI-030720Recording - IPC
IPC Unigy - There was no alerting if media channel establishment (SIP) failed
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
RI-023491Recording - Dial-in
Dial-in Recorder: add support for call segmentation and improved silence gap filling for silence suppression/DTX
RI-026656Recording - SIPRec
Support for Mitel Border Gateway (v11) recording via SIPREC
RI-023900Recording - Symphony
Canceled Symphony calls are recognized and no longer marked as failed recordings
RI-031239Recording - Symphony
Symhony XML import source memory usage optimization for large input files
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
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.
RI-028312Recording - Genesys
T-Server connection alert throttling is introduced. The service will send alerts only in the case of a lost connection.
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
RI-030446Recording - Zoom
Added support for "individual recordings" change on Zoom API for Meetings - now if an extension is set for audio-only recording, the system will import the recording specifically created for the recorded user covering the period the given user was present at the meeting. This feature is only supported for audio, the video file will still contain the entire meeting.
RI-030462Recording - Zoom
Zoom Phones import query now leverages end-time based filtering, which drastically reduces the "safety lookback" overlap period needed for queries, slightly reducing API load
RI-030471Recording - Zoom
The Zoom Phone and Zoom Meeting import source can raise an alert if there are only 2000 API calls have left to reach the API rate limit
RI-030472Recording - Zoom
Better recovery for transient network issues for Zoom Meetings - now retry cycles try import later for meetings that's failed only at participant query while the meetings archiving query succeeded. These retires happen once a day.
RI-030482Recording - Zoom
Zoom Meeting participant list is now cached during import and reused during CDR reconciliation, reducing API load if CDR reconciliation is also enabled
RI-031076Recording - Zoom
Import/archiving of Zoom external meetings (meetings hosted by external Zoom users) if individual recordings for archiving setting is configured in the local Zoom tenant. Limitations: - Only recorded internal participant will be recognized, external participant or non-recorded internal participants will not be stored - Host will always be unknown - Meeting topic will be unknown
RI-023463UI - Web Interface
Apache Tomcat version is upgraded to 9.0.37
RI-023592UI - Web Interface
All HTTP traffic is automatically redirected to HTTPS by default in the Web Application
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
RI-024058UI - Web Interface
Improved group filter performance in Data Retention Policies, Roles Conversation Access Filters etc.
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.
RI-024134UI - Web Interface
"Search conference participants" renamed to "Search All Participants"
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
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.
RI-025848UI - Web Interface
Updated Web Application dependencies: Puppeteer (v7.0.4), embedded Chromium (v90.0.4403.0)
RI-025918UI - Web Interface
New Identity Provider (IdP) option: JSON Web Token (JWT) based authentication (RFC 7519)
RI-025922UI - Web Interface
Apache Tomcat version is upgraded to 9.0.43
RI-025925UI - Web Interface
Improved web interface optimized for mobile devices
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
RI-026778UI - Web Interface
The maximum size of the heap memory of Tomcat web application server is increased from 1GB to 2GB by default
RI-027467UI - Web Interface
Updated Web Application dependencies: Puppeteer (v9.0.0), embedded Chromium (v91.0.4469.0)
RI-027484UI - Web Interface
Improved configuration validation for bulk extension updates
RI-027728UI - Web Interface
Custom legal disclaimer messages can be added to the login screen via the web UI customization/brandind feature
RI-028175UI - Web Interface
New configuration available to control the visibility of labels, which is effective for all users including Supervisors
RI-028260UI - Web Interface
Updated Web Application dependencies: Puppeteer (v10.1.0), embedded Chromium (v92.0.4512.0)
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
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.
RI-028847UI - Web Interface
Apache Tomcat version is upgraded to 9.0.50
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
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
RI-029408UI - Web Interface
Login ID is no longer stored in a browser cookie. It can be turned on under Web Application / Password Policy / Store Login ID in Cookie
RI-029409UI - Web Interface
Default password requirements have changed for user accounts: - Account lockout will be turned on (after 5 failed attempts) - Passwords have to be a minimum of 8 characters, must include capital, numeric, special - Do not allow password reuse by default (remember and prevent reuse of the last 10 passwords)
RI-029431UI - Web Interface
OPTIONS HTTP method has been restricted
RI-029432UI - Web Interface
New configuration option to prevent simultaneous login with the same Login ID (configurable, turned off by default), and decrease default session timeout to 15 minutes (configurable)
RI-029560UI - Web Interface
Apache Tomcat version is upgraded to 9.0.54
RI-029733UI - Web Interface
Updated Web Application dependencies: Puppeteer (v10.4.0), embedded Chromium (v93.0.4577.0)
RI-029844UI - Web Interface
Support for the X-Forwarded-By request header is added to generate full URLs when it is present (e.g. when using a reverse proxy in front of the web application server like IIS)
RI-029845UI - Web Interface
New permission introduced to grant "Download IM Attachment" without the need for granting "Download a Conversation" permission in order to view/download IM attachments for advanced chat data model (e.g. Teams).
RI-030191UI - Web Interface
The prevent simultaneous login with the same Login ID feature now supported across multiple Media Repository servers
RI-030908UI - Web Interface
Updated Web Application dependencies: Puppeteer (v13.2.0), embedded Chromium (v99.0.4844.16)
RI-031180UI - Web Interface
New configuration option (Mobile Host Prefixes) to redirect requests to the mobile web application
RI-031214UI - Web Interface
New fields added to the Search Layout and Conversation Details screens: From RTP Packets, To RTP Packets
RI-031259UI - Web Interface
Ability to remove a Legal Hold Label from conversations individually. It is tied to a new permission, Remove Legal Hold From Conversations, which is not granted to any roles by default.
RI-031394UI - Web Interface
Custom User Fields have been added to the Conversation List layout
RI-031459UI - Web Interface
Try reading from the Active Directory again for three times if there was a network problem during AD Synchronization
RI-031500UI - Web Interface
Updated Web Application dependencies: Puppeteer (v13.6.0), embedded Chromium (v101.0.4950.0)
RI-031635UI - Web Interface
Apache Tomcat version is upgraded to 9.0.62, APR 1.2.33 (OpenSSL 1.1.1o)
RI-020986UI - Reporting
Improved CSV report format, all report produces a valid CSV file
RI-023933UI - Reporting
New Users Conversation Volume report showing the total number of recorded conversations for users
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
RI-028849UI - Reporting
Conversation Count Trend widget improvements: - New filtering options: Platform, Import Source - Date filtering did not work
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)
RI-031608UI - Reporting
Group filter added to Users Without Recording Report
RI-027587Solution - Speech Analytics
Server Name Indication support added to TLS for the Speechmatics integration
RI-020993Platform - API
All internal and external APIs now use HTTP Basic Authentication by default
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.
RI-028256Platform - API
Provisioning API can be used by tenant-level users (previously it was only available for service/hosting providers)
RI-029648Platform - API
Improved error messages for multi-part content praising issues for the Import REST API
RI-031012Platform - API
Legal Hold API allows creating and removing litigation holds in the system programmatically
RI-031257Platform - API
Legal Hold API permission changes by adding the new Remove Legal Hold From Conversations permission which is required when removing a user from legal hold
RI-031393Platform - API
User Custom Fields added to the Search API, and End Time can be filtered by the endTimeFrom and endTimeTo parameters
RI-031580Platform - API
SearchCalls and GetCallInformation APIs returns the attached labels if the returnLabels=1 parameter is added to the request
RI-020958Platform - Configuration
Performance improvements for Azure AD synchronization to support a large number of users
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.
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)
RI-027738Platform - Configuration
Node Manager connection can be optionally encapsulated into HTTPS to support strict firewall and forward proxy configurations
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
RI-023512Platform - Database
Upload policy can run during maintenance job execution to avoid long-running maintenance jobs blocking the upload functionality
RI-024690Platform - Database
The database Index Rebuild process is automatically stopped after 24 hours to avoid blocking normal operation by the database maintenance process
RI-027072Platform - Database
The search was slow in certain cases because the SQL Server has built the wrong execution plan
RI-027336Platform - Database
Improved call record insert performance by removing the possibilities for long running queries (e.g. legal hold management)
RI-028347Platform - Database
Improved legal hold performance for the advanced voice (incl. trader voice) data model
RI-029755Platform - Database
Data management policies are no longer paused during database maintenance jobs to better utilize the SQL Server resources
RI-029765Platform - Database
The default schedule for the maintenance jobs has changed from 22:00 to 20:00 (SQL Server local time) when the maintenance jobs are configured as SQL Server jobs (not applicable to maintenance run by the Web Application Server)
RI-029767Platform - Database
Improved database table index rebuild process which runs every days (instead of weekly)
RI-030991Platform - Database
Significant optimization for labeling rules to support large databases. We switched to an entirely database based implementation which made the Verba Labeling Service obsolete.
RI-031250Platform - Database
When the Archived Conversations checkbox was turned on in the Search settings, then the search was slow in case of large databases
RI-031378Platform - Database
Database maintenance jobs did not run on secondary replica databases when SQL Server Always-on Availability Groups were used. The maintenance jobs are not installed automatically but can be created manually so the secondary replica can use the jobs when the primary replica is down.
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.
RI-024996Platform - Licensing
License violation alerts include more detailed information about the current license
RI-029753Platform - Media Processing
New Intel based MP4 encoder added for video transcoding
RI-031607Platform - Media Processing
Media stitching for advanced voice data (e.g. trader voice) performance improved for GSM-FR based audio
RI-024195Platform - Monitoring
Customizable alert severities and selective alert sending option added for the System Monitor service on the servers
RI-024470Platform - Monitoring
BT ITS TTP packet loss alerts added to SCOM MP and SNMP MIB files
RI-024752Platform - Monitoring
The event ID attribute is added to SNMP traps
RI-026196Platform - Monitoring
SCOM package and SNMP MIB updated with new alerts for Microsoft Teams Bot, Genesys CTI and Unified IM Recorder services
RI-026743Platform - Monitoring
The import service sends an alert when an import source cannot be started due to a bad configuration
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
RI-021944Platform - Storage Management
Microsoft Azure Blob Storage support (in addition to existing Azure File Storage)
RI-023901Platform - Storage Management
Filtering of CDRs without media is done in the Storage Service for performance reasons
RI-023983Platform - Storage Management
VSFT secure file upload protocol connection timeout is now configurable
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]
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
RI-024105Platform - Storage Management
New SMTP export metadata field added for HTML formatted emails: [IMTranscript2_HTML] and [IMTranscript2_HMTL_InUserTimezone]
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.
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.
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.
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.
RI-027435Platform - Storage Management
Improved SFTP connection error and timeout handling
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.
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.
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
RI-029516Platform - Storage Management
Improved log database table handling for advanced export jobs to avoid database locking
RI-029574Platform - Storage Management
New SMTP template IMTranscript4_HTML with table design for standard IM data model
RI-029587Platform - Storage Management
Updated SFTP library to support more 'Key Exchange' algorithms. Now "diffie-hellman-group14-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512" are also supported.
RI-029612Platform - Storage Management
Verint Import Source changes: - Changed the memory cache to a persistent cache - Added conditional deduplication filter to the import manager for old records
RI-030548Platform - Storage Management
Encryption and signing capabilities are added for external Recording Server configurations. Both encryption and signing are available as server-level settings (instead of data management policies) and can be applied to all recorded data only (no filtering) during the upload process. The crypto information is also uploaded and re-used during the import process.
RI-030985Platform - Storage Management
New WORM storage target support, IBM Cloud Object Storage (COS) is added as an S3 Compatible storage target. It supports WORM features such as object lock and legal hold as well.
RI-031156Platform - Storage Management
The Data Retention default schedule will be Hourly from now on (previously it was weekly, configurable)
RI-031176Platform - Storage Management
New Data Management Policy: Adjust Retention for Media-Only Records which can increase the retention of the Media-Only recorded with the highest retention of the referencing CDR-Only records. This policy is useful for integrations where the advanced voice data model is used and the Media-Only records are shared with multiple recorded users (Genesys Active Recording, BT IPTrade TPO based recording).
RI-031184Platform - Storage Management
WORM capabilities are added to Amazon Web Services (AWS) S3 storage target. It supports WORM features such as object lock and legal hold as well.
RI-031276Platform - Storage Management
Improved Azure Blob upload error handling to avoid unnecessary reupload attempts
RI-031320Platform - Storage Management
New Addressing Mode configuration setting for Amazon S3 and Amazon S3 Compatible storage targets to define if Virtual Hosted Style or Path Style addressing mode should used
RI-031477Platform - Storage Management
Improve the Export Data Management Policies to handle Older Than and Recent Than filters according to the time when the current schedule started
RI-027468Platform - Media Streaming
Vulnerable ciphers are disabled by default for the Media Streaming service
RI-023630Installer - Servers
Database partitioning can be enabled during installation (in addition to manual script execution)
RI-023913Installer - Servers
Microsoft .NET Framework updated to version 4.8 in the install kit
RI-024137Installer - Servers
The installer can check if the Windows user running the installer has local administrator privilege which is required for the installation
RI-024793Installer - Servers
Updated Web Application dependencies: Puppeteer (v5.4.1), embedded Chromium (v87.0.4272.0) and Node.js (v14.15.0)
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
RI-030356Installer - Servers
Multiple improvements for the PowerShell Deployment Toolkit: - The PowerShell Deployment Toolkit now searches also for the AdoptOpenJDK JRE 11, ODBC Driver 17, and .Net 4.8 when checking the prerequisites. - 3rd party certificates now can be provided in the PowerShell Deployment Toolkit as Web Application SSL certificate (HTTPS) - The PowerShell Deployment Toolkit now uses the same process for installing the Verba database as the MSI installer. This includes several improvements: Support for Always-on Multi-subnet Failover setting, Support for database partitioning, Running configuration and IM schema update scripts when upgrading from Verba 8.x -SQL script execution log - The PowerShell Deployment Toolkit now searches also for the Oracle JDK 11 when checking the prerequisites. - The PowerShell Deployment Toolkit no longer asks for confirmation for CredSSP authentication when starting the script
RI-026200Platform - CDR and Archived Content Import
Skype for Business CDR reconciliation optimizations to allow faster execution time on large SfB CDR databases
RI-024002Platform - Import
Playback, download, and export support for legacy calls stored on Hitachi Content Platform and migrated from Verint v11
RI-024081Platform - Import
New import source support for O2 mobile recording
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
RI-024183Platform - Import
Improved recording rule/recorded extension handling to distribute the SQL Server load over time
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)
RI-026534Platform - Import
Verba import sources now support Azure Blob and File storages when importing data in Verba format
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
RI-026941Platform - Import
Verint v11 migration process takes user IDs from traders.traderid for front office calls
RI-027660Platform - Import
Verba Import Source has a new option to reinterpret/update recorded participant/owner of a call where it is already set
RI-027679Platform - Import
Forward proxy support added to Verba import source when Azure Blob Storage is configured
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)
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.
RI-028988Platform - Import
Integration with TeleMessage mobile archiving system to allow the capturing and archiving of WeChat, Whatsapp, TeleMessage Enterprise platforms
RI-029814Platform - Import
Added a new "IsExists" function to the Generic Import. The function check if a key exists in the input file.
RI-030538Platform - Import
Azure storage certificate check can be disabled optionally for Azure Blob and Azure File Storage for Verba import policies when the certificate revoke checks don't work due to network firewall limitations
RI-030618Platform - Import
Verint import source improvements: - Deduplication supports historical conversations - Background task counters improved
RI-031362Platform - Import
Generic import execution time significantly improved when CSV files were used
RI-031369Platform - Import
New archive priority configuration which defines the archive location used for playback/download/export in the VFC system when multiple archives were created for the same call


Fixed in
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
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
The value of the DBMSJavaTrustStorePassword was a plain text in the webapp.log
Microsoft Teams Bot Service logged internal API credentials (including the password) in plain text
Multiple Web Application vulnerabilities are resolved: - IP Address and Host Name have been removed from the User Information screen - User Enumeration: a new configuration is introduced that can be used to turn off sending the Login IDs to standard users: Web Application / Miscellaneous / Restrict Listing Login IDs - Cross-site scripting XSS vulnerability fixed in Label display on the Conversations screen - Potential phishing vulnerability for web sessions - Insecure Direct Object References on Get Call Participants, Share and Marker Update requests - Plain passwords were available in the page source on the configuration conflict resolution page - Add frame-ancestors 'self'; CSP header setting to improve the web application protection against clickjacking attack - Possible SQL injection on the dashboard for a specific widget
RI-025802Recording - Passive
VLAN decapsulation might have missed the last 2 bytes leading to processing problems
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.
RI-029570Recording - Passive
Passive Recorder placed the recorded calls into the wrong folder for remote cluster (shared recorder) calls and the upload did not work
RI-030721Recording - Passive
Partially recorded files for remote cluster/shared recorder were not recovered after the recorder crash. After applying the fix, the previous partial recordings can be recovered.
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
RI-029429Recording - Proxy
The TCP reuse option was not initialized in the SIP proxy which could have caused different routing behavior then configured
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
RI-027776Recording - Cisco
Technical/native call ID was not stored in the database when JTAPI integration was enabled for Cisco network-based recording
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
RI-028820Recording - Cisco
Cisco Barge and cBarge calls were not associated with Verba users because the JTAPI did not fill the agent ID field
RI-029790Recording - Cisco
Cisco JTAPI Call Recording Rules based on Genesys information did not work for Consult call scenarios
RI-030355Recording - Cisco
If persisted call event is stored in a corrupted file (e.g. after a crash while flushing data to disk, or not enough free disk space), the Unified Call Recorder Service tried to send invalid XML data to the Cisco JTAPI Service causing the slow communication and delayed database inserts
RI-030504Recording - Cisco
Cisco JTAPI Service did not reconnect to the CUCM after a Provider Shutdown event
RI-030598Recording - Cisco
Database records were missing for very short calls (less than 2 seconds) in rare cases for Cisco JTAPI based integrations
RI-031261Recording - Cisco
The Verba Cisco JTAPI Service sent a CUCM Connection Down alert during service startup
RI-031582Recording - Cisco
The Owner User ID was not determined in some Cisco Barge and cBarge scenarios and user assignment did not work for these call legs
RI-031583Recording - Cisco
Cisco JTAPI records are inserted into the database with a delay when a Controlled Extension started to record automatically, and the call is considered finished by the JTAPI Service
RI-031636Recording - Cisco
Metadata changes were not written into the database when a Cisco JTAPI recorded Extension was set up improperly as Controlled but started to record automatically
RI-031637Recording - Cisco
The Cisco JTAPI Service ran out of memory and crashed when the Cisco UCCE or UCCX integration was enabled. The system raised an alert after the service failure. During the service failure, the system could have missed metadata.
RI-024923Recording - Cisco IM
Participant information was not inserted from Cisco IM&P instant message conversations
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
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.
RI-024073Recording - Lync/SfB
Video was flickering in Acano meetings with Skype for Business interop when only voice recording was enabled for the user
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.
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
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
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
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.
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.
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.
RI-029639Recording - Lync/SfB
The Verba Lync Call Filter and IM Filter Services didn't reset the keep-alive state in the case of non-graceful disconnection. This could lead unsuccessful connection attempts. This state could be resolved by restarting the filter service.
RI-030786Recording - Lync/SfB
Skype for Business and Azure Voice Mail or Microsoft Teams Media Resource (conference call, including recorded calls in Teams) call scenarios could not be recorded and couldn't be established when the recording was enabled. This was caused by changes on Microsoft/Azure side (first occurrence in January 2022).
RI-031235Recording - Lync/SfB
During Skype for Business application share recording if RDP was in use and the sharer/viewer role changed and meanwhile the storage upload cycle ran, the initial segment might have been lost
RI-031364Recording - Lync/SfB
Skype for Business calls to Azure Voicemail did not get recorded when the caller device supported RTCP multiplexing and one of the called devices (e.g. in the case of simulring) did not support RTCP multiplexing.
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
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.
RI-024027Recording - Microsoft Teams
HSTS response headers were missing for HTTPS listeners on 9440 and 10100 ports for the Microsoft Teams Bot service
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
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
RI-024177Recording - Microsoft Teams
Transcoding application share recording to MP4/WMV might miss the voice part after the application share is stopped
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.
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.
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.
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.
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.
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.
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.
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.
RI-025921Recording - Microsoft Teams
The video stream of the guest users was ignored and the bot never subscribed to them
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.
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.
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
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
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.
RI-026932Recording - Microsoft Teams
Microsoft Teams Media SDK generated invalid timestamps for audio leading to media processing issue and continuously growing audio files
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.
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.
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
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.
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.
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.
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.
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.
RI-027912Recording - Microsoft Teams
The guest users' video content was not recorded due to a video subscription issue.
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.
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.
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
RI-028446Recording - Microsoft Teams
When call splitting was configured, participant information was only available for the last segment in the database
RI-029375Recording - Microsoft Teams
When the service failed processing an item of the participant list, it didn't process the rest of the participant list.
RI-029630Recording - Microsoft Teams
The Microsoft Teams Bot service didn't follow the change in the media stream id of the participants. In the cases of stereo recording, when the recorded user's media steam id changed the recorded user's audio was mixed to the other participants' audio.
RI-030189Recording - Microsoft Teams
The audio stream ID was not properly updated in the case of P2P calls. It caused that in the case of stereo recording the bot didn't use the dedicated channel for the recorded user.
RI-030586Recording - Microsoft Teams
The Microsoft Teams Bot service didn't take into account the selective recording options in the case of call escalation from P2P to meeting.
RI-030587Recording - Microsoft Teams
The Microsoft Teams Bot service started the recording in the case of undefined call direction. The service will wait until it can gather enough information to calculate the direction of the call. The affected call scenarios: P2P VBSS-only and call queues.
RI-030765Recording - Microsoft Teams
The Microsoft Teams Bot service started recording in the case of external meeting organizer even if the extension was configured to start recording only for specified meeting organizers.
RI-031011Recording - Microsoft Teams
Microsoft Calling SDK is rolled back to v1.2.0.1702 due to performance issues with the latest version in handling call invites and participant updates. By rolling back to this version, the bot grouping feature will be entirely disabled.
RI-031421Recording - Microsoft Teams
The Microsoft Teams Bot service didn't start recording of anonymous P2P calls.
RI-031528Recording - Microsoft Teams
In the case of controlled recording, adding the screen share modality to the call automatically started the recording.
RI-031529Recording - Microsoft Teams
The system recorded calls even if the Record Only if External User is Participating and the Record Video Only for External Users settings were enabled and there was no external user on the call.
RI-031530Recording - Microsoft Teams
In the case of transfer scenarios, the party which initiated the transfer was stored in the From Info field instead of the To Info.
RI-031531Recording - Microsoft Teams
In the case of screen share only calls (when the screen share was used only), the later added audio or video modalities were not recorded.
RI-031532Recording - Microsoft Teams
In the case of a non-configured recorded user, the video modality was not recorded when the Record Non-configured Extensions configuration setting was enabled.
RI-031534Recording - Microsoft Teams
The Microsoft Media SDK upgraded to version which resolves the following issues according to Microsoft: Fixed a bottleneck within the SDK's media engine that could cause severe delay in setting up new media sessions containing VideoSockets. In some cases, the delay could result in meeting join failures for the bot.
RI-031535Recording - Microsoft Teams
Large Microsoft Teams meetings were not recorded if the list of participants is truncated, and the recorded user was not on the participant list sent to the bot. The system did not raise an alert or log an error when an invite to the bot was not followed by a related participant list update. The issue can only be detected if call/meetings logs are compared with the database records. The issue affected only the call recording taking place for the specific user who was not listed as a participant. If there were multiple recorded users joining the same meetings, the meeting could be recorded from the other user's point of view if that user was listed as a participant. In order to provide an immediate workaround, the system uses a different recording start logic in the bot to not wait for the recorded user to appear as a participant. There is an open support case with Microsoft on how to get the full list of participants because the system stores the participants in the database, and the information is incomplete in this way. The Start Recording After Recorded User Joined settings must be changed to No in order for the bot to ignore the join event for the user. The setting defines if the bot waits for the join event of the recorded user before it starts recording a meeting. This setting is only applied for meetings, for P2P and PSTN calls, the bot always waits for the recorded user join event. If the configuration is set to 'No', the bot will trigger recording after it processed the first participant of the first roster update. The service will also stream every media packet to the recorder without waiting for the recorded user to join.
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
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.
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.
RI-028174Recording - Microsoft Teams IM
The message processing queue was stuck when federated Skype for Business users were participating in the chat room
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
RI-028331Recording - Microsoft Teams IM
Stickers could not be downloaded and archived for P2P and group chats
RI-028335Recording - Microsoft Teams IM
Unnecessary Microsoft Graph webhook subscriptions when the system attempted to subscribe to an already exiting subscription
RI-029358Recording - Microsoft Teams IM
Attachments could not be accessed for standard users, only for system supervisors
RI-030912Recording - Microsoft Teams IM
Multiple issues resolved for Microsoft Teams IM capture using the webhook DLP API: - Participant name might have been empty in Skype for Business and Teams interop scenarios, which led to SQL query errors and alerts, and the data was not inserted - If attachment download resulted in 429/Too many requests, the download task was considered as failed and an alert was raised, it was never retried - The message processing could have been stuck in an infinite loop in the case of HTML processing error, and the affected processing queue got stock - Several performance optimizations to enable processing a high number of messages and reducing the number of Microsoft Graph API queries - Records and participants generated from participant list query results might have had a start time 1900.01.01. - If the file attachment extension was not properly parsed, then the attachment insert query might have failed - Unsupported system events caused empty messages with "unknown" as participant name. - Recorded extension configuration update timed out on the web interface while it was still running on the server
RI-031243Recording - Microsoft Teams IM
Microsoft Teams instant messages were missing sender information intermittently
RI-031399Recording - Microsoft Teams IM
Chat messages for Microsoft Teams were not moved from section_message1 to section_message2 when more than 1000 records were in the table. This could cause the system to slow down during the search and the running of data management policies such as export. This issue only affects and later deployments
RI-024033Recording - Avaya
Preferred Codecs list was incorrect in the hint of the Avaya Recorder / Avaya DMCC / Preferred Codec server configuration
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
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
RI-031494Recording - Avaya
The Avaya DMCC Service could not start with the Avaya DMCC API 8.1 jar files. This issue only affects or later.
RI-025887Recording - Centile
The duration of the stereo recordings (AU files) was double the length of the call
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)
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.
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)
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.
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
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.
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
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
RI-030217Recording - Unified Call Recorder
Verizon meeting RTP echoing caused recording only silence once the send back delay timer elapsed
RI-030722Recording - Unified Call Recorder
Partially recorded files for remote cluster/shared recorder were not recovered after the recorder crash. After applying the fix, the previous partial recordings can be recovered.
RI-031468Recording - Unified Call Recorder
Call segmentation optimization to avoid possible short gaps (0-2 seconds) in media records when a large number of calls are segmented at the same time (e.h. when an absolute segmentation timer is used)
RI-023895Recording - IPTrade
IPTrade turret based playback was very slow due to the wrong execution plan compiled by SQL Server
RI-027647Recording - IPTrade
BT IP Trade turret side playback list recording action was very slow
RI-031415Recording - IPTrade
BT IPTrade call playback on turret did not work in multi-tenant environments
RI-024098Recording - BT ITS
If a second device connected to the same call on the turret, the recorder stopped recording on the first device
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
RI-025011Recording - BT ITS
If BT ITSLink server sent the dialed number multiple times, the dialed digits were concatenated and appeared multiple times
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.
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.
RI-029624Recording - BT ITS
BT IPSI media recording did not work from version, media could not be recorded at all
RI-031159Recording - BT ITS
Optionally enabling the processing of the cstDialedDigits CTI event when the cstProceeding is missing and the called party number is missing. Please note, the system will potentially record and store sensitive information entered during the call. The cstDialedDigits carries all digits entered/pressed during the call, including PIN codes or other private and sensitive data. This information will be stored in the standard metadata fields of the system and there is no option to mask or block these additional digits.
RI-024786Recording - Speakerbus
In some case, the system sent a false call processing error alerts if a device change happened on the line
RI-031631Recording - Speakerbus
When the Recording Server did not receive a logout event (unexpectedly) for a trader and a new trader logged in to the turret and started making/receiving calls, the system could not record the new calls for the new user.
RI-029809Recording - IPC
IPC Unigy recording did not work when AudioCodes SBC was in the media path
RI-030044Recording - IPC
IPC Unigy external turrets via a Session Border Controller could not be recorded due to an interoperability issue in SDP negotiation
RI-024100Recording - Cloud9
Cloud9 Recording System API integration did not work and C9 clients were unable to upload data to the Recording Server (affects or later builds only)
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
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
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.
RI-024787Recording - Cloud9
Cloud9 Recording System API based integration did not work intermittently due to an uninitialized connection timeout
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
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
RI-028826Recording - Cloud9
Cloud9 Call Data API Import Source was looking for the wrong metadata template
RI-029389Recording - Cloud9
C9 Call Data API did not handle the HTTP proxy error code 504 (Gateway Timeout)
RI-030202Recording - Cloud9
Cloud9 Call Data API integration will store the media file ID as soon as it becomes available to avoid race condition in upload process
RI-031405Recording - Cloud9
Cloud9 Recording System API based import source did not insert the data to the right tenant in multi-tenant environments.
RI-026230Recording - Desktop
The desktop agent application did not update the status icon after the connection with the Web Application was recovered
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
RI-027755Recording - Desktop
Desktop Agent muted recording unexpectedly when the Auto-Pause Recording on URL setting contained an empty line
RI-029869Recording - Desktop
The Verba Screen Capturing Service crashed if "silent/non-visible" mode was configured
RI-028977Recording - Dial-in
Phone-based playback did not work imported calls where the Audio Codec ID was not set
RI-025678Recording - SIPRec
Metaswitch Perimeta: caller/callee was swapped in case of interconnecting calls
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).
RI-023943Recording - Symphony
Screen/application share modality was not properly determined for SIPREC sessions and the system stored these streams as video recordings
RI-024005Recording - Symphony
Symphony calls were not assigned to users
RI-030904Recording - Symphony
Symphony chat messages with multiple attachments could not be displayed
RI-024302Recording - Genesys
The Cisco JTAPI Service tried to connect to a T-Server with Backup role
RI-029671Recording - Genesys
The Verba Genesys CTI service failed to insert database record in the case of database record duplication check.
RI-029874Recording - Genesys
The Verba Genesys CTI Service didn't apply recording configuration based on the Genesys Agent ID. It used the directory numbers configuration. It could have led to inconsistent recording. The service also didn't process the metadata properly before the recording decision-making.
RI-030590Recording - Genesys
The Genesys CTI service didn't start recording based on CTI event fields mid-call. The service only applied the recording rules at the beginning of the conversation.
RI-030597Recording - Genesys
Mid-call failover didn't work with Genesys active recording integration
RI-031537Recording - Genesys
Fixed handling of CTI triggered recording in the case of hold-resume, blind transfer, consultative transfer, consultative conference scenarios for Genesys Active Recording based integration
RI-030444Recording - Zoom
Multiple issues fixed for Zoom Meeting and Zoom Phone import/archiving: - Fixed a networking issue related to chunked HTTP transfer that could rarely affect API calls and downloads and resulted in parsing errors and alerts - Certain Zoom Phones MP3 files waveform was displayed incorrectly (full silence) in the web application player - Zoom Meetings host information handling fixed. Zoom Meeting host and conferee participant roles were not properly saved and displayed. - Fixed an issue that causes last Zoom Meetings and Phones calls sometimes would not get imported until a new meeting or call happened - Fixed an issue that could result in Zoom Meetings data loss if there were an excessively large number of meetings in a single import cycle
RI-030807Recording - Zoom
Multiple fixes for Zoom Meeting and Phone import/archiving: - Fixed individual recordings choosing based on time: when a user joined a single meeting multiple times, the correct individual recordings are chosen for the resulting CDR (previously always the same was chosen) - Fixed a bug when sometimes a meeting or phone call that was already imported was downloaded and attempted to be imported multiple times - Import/reconciliation stopped progressing indefinitely when there were no meetings/phone calls for the entire max filter period (Meetings 7 days / Phones 28 days) - Some configurations of safety lookback with phones reconciliation caused reconciliation to stop progressing indefinitely when calls happened near midnight - Fixed potential data loss in meetings, when a very high amount of meetings were imported in a single cycle, and the load was unbalanced between "past" and "pastOne" type of meetings - Fixed a SQL problem that could cause crashes, and prevented reconciliation tasks to appear in background tasks - Fixed Meetings reconciliation that did not work when recorded extension configuration was set to voice only - Solved a problem that caused reconciliation to cause false-positive alerts when Zoom took a too long time to archive meetings or phone calls. A new parameter is introduced for both Zoom Phones and Meetings import: Reconciliation Delay Behind Import in Minutes (60 minutes by default), which causes the reconciliation to ignore elements within this period before where import progress is currently at. Never set this lower than how long it takes for Zoom to process the archiving of a meeting/phone call.
RI-031389Recording - Zoom
Waveform of M4A/MP4A files might have not been generated properly (for MP4 there was no problem)
RI-031454Recording - Zoom
Zoom import source stopped working after receiving an unkown archived file type for Zoom meeting import. Unkownfile types are no longer causing an error, but a warning alert
RI-031478Recording - Zoom
When querying the Zoom API if the server responds with a TO field with a value far in the future, the system disregards it. preventing data loss in the period in the period of actual TO time and the value provided by the Zoom API (when TO is in the past, the system still adjusts to it)
RI-031578Recording - Zoom
Workaround for missing participant leave date (unexpected) for Zoom Meeting imports
RI-023605UI - Web Interface
The player buttons FWD and END, didn't work properly. If not applicable the button will be grayed out.
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.
RI-023902UI - Web Interface
Selecting the Excel export option on the Alert Management page resulted in a blank page
RI-023909UI - Web Interface
Send URL feature did not work
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.
RI-023915UI - Web Interface
Audio segment download in player did not work for trader voice recordings with stitched media
RI-023918UI - Web Interface
Search was very slow for trader voice conversations due to the wrong execution plan compiled by SQL Server
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
RI-024010UI - Web Interface
The Audit Log details were double-escaped, so "->" strings and HTML tables (Search parameters) were garbled
RI-024056UI - Web Interface
The scroll bar was missing in the conversation metadata tab in the player
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)
RI-024070UI - Web Interface
The selected Identity Providers were displayed as "Available" too when cloning an existing Role
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
RI-024149UI - Web Interface
Users were able to bypass playback restriction when the multiple playback feature was used
RI-024166UI - Web Interface
Home Page setting did not work with Integrated Windows Authentication (IWA)
RI-024227UI - Web Interface
Bulk Media download was available even if the user had no "Download a Conversation" permission
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.
RI-024239UI - Web Interface
Copy URL icon was not shown on conversations
RI-024242UI - Web Interface
In the case of text search, the Unicode characters were not encoded properly in the transcript view
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.
RI-024417UI - Web Interface
Cloud9 Call Data API import source configuration page did not work
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.
RI-024625UI - Web Interface
The Cisco Finesse gadget could not authenticate with HTTP Basic authentication method.
RI-024788UI - Web Interface
Media files bigger than 2 GB cannot be downloaded and played back from the web application
RI-024789UI - Web Interface
The e-mail generated by the Send URL feature displays question marks for non-ASCII characters
RI-024831UI - Web Interface
If the user did not have "Customize Conversation Export Target Folder" permission, then the Direct Download feature did not work
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: +, -, @, =, ;
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.
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
RI-025938UI - Web Interface
When a Controlled auto-start recording started, only the Administrator was able to stop the recording
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
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
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
RI-026672UI - Web Interface
The CSV user export did not differentiate the "User/Agent ID" type extensions
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)
RI-026927UI - Web Interface
The silent monitoring button on the Agent View page was added multiple times for each on-hook agent.
RI-027323UI - Web Interface
Playback of a Desktop Screen recording was audio-only after the VF file converted to MP4 and got deleted
RI-027334UI - Web Interface
Background Tasks page End Time column was converted to the user's timezone two times
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.
RI-027642UI - Web Interface
Active Directory Synchronization: groups not re-added after the user is re-activated in the same Active Directory Synchronization Profile
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
RI-027653UI - Web Interface
Microsoft Teams Instant Messages could be duplicated when searching for a text for a long time period
RI-027657UI - Web Interface
Microsoft Teams Instant Message edit history could not be displayed
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
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
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.
RI-027882UI - Web Interface
The Data Management and Export features' Duration Interval filter threw error when there were calls longer than 24 days
RI-027885UI - Web Interface
The transcription did not load into the player when the user did not use the Text Search
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)
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
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)
RI-028160UI - Web Interface
The Reports / Create New Report menu showed a blank page when using Internet Explorer
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
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.
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
RI-028441UI - Web Interface
The fetch following or previous SMS messages did not work in the Conversation View
RI-028443UI - Web Interface
The Conversation Export Metadata Fields always showed the Reference Environment's Metadata Fields in a Multi-Tenant deployment
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)
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.
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
RI-028925UI - Web Interface
Download of a shared file did not work when there was a + sign in the file name
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
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.
RI-029435UI - Web Interface
The reports list downloaded the wrong file when pagination was used
RI-029436UI - Web Interface
Change History could be viewed without permission to the object
RI-029449UI - Web Interface
Dashboard did not work when the Date Interval was set to Hour
RI-029480UI - Web Interface
The Cisco IP Phone Service showed "Host not found" after the user typed the login and password and submitted the authentication form
RI-029546UI - Web Interface
If a User was created manually, and the "Synchronized by Active Directory" was turned on, then this User was not deactivated when not found in the Active Directory, because the Users that are synchronized by failed AD Sync Profiles are never deactivated by the system.
RI-029559UI - Web Interface
The system displayed configuration discrepancies even if the server's configuration was the same as the central for Microsoft Teams Bot / Microsoft Teams / Call Control Port and Media Control Port
RI-029562UI - Web Interface
Data Management Policy delete gives no error explanation when referenced by another policy as "Execute Only After Another Policy Executed"
RI-029596UI - Web Interface
Preview Conversation didn't work for trader voice recordings
RI-029867UI - Web Interface
Private checkbox did not mark the conversations as Private
RI-030192UI - Web Interface
User Bulk Update threw error when multiple Extension Directions should be changed and the Full-Matrix mode was turned on
RI-030433UI - Web Interface
The Conversations Search Export / Media feature downloaded previously selected recordings' media files after the user performed new searches
RI-030588UI - Web Interface
The time zone listbox did not display half-our time zones correctly, but it worked properly in the actual time display
RI-030730UI - Web Interface
A "Database Maintenance Error" alert was generated after a Conversation that was already marked for deletion got a Legal Hold Label
RI-031087UI - Web Interface
After deduplication, secondary Media-Only records were not displayed when related CDR/Media records were listed
RI-031192UI - Web Interface
Direct Search link did not work because the colon character triggered a false vulnerability blocking
RI-031216UI - Web Interface
"End of Retention" column cannot be added to the search layout configuration if the system was upgraded from 9.5 or earlier versions
RI-031221UI - Web Interface
Viewer for advanced IM (Microsoft Teams) didn't respect the advanced search timezone display settings
RI-031241UI - Web Interface
Voice Quality Check alerts were displaying HTML source code on the web interface instead of the formatted content
RI-031255UI - Web Interface
Pressing the Find button on the Automation Rules - Cases redirected the user to the Automation Rules - Labeling page
RI-031313UI - Web Interface
Creating a Hitachi Content Platform storage target, the API User field was overwritten with "v2" no matter what was defined
RI-031361UI - Web Interface
The existing custom metadata fields were not shown after an upgrade from v9.3 or older version
RI-031367UI - Web Interface
The Mobile UI Search feature did not work with the latest version, and the Detail screen showed the times in the wrong timezone
RI-031381UI - Web Interface
Right-click options did not working properly on the Conversations screen
RI-031437UI - Web Interface
The calls recorded in "High Quality Opus in Ogg" format could not be played back in Internet Explorer (using the Windows Media Player Active-X component)
RI-031458UI - Web Interface
Active Directory Synchronization User read failures were not detected if paging was required (more than 1000 users) and it did not happen on the last page. This led to user invalidation which could have led to recording and data loss. The underlying LDAP protocol did not provide any error.
RI-031461UI - Web Interface
License activation information was not shown on the license page when there were license warnings or errors
RI-031687UI - Web Interface
Right-click options / Same day features on the conversations screen chose the day in UTC timezone instead of the user's timezone
RI-031689UI - Web Interface
Advanced IM viewer (Microsoft Teams) failed to render a message if it was a message reference without a proper user display name.
RI-021162UI - Waveforms
Waveform always showed on peak when static there was noise in the call. Now data is normalized by the visualization script.
RI-026509UI - Waveforms
Selective audio download did not work when the wave file is on a network drive with Custom Credentials
RI-030981UI - Waveforms
Missing waveform with SMB network storage for MP4 or MP3 media (did not apply if VMF was available)
RI-023937UI - Reporting
The Conversation Access Event Details report supported the English language only
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
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
RI-024230UI - Reporting
Recorded Users and Extensions report did not show the Distinct Total value in case of the CSV format
RI-024399UI - Reporting
Dashboard snapshot schedule was not correct when the creation time converted to UTC resulted in a longer time then 24 hours
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.
RI-024823UI - Reporting
Quality Management Form Custom Field titles and values were not saved
RI-024857UI - Reporting
Agents Evaluation Details report's CSV format contained the column headers multiple times
RI-027318UI - Reporting
The Recording Server Utilization dashboard widget loaded very slowly if Microsoft Teams instant message capture was used
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)
RI-029350UI - Reporting
Group name was missing from Users Roles Permissions and Groups report in XLS format
RI-030173UI - Reporting
The Audit Log Report XLS version did not display the Search Query details
RI-030193UI - Reporting
User Instant Messages Details report did not show participants
RI-030432UI - Reporting
The Permission Configuration Report displayed only reference environment users
RI-030593UI - Reporting
The following reports did not work when there was a Recording Server filter: Conversation Access Event Details, Conversations With No Media Details, Not Recorded and Incorrect Conversations Details, Recording Minute Usage, Users CDR Reconciliation Summary, Users Call Activity Details, Users Call Activity Summary, Users Inbound Call Activity, Users Outbound Call Activity, Users Server Usage Details, Users Speech Transcript Details
RI-030635UI - Reporting
The User Instant Messaging Details report did not show the participants of the conversation. It only showed the user who sent the message.
RI-031245UI - Reporting
The Permission Configuration report was missing the localized text for a few Permissions
RI-031371UI - Reporting
Voice Quality Check Summary report generated 0KB file when filtered for groups
RI-031373UI - Reporting
Users, Roles, Permissions and Groups, and Not recorded and Incorrect Conversations Details reports with user filter threw exceptions and generated 0KB output file when CSV format was used
RI-031404UI - Reporting
Reporting did not work with Firefox. The issue only affects and later.
RI-031479UI - Reporting
Group supervisors were only able to see supervisioned groups in reports
RI-031634UI - Reporting
The Roles and Permissions report did not work when there was a Role with the "Unable to Access Conversations Older than
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.
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
RI-028147Solution - Quality Management
Quality Management agents could not open their own scorecard
RI-024702Solution - Speech Analytics
If the case of video recording with mixed audio, the voice transcript included everything twice
RI-027737Solution - Speech Analytics
Speech transcription did not work since 9.6.7 due to SQL query errors
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)
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)
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
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.
RI-030361Platform - Announcement
The Verba Lync/SfB Announcement Service could not insert announcement audit log to the database because of a password encoding issue.
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)
RI-024613Platform - API
SearchCalls API threw an error when searching for ongoing calls without the end time parameter
RI-024846Platform - API
When a User was created via the Provisioning API without a password, then the web application threw an error
RI-025691Platform - API
Import REST API did not work intermittently due to an uninitialized connection timeout
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
RI-027881Platform - API
The Provisioning API v3 GetUsers call did not return the Roles of the Users
RI-027894Platform - API
The Provisioning API did not return the expired Users' group memberships
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
RI-028096Platform - API
Provisioning API v3 - Extension update without modalities caused NullPointException
RI-028674Platform - API
The Business API did not return archived conversations
RI-029759Platform - API
Import REST API was not tenant aware and allowed importing into any tenant
RI-031314Platform - API
Provisioning API v3 - Invalid import sources could be added for extensions.
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
RI-031185Platform - Configuration
SQL Server Failover Partner connection setting was not adjusted for ODBC connection string scheme if a custom port number was specified causing persistent SQL connection failure. This only affects C++ based services such as Storage Management Service, Unified Call Recorder Service, Passive Recorder Service, Import Service, Node Manager Agent Service.
RI-031215Platform - Configuration
Java services always logged to the c:\Program Files\Verba\log\ folder even if that was not the installation folder with certain Java versions
RI-031316Platform - Configuration
Certificate validation: revocation status was checked only for issuers but not for the actual certificate which caused the system to continue operating with revoked certificates
RI-031356Platform - Configuration
Shared server upload relied on the remote Media Repository list presented at recording time, which might have become outdated if Media Repositories were deleted in the meantime. This caused the upload to fail because the Storage Management service was trying to upload to an invalid server.
RI-031554Platform - Configuration
When site configuration was used and the Recording Server recorded a call for the user using an integration that supported shared server recording rules, the system could have recorded calls on the server which should not have been recorded on that site.
RI-024233Platform - Database
The upload process prevented Maintenance Job from running and vice versa
RI-024685Platform - Database
The following deletion functions did not work since - 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.
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.
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
RI-030732Platform - Database
Recordings may have stayed occasionally in the Ongoing table for a few minutes when more than 10 calls were recorded per second
RI-024112Platform - Licensing
License Usage was not counted after a Web Application restart until the daily license check or visiting the license screen
RI-024689Platform - Licensing
License: Media Monitor (CDR Reconciliation) check counted non-voice Extensions too
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
RI-026260Platform - Media Processing
Transcoding desktop screen captures (.vf files) did not work
RI-028274Platform - Media Processing
Very short (<500msec) video/screen share transcoding might have stuck
RI-029744Platform - Media Processing
When transcoding Skype for Business screen and application share recordings (VBSS) the video streams might have been out of sync with audio
RI-030669Platform - Media Processing
Memory and resource leak fixed in MP4 transcoding. MP4 transcoding might have stuck in the processing state at the end of the process when SMB storage was used.
RI-031455Platform - Media Processing
Transcoder job has stuck when there was an exception when opening the media file
RI-031524Platform - Media Processing
Video frames could be missing when decoding VMF files when the aspect ratio of the video stream was changed and become noticeable with low framerates such as application share streams
RI-024007Platform - Monitoring
Unsupported SNMP v3 is removed from configuration dropdown and the default value is to version 2
RI-024837Platform - Monitoring
When an SNMP trap was sent successfully it was inserted into the database with unsuccessful SNMP sending status
RI-026746Platform - Monitoring
The "Policy Continues After Error" alert had the wrong alert ID set in the storage service
RI-027880Platform - Monitoring
System Monitor service at detail level logged the credentials for the API user requests (injecting alerts into the database)
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
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
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
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
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
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
RI-023989Platform - Storage Management
Policy-based upload ignored policy level retention period setting if Prefer User Retention was enabled and the value was empty
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.
RI-024014Platform - Storage Management
Recorded Party field parsing caused "stoi argument out of range" errors in the generic import
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
RI-024025Platform - Storage Management
Duplicate email attachments were sent during policy-based SMTP export of voice calls when the email template had attachments configured.
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.
RI-024045Platform - Storage Management
SMTP export sent extra emails while checking for transcipt (.vtr) file
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
RI-024139Platform - Storage Management
Connection failed to EMC Centera when secondary server was configured due to wrong connection string parsing
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
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).
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
RI-024751Platform - Storage Management
Improved handling of Increase Retention policy failures in case of EMC Isilon SmartLock
RI-024829Platform - Storage Management
Transcript of voice calls could not be exported to an SMTP target
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
RI-024875Platform - Storage Management
Azure Blob based storage target was slow in case of a large number of files in the container (>500K)
RI-024878Platform - Storage Management
Storage Management and Speech Analytics services startup failed if there was no SQL connection
RI-024879Platform - Storage Management
Advanced Export: CSV metadata was not properly escaped if it contained delimiter, newline, or " characters
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
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
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
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
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
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.
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.
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)
RI-026862Platform - Storage Management
Retention information was lost after executing the "Archive in DB" policy
RI-026931Platform - Storage Management
Storage Management service crashed due to database connection issues during export
RI-026959Platform - Storage Management
MP4 transcoding failed intermittently when the transcoding job was finished
RI-027261Platform - Storage Management
Microsoft Azure File Storage playback/download did not work after Microsoft changing the API
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
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
RI-027324Platform - Storage Management
Archive in DB policy did not set the original storage target and the conversations could not be access
RI-027372Platform - Storage Management
Storage Management service crashed when voice quality check was enabled for upload and it processed a CDR-Only record
RI-027473Platform - Storage Management
Direct Upload/export was not processing calls after dual-archiving was enabled
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)
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.
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)
RI-027763Platform - Storage Management
Delete did not work for CDR-Only records (trader voice) migrated from Verint v11/v15.2 systems
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
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
RI-027906Platform - Storage Management
Trader voice export could have contained ongoing, partial conversations
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
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
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
RI-028271Platform - Storage Management
Upload did not work when no matching policy was found
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
RI-028319Platform - Storage Management
Playback, download, and export was slow when using Azure File Share Storage
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.
RI-028395Platform - Storage Management
Manifest file for advanced export did not contain the end time of the export job
RI-028424Platform - Storage Management
Skype for Business RDP based app sharing recordings couldn't be transcoded when using policy based transcoding
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.
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
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)
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
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.
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
RI-029379Platform - Storage Management
Erroneous background task counters were displayed for the deletion policy for migrated Verint v11/v15 TAR files. In addition, potentially high memory usage when querying a large number of records to be processed.
RI-029385Platform - Storage Management
The progress bar for the playback download popup window could go above 100% when the media file was stored on Microsoft Azure storage target.
RI-029536Platform - Storage Management
Advanced export ignored the Recent Than, Older Than, Elapsed Time Since Transcoding filter options when the schedule was set to "Once immediately"
RI-029538Platform - Storage Management
Generic Import Source was not handling the timezone correctly. It was adding timezone offset instead of subtracting.
RI-029545Platform - Storage Management
Advanced IM export e-mail attachments sometimes were ZIP files with wrong (.png) extensions
RI-029638Platform - Storage Management
When the retention period of a migrated VOX record (from Verint v11/v15) was over and that record was archived multiple times with different retention periods in the v11/15 system (before the migration), then another (one more) non-expired copy of the record was deleted too from the system. The bug impacts v9.6.7.6349 or later installations.
RI-029732Platform - Storage Management
If custom thresholds were set for voice quality check then false alerts might have been raised because RTP Decoding Errors and Beep & Clicks scores were swapped when evaluating thresholds
RI-029777Platform - Storage Management
Verint WFO export/ingestion authentication did not work after recent WFO patch
RI-029802Platform - Storage Management
Deduplication could process both primary and secondary recording at the exact same time. If both tasks tried to delete a file or swap something in the database then the system raised alerts about missing files.
RI-029935Platform - Storage Management
Export of imported chat conversations (e.g. Symphony) did not work using an export policy
RI-030043Platform - Storage Management
Imported Cloud9 recordings (via the Call Data API) could not be uploaded when there was no media file referenced
RI-030049Platform - Storage Management
Two servers could receive the same conversations for a Data Management Policy when the "Check Policy Order on Call Basis" was set to "No" and the stored procedure was called at the same time
RI-030219Platform - Storage Management
Migrated TAR files from Verint v11/v15 were not deleted when two TAR files with the same name were archived two times
RI-030224Platform - Storage Management
Attachment file size limitation (it was 5 MByte) is removed from SMTP based export targets. It is now configurable under Storage Management / Storage Targets / SMTP / Attachment Size Limit [MB]
RI-030237Platform - Storage Management
When the system was unable to determine the size of the file to be uploaded to a storage target, the upload process failed due to the invalid file size parameter. Affected storage targets: Amazon S3, Verint, Bloomberg Voice, O365 Compliance Archive.
RI-030559Platform - Storage Management
Advanced IM Export policy did not work when there was a Group or Metadata Template filter configured
RI-030788Platform - Storage Management
When the key was not available during decrypting legacy encrypted files (VF), the system didn't recognize the missing key and generated invalid files
RI-030851Platform - Storage Management
Policy-based export did not take into account voice/audio transcoding codec setting when trader voice recordings were exported and media stitching was used
RI-030974Platform - Storage Management
Using advanced export, the naming pattern for files could have caused the media file name to be not unique
RI-031312Platform - Storage Management
The [DateTime] field could not be parsed when used in the SMTP export target and the export failed to send emails
RI-031319Platform - Storage Management
Advanced IM export did not take into account the Do Not Export Attachments option
RI-031354Platform - Storage Management
In the case of using Verba Secure File Transfer (VSFT) based upload if on the Media Repository side, the received media was to be moved to another drive and took longer than 30 seconds, the client side (Recording Server) timed out and reattempted the upload which continuously failed.
RI-031398Platform - Storage Management
Participant information was missing for advanced IM export (Microsoft Teams) when the UPN information was not available when the CDR entry was created (it only become available later)
RI-031409Platform - Storage Management
SMTP IM Export attachment was missing because the storage target ID was wrong
RI-031414Platform - Storage Management
Auto-delete after the retention period is over did not work in multi-tenant deployments. Those conversations were not deleted where the retention has expired. The auto-delete feature is used when the retention of the conversations is set by an upload policy, instead of using a delete policy.
RI-031476Platform - Storage Management
Delete Policy with "File Extension(s)" configuration did not work and caused a database error
RI-031573Platform - Storage Management
Storage Management Service could have raised false alerts on upload failures (no matching policy) due to race conditions in database and file operations
RI-031577Platform - Storage Management
Certain Storage Management functions were not automatically retried after recoverable database errors
RI-031609Platform - Storage Management
Transcoding from video/app share/desktop screen to audio format did not convert the call to voice only modality and did not delete the original video file
RI-031268Platform - Tools
Copy-Item cmdlet failed randomly in the PowerShell Deployment Toolkit
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.
RI-023716Installer - Servers
The private key of the generated server certificate was not exportable
RI-024136Installer - Servers
Test SQL connection in the installer showed an error when the database had already exist
RI-027469Installer - Servers
SQL Server Express Edition install script did not work in the prerequisite tool in some cases
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.
RI-028337Installer - Servers
Genesys metadata template database update failed on multitenant systems
RI-028880Installer - Servers
Installer did not detect partitioning support on Azure SQL Database and Azure SQL Managed Instance
RI-029367Installer - Servers
Speech Analytics Server role installer was missing EMC Centera and Netapp runtime DLLs and the integrations did not work after the installation
RI-030570Installer - Servers
Multiple issues fixed for the PowerShell Deployment Toolkit: - The PowerShell Deployment Toolkit included the wrong version of the lyncfilter.dll - The PowerShell Deployment Toolkit used the old hashing algorithm for the user passwords created during the install process, therefore it wasn't able to update them. - File copying failed randomly in the PowerShell Deployment Toolkit. The Toolkit now uses xcopy instead, which is more stable than the PowerShell Copy-Item cmdlet. - The PowerShell Deployment Toolkit failed to install the database when using windows credentials. - The certificate generation failed randomly in the PowerShell Deployment Toolkit, because the CNG Key Isolation service wasn't running. The script now checks and starts the service.
RI-030583Installer - Servers
The installer didn't fill the API URL correctly when installing the Recording Server role, and skipping the API URL check. Now it fills localhost in the setting.
RI-030591Installer - Servers
Microsoft SQL Express installer did not work from the Prerequisite Tool
RI-031264Installer - Servers
User impersonation was missing when checking the existence of the API user in the database
RI-028744Platform - CDR and Archived Content Import
The CDR reconciliation process did not take into account correctly the direction configuration of the extensions
RI-029595Platform - CDR and Archived Content Import
Cisco CDR reconciliation did not work for calls where the user was configured for voice-only recording but made video calls
RI-031210Platform - CDR and Archived Content Import
Lync/SfB CDR import on the rare occasion of reconciliation was not set in the data management policy, the customer could see a long reconciliation cycle until 2100.1.1.
RI-023995Platform - Import
Unescaped null character in the input caused SQL errors for generic import source
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
RI-024048Platform - Import
Verint import (dual consolidation) fixes: - fixed direction field parsing - fixed start/end time and duration parsing
RI-024120Platform - Import
Generic Import from CSV files showed incorrect information about the total number of importable calls
RI-024121Platform - Import
Import Service crashed after service start if Verint Import Source was enabled and if the Verba Server IP configuration was incorrect
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
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.
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
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
RI-024692Platform - Import
Generic Import XML reading issue in case of single line XML files
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
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
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
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
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.
RI-027775Platform - Import
When using the Verint Import Source, not all calls were properly assigned/mapped to users
RI-028087Platform - Import
Import tasks were stuck in the case of Import Service restart
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
RI-028871Platform - Import
Cisco Webex Teams file attachments could not be downloaded due to HTTP redirect changes in the API
RI-028873Platform - Import
Cisco Webex Teams instant message export did not work for malformed database fields
RI-029807Platform - Import
The Generic Import test feature did not work because the service skipped metadata file testing when the metadata had a lock on the file. No error message was given/logged on the user interface.
RI-029852Platform - Import
Verba import did not work when the standard metadata template type was used in the source system
RI-030229Platform - Import
When the last character of a Webex Teams chat message was a \ character the formatting was malformed and multiple messages were merged together
RI-030233Platform - Import
The generic import source was setting the Native Call ID wrong and the information was not stored in the database
RI-030853Platform - Import
Generic import source failed if the file was encoded with BOM, which sometimes caused issues, like the first column not matching in CSV headers.
RI-030977Platform - Import
RingCentral import source did not handle API throttling responses
RI-031247Platform - Import
The time of Next Execution changes randomly if the clock of the SQL Server and Media Repository servers are not in perfect sync
RI-031260Platform - Import
Ringcentral import source did not handle API throttling responses
RI-031284Platform - Import
Verint v11/v15 migration got to an infinite loop when two Back Office inums were referencing each other with the previnum field.
RI-031315Platform - Import
Migration from Verint v11/v15 may chose an unsupported (tape) storage during migration, and that led to an empty Storage Target
RI-031360Platform - Import
Verint Import Source did not work after upgrading Verint v15 to the latest version
RI-031427Platform - Import
HTTPS connections could not be established when HTTP headers exceeded a certain size
RI-031684Platform - Import
Import sources did not insert the data to the right tenant in multi-tenant environments, all data was inserted into the reference tenant, regardless of in which tenant the import policy and the user were configured.
RI-031467Offline Player
Verba Offline Player could not playback Microsoft Teams video (or any other where "unknow" directional audio streams were present)

Download your software

You can download the latest Verba releases at

Updates to this document

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

Access to support

Verba customers that have purchased support have access to support through

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

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

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

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

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