RI-020110 | Security |
Possible CSV command injection vulnerability resolved when a malicious user can make Excel running commands. For more information, see https://owasp.org/www-community/attacks/CSV_Injection | 9.5.1.5922 | 2020-03-25 |
RI-020111 | Security |
Vulnerability resolved which made it possible to update user passwords without enforcing password rules on the administrator pages | 9.5.2.5944 | 2020-03-25 |
RI-020122 | Security |
Vulnerability resolved when the web application infrastructure details (version number) were disclosed with the error message | 9.5.1.5922 | 2020-03-24 |
RI-020123 | Security |
Vulnerability resolved when the system sent previously saved Active Directory passwords in plain text during Connection Test | 9.5.1.5922 | 2020-03-24 |
RI-019525 | Recording - Cisco |
Cisco network-based recording with JTAPI integration: conversations had not been inserted into the database or got stuck ongoing in very rare cases | 9.5.0.5894 | 2020-02-12 |
RI-019630 | Recording - Cisco |
Cisco JTAPI call details were not added to the Barger party's recording in case of Barge calls (Called information and Agent/User ID) | 9.5.0.5899 | 2020-02-24 |
RI-020004 | Recording - Cisco |
Cisco Unity voice mail calls were not recorded due SCCP protocol changes | 9.5.1.5911 | 2020-03-05 |
RI-020013 | Recording - Cisco |
Cisco JTAPI service did not associate conference participants with users | 9.5.1.5911 | 2020-02-28 |
RI-020575 | Recording - Cisco |
If the Verba Cisco JTAPI Service was stopped meanwhile it was processing an End Call event, then the call could stick in the ongoing records | 9.5.3.5953 | 2020-05-04 |
RI-021246 | Recording - Cisco |
Unchanged Genesys metadata were not stored for the next call of an extension | 9.5.3.5975 | 2020-06-10 |
RI-021550 | Recording - Cisco |
In very rare cases, the Unified Call Recorder service sent the call end event twice to the Cisco JTAPI service which caused an error and an alert was raised. No data was lost. | 9.5.4.5979 | 2020-06-23 |
RI-019606 | Recording - Lync/SfB |
Skype for Business calls to Azure Voice Mail did not work when the SfB user was configured for proxy-based recording | 9.5.0.5898 | 2020-02-21 |
RI-020120 | Recording - Lync/SfB |
False SRTP decryption alerts were raised for SfB - Teams interop calls | 9.5.1.5922 | 2020-03-19 |
RI-021109 | Recording - Lync/SfB |
Skype for Business Filter services stuck at startup when the Secure API certificate was not found | 9.5.3.5972 | 2020-05-26 |
RI-020181 | Recording - Microsoft Teams |
Unified Call Recorder service might have crashed after configuring Microsoft Teams Bot service connection with an FQDN which could not be resolved | 9.5.2.5933 | 2020-04-02 |
RI-020354 | Recording - Microsoft Teams |
Unified Call Recorder service could not continue recording for Teams calls after call splitting timer expired (2 hours by default) | 9.5.2.5947 | 2020-04-22 |
RI-020412 | Recording - Microsoft Teams |
After a participant changed the screen/app share source, the system stopped recording the stream | 9.5.2.5950 | 2020-04-23 |
RI-020413 | Recording - Microsoft Teams |
Meeting participants were not inserted into the database in some rare cases | 9.5.2.5950 | 2020-04-23 |
RI-020415 | Recording - Microsoft Teams |
The application secret was stored as a clear text in the local registry on the server. After upgrade, the secret has to be re-entered on the configuration interface. | 9.5.2.5950 | 2020-04-23 |
RI-020771 | Recording - Microsoft Teams |
The connection between the Microsoft Teams Bot and the Unified Call Recorder service might have stuck and the system could not record calls | 9.5.2.5963 | 2020-05-14 |
RI-021116 | Recording - Microsoft Teams |
Conversations could not be found when extensions were not configured in an environment/tenant when multi-tenancy was enabled | 9.5.3.5973 | 2020-05-27 |
RI-021121 | Recording - Microsoft Teams |
Source platform was not filled in the database record | 9.5.3.5973 | 2020-05-21 |
RI-021122 | Recording - Microsoft Teams |
P2P escalation to group call was not reflected in the database and there was no new recording started | 9.5.3.5973 | 2020-05-19 |
RI-021123 | Recording - Microsoft Teams |
The connection between the Microsoft Teams Bot and the Unified Call Recorder services could be stuck in a registration state which prevented call recording. No alerts were raised. | 9.5.3.5973 | 2020-05-18 |
RI-021135 | Recording - Microsoft Teams |
The Microsoft Teams Bot service subscribed for video or VBSS streams of the call participants even if these modalities were not configured for the recorded user | 9.5.3.5973 | 2020-05-12 |
RI-021138 | Recording - Microsoft Teams |
The service ignored the 'Number of Recorded Video Participants' configuration and it was limited for 4 video streams | 9.5.3.5973 | 2020-05-06 |
RI-021140 | Recording - Microsoft Teams |
The Microsoft Teams Bot service could not parse anonymous caller which caused missing CDR entries in the database | 9.5.3.5973 | 2020-05-06 |
RI-021553 | Recording - Microsoft Teams |
Connection recovery mechanisms improved in the Unified Call Recorder service with the Microsoft Teams Bot service in case of partial connection failures | 9.5.4.5979 | 2020-06-18 |
RI-019501 | Recording - Avaya |
Avaya DMCC Service tried the next (backup) CM when got "Access code invalid" error during extension registration | 9.5.0.5894 | 2020-02-14 |
RI-019024 | Recording - Centile |
Centile connector service did not insert new database fields such as file size, modality, etc. | 9.5.0.5894 | 2019-12-02 |
RI-018915 | Recording - Unified Call Recorder |
Markers overlapping segmented calls were stored inaccurately | 9.5.0.5894 | 2020-01-30 |
RI-018938 | Recording - Unified Call Recorder |
In case of terminating the recording with call timeout (no call end event received, not trader voice recording), the end time of the record was the time of timeout occurred instead of the last media received | 9.5.0.5894 | 2020-01-23 |
RI-020363 | Recording - Unified Call Recorder |
Conference participants were not inserted at video escalation or CDR update | 9.5.2.5947 | 2020-04-14 |
RI-020573 | Recording - Unified Call Recorder |
Due to SQL performance reasons, participant information is available only at conversation end | 9.5.2.5953 | 2020-05-04 |
RI-021637 | Recording - Unified Call Recorder |
Media file recovery after a service crash might fail for BT IPTrade, IPC Unigy or Speakerbus calls when Voice Activity Detection (VAD) is not enabled | 9.5.5.5985 | 2020-07-02 |
RI-018965 | Recording - IPTrade |
If CDR was updated with the same caller/callee number/URI then a possible display name/line label change was skipped and not reflected in the CDR | 9.5.0.5894 | 2020-01-16 |
RI-020410 | Recording - IPTrade |
When using Voice Activity Detection (VAD) for BT IP Trade recording, voice clipping could occur at the end of the recording if the media recording session was very short (few seconds or less) | 9.5.2.5950 | 2020-04-23 |
RI-020787 | Recording - IPTrade |
BT IPTrade recording with separate streams for caller and callee (no mixing) crashed the recorder service. Alert was raised. The issue affected v9.5.2.5950 or later releases only. | 9.5.3.5966 | 2020-05-19 |
RI-021557 | Recording - IPTrade |
After TPO failover, the system might not detect number changes for calls and stored the initial number only | 9.5.5.5985 | 2020-07-01 |
RI-021560 | Recording - IPTrade |
BT IPTrade TPO recording: call type was determined only for the master call leg but not for turret legs | 9.5.5.5985 | 2020-06-30 |
RI-018964 | Recording - BT ITS |
BT ITS trader name metadata was not properly looked up if the trader was configured with extended trader ID and it did not match the legacy ID and provisioning source was TMS file | 9.5.0.5894 | 2020-01-16 |
RI-019631 | Recording - BT ITS |
If BT ITS TTP staggering time for a given TTP was longer than TTP initialization timeout, recorder considered TTP as failed for a short period of time. This resulted in a false TTP Down alert and in the case of dynamic load balancing of TTPs, it could trigger a Media Recorder failover unnecessarily | 9.5.0.5899 | 2020-02-24 |
RI-020096 | Recording - BT ITS |
BT username metadata field was updated on the media record if this information was arrived after creating the media/vox record (next media/vox record contained this information properly) | 9.5.1.5922 | 2020-03-24 |
RI-021544 | Recording - BT ITS |
Line label changes from TMS/LDAP did not trigger refreshing the line label information on the calls | 9.5.4.5979 | 2020-06-25 |
RI-019004 | Recording - IPC |
The Line Description and the Direction fields were missing from the IPC Unigy Metadata Template in case of some specific upgrade paths | 9.5.0.5894 | 2019-12-13 |
RI-019571 | Recording - IPC |
Media recording could stop when there was a Media Recorder failure at the same time when there was a new media session establishment | 9.5.0.5894 | 2020-02-04 |
RI-019963 | Recording - IPC |
IPC Unigy CTI connection up (Recording Provider Up) alert was sent out with wrong alert type (Recording Provider Down) | 9.5.1.5911 | 2020-03-18 |
RI-020002 | Recording - IPC |
Unified Call Recorder Service could not be started in rare cases after server power failure due to corrupted local SQL cache | 9.5.1.5911 | 2020-03-06 |
RI-020639 | Recording - IPC |
Recording for IPC Unigy softclients did not work because the recorder did not offer AES_CM_128_HMAC_SHA1_80 for SRTP | 9.5.2.5958 | 2020-05-11 |
RI-020772 | Recording - Cloud9 |
Cloud9 import failed when microphone was set for device type in case of ring down calls | 9.5.2.5963 | 2020-05-14 |
RI-018929 | UI - Web Interface |
Group Membership Primary flag was reset to the Default group when the administrator could not see the Primary checkbox (because of the HideFeatures setting) | 9.5.0.5894 | 2020-01-27 |
RI-019550 | UI - Web Interface |
Azure AD and ADFS SSO did not work when the web application was behind a load balancer because the wrong Redirect URI was sent to the SSO server | 9.5.0.5894 | 2020-02-06 |
RI-020101 | UI - Web Interface |
"End of retention" field couldn't be saved in Conversation Layout configuration | 9.5.1.5922 | 2020-03-20 |
RI-020103 | UI - Web Interface |
Verify Signature displayed "Signature file not found" when the files were stored on non-SMB/DFS storage targets | 9.5.1.5922 | 2020-03-20 |
RI-020106 | UI - Web Interface |
After an upgrade from 9.4 or older version, if a user was removed from the AD before the first Verba AD Sync run, then the user was not deactivated, because her Object GUID was not set in the Verba database | 9.5.1.5922 | 2020-03-19 |
RI-020154 | UI - Web Interface |
User Bulk Update modified users out of scope when the Enable Modality Based Direction Rules is enabled and the updated fields contained Modalities | 9.5.1.5923 | 2020-03-30 |
RI-020155 | UI - Web Interface |
Import Sources were visible in all tenants | 9.5.1.5923 | 2020-03-30 |
RI-020178 | UI - Web Interface |
Playback of the transcoded video file did not work when the files were stored on a WORM storage and the transcoded file was not on the storage but only in the local file cache | 9.5.2.5928 | 2020-03-30 |
RI-020317 | UI - Web Interface |
Login screen did not work when the session expired on a dashboard | 9.5.2.5944 | 2020-04-09 |
RI-020357 | UI - Web Interface |
The Audit Log Details report did not filter for the tenant | 9.5.2.5947 | 2020-04-21 |
RI-020577 | UI - Web Interface |
The group supervisor was not able to search on the users already removed from the supervised group | 9.5.2.5953 | 2020-04-30 |
RI-020583 | UI - Web Interface |
Administrators with Ready-Only Extensions permissions could invalidate extensions when they had Users/Groups Update permission | 9.5.2.5953 | 2020-04-28 |
RI-020642 | UI - Web Interface |
Playback of the transcoded video file did not work when the files were stored on a NAS accessible by custom credentials, and the record was signed | 9.5.2.5958 | 2020-05-08 |
RI-020786 | UI - Web Interface |
Verify Signature displayed error when the recordings were signed but not encrypted and the files were stored on storage that did not support UNC path | 9.5.3.5966 | 2020-05-19 |
RI-021102 | UI - Web Interface |
Error occurred when deleting an export task while it was still running | 9.5.3.5972 | 2020-06-04 |
RI-021559 | UI - Web Interface |
The Audit Log Types could not be inserted into the database when the Verba database collation differed from the default collation of the database server | 9.5.5.5985 | 2020-07-01 |
RI-020098 | UI - Reporting |
Voice Quality Check Details report only returned the top 100 random records | 9.5.1.5922 | 2020-03-23 |
RI-020783 | UI - Reporting |
Dashboard templates were only available in the reference environment/tenant | 9.5.2.5966 | 2020-05-20 |
RI-020792 | UI - Reporting |
Dashboard filters did not work in widget configuration for pre-populated lists | 9.5.2.5966 | 2020-05-13 |
RI-021104 | UI - Reporting |
Conversations Length Trend Dashboard Widget did not work but displayed a SQL error | 9.5.3.5972 | 2020-06-03 |
RI-021242 | UI - Reporting |
Users CDR Reconciliation Summary report group filters did not work | 9.5.3.5975 | 2020-06-11 |
RI-021244 | UI - Reporting |
Voice Quality Check report issues:
- the report showed that there was an "Overall Score less than 75" filter even when there was no filter at all
- group filter did not work | 9.5.3.5975 | 2020-06-10 |
RI-019654 | Solution - Ethical Wall |
Skype for Business DataShare in conferences (whiteboard, PPT share, polls, Q&A, etc.) was evaluated improperly which resulted in allowing these scenarios if the DataShare session policy configured with IM allow policy. | 9.5.0.5899 | 2020-02-20 |
RI-019656 | Solution - Ethical Wall |
Evaluation of the phone numbers changed to use the numbers without the domain part. When it was using the numbers with the domain-part, it didn't match any phone number based ethical wall rules e.g.: phone number as a conference participant, PSTN calls, phone number as simring. | 9.5.0.5899 | 2020-02-13 |
RI-021551 | Solution - Ethical Wall |
When single directional presence blocking was configured, user A who should have seen the user B's presence was not able to see the user B's presence after login until the first presence change of user B due to blocked presence probing | 9.5.4.5979 | 2020-06-22 |
RI-020781 | Platform - Announcement |
Call setup failed intermittently when Cisco outbound announcement was configured | 9.5.3.5966 | 2020-05-21 |
RI-018959 | Platform - API |
AttachMetaData API call returned affected rows = 0 when there was no metadata attached to the call yet | 9.5.0.5894 | 2020-01-20 |
RI-019976 | Platform - API |
GetMediaEncoded API call did not take the format parameter into account and always returned WAVE files | 9.5.1.5911 | 2020-03-16 |
RI-020285 | Platform - API |
Attach Metadata HTTP Business API call did not work for ongoing conversations | 9.5.2.5940 | 2020-04-07 |
RI-018958 | Platform - Configuration |
If User and Group Full DN information contained special characters, the users were continuously activated and deactivated by Active Directory Synchronization | 9.5.0.5894 | 2020-01-20 |
RI-019144 | Platform - Configuration |
Service reread failure after a Refresh Extension Configuration or an Apply Communication Policy Configuration tasks were not displayed and considered as errors | 9.5.0.5894 | 2019-10-25 |
RI-020581 | Platform - Configuration |
CSP certificates might refer to a KSP key and the system was unable to load the key in that case | 9.5.2.5953 | 2020-04-29 |
RI-020773 | Platform - Configuration |
In the case of IPv6 address in the Media Repository HTTP URL, JTAPI service URL, and Recorder Server URL, the host part was not parsed properly | 9.5.2.5963 | 2020-05-13 |
RI-019989 | Platform - Database |
The update-for-9.4.sql script threw an error under certain circumstances when there were calls marked as Private | 9.5.1.5911 | 2020-03-10 |
RI-020006 | Platform - Database |
Database connection error handling improved to reduce unnecessary alerts | 9.5.1.5911 | 2020-03-04 |
RI-020356 | Platform - Database |
The Daily Maintenance Job threw an error when the same ccdr_id existed in section1 and section2 tables | 9.5.2.5947 | 2020-04-21 |
RI-021556 | Platform - Database |
Snapshot Isolation update conflict could result in partial data updates in e.g. Active Directory synchronization when recorded extensions were not added | 9.5.4.5979 | 2020-06-15 |
RI-021558 | Platform - Database |
Disposal Log entries were not created | 9.5.5.5985 | 2020-07-01 |
RI-021099 | Platform - Licensing |
License Usage was not logged when there were multiple tenants | 9.5.3.5972 | 2020-06-05 |
RI-019511 | Platform - Media Processing |
Storage Service and/or Media Codec could crash when mixing video in specific layouts | 9.5.0.5894 | 2020-02-13 |
RI-019512 | Platform - Media Processing |
If mobile video recording changes the aspect ratio (landscape/portrait, mobile is rotated 90 degrees), the video layout did not adapt to it and distorted the picture | 9.5.0.5894 | 2020-02-13 |
RI-019536 | Platform - Media Processing |
Media records stuck in ongoing state could prevent users to playback calls referencing the media channel | 9.5.0.5894 | 2020-02-11 |
RI-019613 | Platform - Media Processing |
Transcoding for desktop screen capture did not work when the total resolution if the screens were higher than 2048x2048 pixel | 9.5.0.5898 | 2020-02-18 |
RI-020572 | Platform - Media Processing |
If Siren stream had loss the decoding might crash during transcoding | 9.5.2.5953 | 2020-05-04 |
RI-020582 | Platform - Media Processing |
In rare cases, video streams might have had a color defect at mixing | 9.5.2.5953 | 2020-04-29 |
RI-020776 | Platform - Media Processing |
In the case of MP4 transcoding, when there was a long gap in the video (video was turned off and on again), then instead of showing black screen, the last frame was repeated | 9.5.2.5963 | 2020-05-13 |
RI-021237 | Platform - Media Processing |
Memory consumption could increase temporarily dramatically (up to 4-6 GBytes) if there was a gap in the video stream during MP4 encoding | 9.5.3.5975 | 2020-06-12 |
RI-021547 | Platform - Monitoring |
Memory leak in OpenSSL 1.1.1 caused memory issues for the following services:
- Node Manager Agent
- System Monitor
In the case of the Node Manager Agent service, the service could leak 10 MBytes per hour when e.g. the Service Control page as open in the web application. | 9.5.4.5979 | 2020-06-25 |
RI-018951 | Platform - Storage Management |
Export did not work for Bloomberg voice | 9.5.0.5894 | 2020-01-21 |
RI-019059 | Platform - Storage Management |
The number of maximum files for media stitching was limited to 512, it is unlimited from now on | 9.5.0.5894 | 2019-11-23 |
RI-019368 | Platform - Storage Management |
The Encrypt and Sign policy tried to re-encrypt the files which were already encrypted when a new certificate was selected | 9.5.0.5894 | 2019-09-03 |
RI-019605 | Platform - Storage Management |
EMC Isilon SmartLock secure API connection did not work | 9.5.0.5898 | 2020-02-14 |
RI-019967 | Platform - Storage Management |
Exporting instant messages in a multitenant environment (when the transcript file was not available on the storage) resulted in an incorrect output path | 9.5.1.5911 | 2020-03-18 |
RI-019987 | Platform - Storage Management |
The upload policies in a multitenant environment do not take into account the tenant EID if the policy did not contain filters | 9.5.1.5911 | 2020-03-12 |
RI-019992 | Platform - Storage Management |
Player based video transcoding did not work on SMB shares with custom credentials | 9.5.1.5911 | 2020-03-09 |
RI-020016 | Platform - Storage Management |
Playback did not work in some cases for imported calls from a Verint WFO system when the medial files (TAR) were archived on EMC Centera | 9.5.1.5911 | 2020-02-27 |
RI-020108 | Platform - Storage Management |
Deduplication did not work due to database transaction rollback issues | 9.5.1.5922 | 2020-03-18 |
RI-020124 | Platform - Storage Management |
Deduplication of encrypted records (Avaya, Skype for Business, Passive SIP) could invalidate crypto information when the secondary recording was considered better than the primary copy. This caused the file to be unusable. | 9.5.1.5922 | 2020-03-27 |
RI-020179 | Platform - Storage Management |
Metadata XML files for CDR-only records were not uploaded to EMC Centera and ECS | 9.5.2.5933 | 2020-04-03 |
RI-020353 | Platform - Storage Management |
SfB application share (RDP only) recordings could not be transcoded on SMB storages when custom SMB credentials were used | 9.5.2.5947 | 2020-04-22 |
RI-020585 | Platform - Storage Management |
.g729 files were not properly handled at export and playback, transcoding showed an error message about not supported codec | 9.5.2.5953 | 2020-04-28 |
RI-020854 | Platform - Storage Management |
SfB application share (VMF files) recordings could not be transcoded on SMB storages when custom SMB credentials were used | 9.5.3.5969 | 2020-05-25 |
RI-020856 | Platform - Storage Management |
Data retention times beyond 2038 could not be applied on Netapp SnapLock | 9.5.3.5969 | 2020-05-25 |
RI-021100 | Platform - Storage Management |
Export failed randomly from Amazon S3 and Amazon S3 compatible storage targets | 9.5.3.5972 | 2020-06-05 |
RI-021243 | Platform - Storage Management |
Export of encrypted calls might not export the encryption info file if the media was not to be transcoded | 9.5.3.5975 | 2020-06-10 |
RI-021245 | Platform - Storage Management |
Call export did not work if the voice transcoding format specified was the same as the original file format | 9.5.3.5975 | 2020-06-10 |
RI-021640 | Platform - Storage Management |
Connection error with EMC Isilon SmartLock when special characters were used in API credentials | 9.5.5.5985 | 2020-07-02 |
RI-019517 | Platform - CDR and Archived Content Import |
Cisco CDR Column Filters configuration did not work for Cisco CDR reconciliation | 9.5.0.5894 | 2020-02-13 |
RI-019524 | Platform - CDR and Archived Content Import |
Cisco CDR reconciliation could not filter out calls on shared lines which were handled by non-recorded users | 9.5.0.5894 | 2020-02-12 |
RI-020368 | Platform - CDR and Archived Content Import |
Some of the policy settings are not refreshed on-the-fly for Import policies which are running non-scheduled | 9.5.2.5947 | 2020-04-14 |
RI-020491 | Platform - CDR and Archived Content Import |
In the case of persistent SQL Server connection errors, the system might have skipped CDRs during reconciliation | 9.5.2.5952 | 2020-04-24 |
RI-020644 | Platform - CDR and Archived Content Import |
The CDR Import service crashed during recheck when it tried to delete a failed CDR | 9.5.2.5958 | 2020-05-08 |
RI-020767 | Platform - CDR and Archived Content Import |
CDR import was unable to update Skype for Business conference participants | 9.5.2.5963 | 2020-05-15 |
RI-021552 | Platform - Labeling |
Labeling did not work in case of special characters were used in the configuration | 9.5.4.5979 | 2020-06-18 |
RI-020490 | Platform - Import |
CSV file import failed using the generic importer when the last character was a number in the CSV file and it contained a NULL character | 9.5.3.5952 | 2020-04-28 |
RI-021112 | Platform - Import |
Generic import: Improve possible value handling of expressions for constants. In case of "IF" function value can be picked from possible value list. | 9.5.3.5972 | 2020-05-26 |