RI-023459 | Security |
Multiple security and vulnerability fixes and configuration changes for the Web Application:
- Cross-site scripting (XSS) vulnerability fixes
- Weak ciphers removed from TLS configuration
- HTTP security headers updated
- Web Application logging changes to hide version and code specific information
- 3rd party Javascript library updates
- Improved secure cookie handling | 9.6.0.5966 | 2020-08-13 |
RI-024073 | Recording - Lync/SfB |
Video was flickering in Acano meetings with Skype for Business interop when only voice recording was enabled for the user | 9.6.2.6015 | 2020-10-27 |
RI-023997 | Recording - Lync/SfB IM |
The Skype for Business IM recorder could not create an XML file for the conferences when direct export/upload configuration was used | 9.6.1.5995 | 2020-09-30 |
RI-024027 | Recording - Microsoft Teams |
HSTS response headers were missing for HTTPS listeners on 9440 and 10100 ports for the Microsoft Teams Bot service | 9.6.1.5995 | 2020-10-06 |
RI-024028 | Recording - Microsoft Teams |
When multi-tenancy was disabled, the Microsoft Teams Bot service used the 0000 environment ID and the recordings were uploaded into the 0000 folder | 9.6.1.5995 | 2020-10-13 |
RI-024138 | Recording - Microsoft Teams |
Microsoft Teams Bot service was installed with the wrong default value for the Recording Notification setting and recording was still controlled by the system while it should not have been | 9.6.2.6022 | 2020-11-05 |
RI-024033 | Recording - Avaya |
Preferred Codecs list was incorrect in the hint of the Avaya Recorder / Avaya DMCC / Preferred Codec server configuration | 9.6.1.5995 | 2020-10-12 |
RI-024122 | Recording - Unified Call Recorder |
If the Recording Director and the Media Recorder is separated and either File Share, Poll/Q&A, Whiteboard or SMS modality was enabled in addition to Voice/Video or Screen Share (but not all modalities), then the recording rule became invalid end the call was not recorded at all. Alerts were raised with "Cannot register call on media recorder" error. | 9.6.2.6021 | 2020-11-04 |
RI-023895 | Recording - IPTrade |
IPTrade turret based playback was very slow due to the wrong execution plan compiled by SQL Server | 9.6.0.5987 | 2020-09-24 |
RI-024154 | Recording - BT ITS |
BT ITS LDAP provisioning queries could take too much time during service start which could prevent the service from starting as Windows considered it a service failure after a timeout and killed the process prematurely | 9.6.3.6043 | 2020-11-16 |
RI-024100 | Recording - Cloud9 |
Cloud9 Recording System API integration did not work and C9 clients were unable to upload data to the Recording Server (affects 9.6.0.5983 or later builds only) | 9.6.2.6015 | 2020-10-15 |
RI-023943 | Recording - Symphony |
Screen/application share modality was not properly determined for SIPREC sessions and the system stored these streams as video recordings | 9.6.0.5987 | 2020-08-27 |
RI-024005 | Recording - Symphony |
Symphony calls were not assigned to users | 9.6.1.5995 | 2020-09-29 |
RI-023605 | UI - Web Interface |
The player buttons FWD and END, didn't work properly. If not applicable the button will be grayed out. | 9.6.0.5974 | 2020-08-25 |
RI-023609 | UI - Web Interface |
Video playback area in Internet Explorer didn't fit properly to screen size. In some cases, when the screen resolution was under 1080p, it overfleww into the conversation details section. | 9.6.0.5974 | 2020-08-25 |
RI-023902 | UI - Web Interface |
Selecting the Excel export option on the Alert Management page resulted in a blank page | 9.6.0.5987 | 2020-09-24 |
RI-023909 | UI - Web Interface |
Send URL feature did not work | 9.6.0.5987 | 2020-09-24 |
RI-023910 | UI - Web Interface |
User group membership will not be updated when the user is primarily synchronized by an AD Profile which should not synchronize users. Membership update incorrectly happened when the user started to be merged by another AD Profile. | 9.6.0.5987 | 2020-09-23 |
RI-023915 | UI - Web Interface |
Audio segment download in player did not work for trader voice recordings with stitched media | 9.6.0.5987 | 2020-09-22 |
RI-023918 | UI - Web Interface |
Search was very slow for trader voice conversations due to the wrong execution plan compiled by SQL Server | 9.6.0.5987 | 2020-09-21 |
RI-023985 | UI - Web Interface |
Ad hoc transcoding jobs were executed by any of the Media Repository / Application Servers (whichever has seen the job first) and the transcoded video was not available for playback on the server where the user was connected to | 9.6.1.5995 | 2020-10-07 |
RI-024010 | UI - Web Interface |
The Audit Log details were double-escaped, so "->" strings and HTML tables (Search parameters) were garbled | 9.6.1.5995 | 2020-09-25 |
RI-024056 | UI - Web Interface |
The scroll bar was missing in the conversation metadata tab in the player | 9.6.2.6015 | 2020-10-20 |
RI-024063 | UI - Web Interface |
When using a direct link to open the Conversation Details, the Protect icon did not work and the Related Calls icon was visible even if it was not working (and now removed) | 9.6.2.6015 | 2020-10-07 |
RI-024070 | UI - Web Interface |
The selected Identity Providers were displayed as "Available" too when cloning an existing Role | 9.6.2.6015 | 2020-10-27 |
RI-024143 | UI - Web Interface |
If a user did not have the "Customize Conversation Export Target Folder" role then updating an advanced export configuration page caused an error | 9.6.3.6043 | 2020-11-09 |
RI-024149 | UI - Web Interface |
Users were able to bypass playback restriction when the multiple playback feature was used | 9.6.3.6043 | 2020-11-12 |
RI-021162 | UI - Waveforms |
Waveform always showed on peak when static there was noise in the call. Now data is normalized by the visualization script. | 9.6.0.5944 | 2020-06-09 |
RI-023937 | UI - Reporting |
The Conversation Access Event Details report supported the English language only | 9.6.0.5987 | 2020-09-14 |
RI-024152 | UI - Reporting |
The Server Capacity report did not work and the system generated 0kb reports (no report output) with exceptions in the log files | 9.6.3.6043 | 2020-11-16 |
RI-023979 | Platform - API |
Provisioning API getStoragePolicies and getStoragePolicy returned a StorageFolder even when the policy had no Storage Folder (then returned a dummy folder with id 0) | 9.6.1.5995 | 2020-10-08 |
RI-024093 | Platform - Configuration |
Server certificate validation timeout was too short in some rare cases and validation failed during the startup of the following services: Web Application Service, Cisco JTAPI Service, Cisco Compliance Service, Avaya DMCC/JTAPI Service | 9.6.2.6015 | 2020-10-20 |
RI-024112 | Platform - Licensing |
License Usage was not counted after a Web Application restart until the daily license check or visiting the license screen | 9.6.2.6015 | 2020-10-22 |
RI-024141 | Platform - Media Processing |
Transcoded MSRDP based Skype for Business screen/application share recording could not be played back (showed green screen) if the original stream (shared window) height was an odd number | 9.6.3.6043 | 2020-11-09 |
RI-024007 | Platform - Monitoring |
Unsupported SNMP v3 is removed from configuration dropdown and the default value is to version 2 | 9.6.1.5995 | 2020-09-28 |
RI-023603 | Platform - Storage Management |
Export and import of Skype for Business IM conversations did not work when IM transcript file creating was enabled in the recorder service | 9.6.0.5974 | 2020-08-25 |
RI-023896 | Platform - Storage Management |
Media stitching for playback and export was very slow for trader voice conversations due to the wrong execution plan compiled by SQL Server | 9.6.0.5987 | 2020-09-24 |
RI-023898 | Platform - Storage Management |
Advanced Export and Export Policy could show invalid records count at the end of the task if new, matching records were inserted to the database while the task was running | 9.6.0.5987 | 2020-09-24 |
RI-023899 | Platform - Storage Management |
Advanced Export manifest file contained the temporary file path of the media files if the file was to be transcoded or stitched | 9.6.0.5987 | 2020-09-17 |
RI-023982 | Platform - Storage Management |
Recent than/older than filtering for advanced export did not work as expected because the reference date was based on the current time and not on the export schedule | 9.6.1.5995 | 2020-10-08 |
RI-023988 | Platform - Storage Management |
In case of data was modified by other processes during executing the deletion transaction in the deduplication policy, the failed transaction was not retried, instead of alert was raised and processing was reattempted only at the next policy run | 9.6.1.5995 | 2020-10-06 |
RI-023989 | Platform - Storage Management |
Policy-based upload ignored policy level retention period setting if Prefer User Retention was enabled and the value was empty | 9.6.1.5995 | 2020-10-06 |
RI-023999 | Platform - Storage Management |
On-demand conversation processing SQL queries might fail after a long idle time. Alerts were raised and queries were executed again. | 9.6.1.5995 | 2020-09-30 |
RI-024014 | Platform - Storage Management |
Recorded Party field parsing caused "stoi argument out of range" errors in the generic import | 9.6.1.5995 | 2020-09-25 |
RI-024023 | Platform - Storage Management |
Policy based export ignored the "Encrypt XML metadata" checkbox on UI and encrypted all the time when the media was encrypted | 9.6.1.5995 | 2020-10-14 |
RI-024025 | Platform - Storage Management |
Duplicate email attachments were sent during policy-based SMTP export of voice calls when the email template had attachments configured. | 9.6.1.5995 | 2020-10-14 |
RI-024032 | Platform - Storage Management |
The system showed wrong export statistics for Bloomberg Voice on the user interface (multiple tasks were checking the same storage target level files and updating their task status). Improved error and SFTP handling. | 9.6.1.5995 | 2020-10-12 |
RI-024045 | Platform - Storage Management |
SMTP export sent extra emails while checking for transcipt (.vtr) file | 9.6.1.5995 | 2020-10-14 |
RI-024069 | Platform - Storage Management |
The wrong file was played back in some cases in the player in case of Verint v11 migrated calls which were stored on Hitachi Content Platform | 9.6.2.6015 | 2020-10-28 |
RI-024139 | Platform - Storage Management |
Connection failed to EMC Centera when secondary server was configured due to wrong connection string parsing | 9.6.3.6043 | 2020-11-09 |
RI-023716 | Installer - Servers |
The private key of the generated server certificate was not exportable | 9.6.0.5983 | 2020-09-10 |
RI-024136 | Installer - Servers |
Test SQL connection in the installer showed an error when the database had already exist | 9.6.3.6043 | 2020-11-05 |
RI-023995 | Platform - Import |
Unescaped null character in the input caused SQL errors for generic import source | 9.6.1.5995 | 2020-10-02 |
RI-024008 | Platform - Import |
Migration from Verint v11 did not pull all of the Verint "Media" as Verba "Storage Target" so calls possibly could be migrated without a Storage Target property | 9.6.1.5995 | 2020-09-28 |
RI-024048 | Platform - Import |
Verint import (dual consolidation) fixes:
- fixed direction field parsing
- fixed start/end time and duration parsing | 9.6.2.6015 | 2020-10-22 |
RI-024120 | Platform - Import |
Generic Import from CSV files showed incorrect information about the total number of importable calls | 9.6.2.6015 | 2020-11-03 |
RI-024121 | Platform - Import |
Import Service crashed after service start if Verint Import Source was enabled and if the Verba Server IP configuration was incorrect | 9.6.2.6015 | 2020-11-03 |
RI-024135 | Platform - Import |
Verba import did not work for previously exported calls from a Verba system when calls were encrypted originally and were decrypted during export | 9.6.1.5995 | 2020-10-14 |
RI-024156 | Platform - Import |
Verint Migration: Back-Office calls were not assigned to Verba users. If a Front-Office call could be assigned to multiple Verba users, then the migration failed. | 9.6.3.6043 | 2020-11-16 |