| RI-032203 | Security |
Multiple security and vulnerability fixes for the Web Application:
- Cross-site scripting (XSS) vulnerability in SilverLight component
- Directory Manipulation/Traversal in Verint v11/v155 migration module
- XML External Entity injection in Verint v11/v155 migration module
- Login ID will not be filled in with the received parameter on the login page
- Client-side HTTP parameter pollution (reflected) fixes
- The User Import Sample XLS could be downloaded without Bulk User Import permission
- The "Export to XLS" links could be accessed without permissions to the given feature
- HTTP Business API reflected the action parameter unescaped | 9.7.5.7598 | 2022-08-30 |
| RI-032665 | Security |
The internal API ports did not take into account the TLS cipher restrictions configured under Server Certificate/Advanced TLS Settings/Suite Constraints for the following services: Verba System Monitor Service, Verba Passive Recorder Service, Verba Node Manager Agent, Verba Analogue and Radio Recorder Service, Verba Storage Management Service, Verba Media Utility Service, Verba Media Streamer and Content Server Service, Verba Dial-in Recorder Service
Verba Screen Capturing Service, Verba Screen Capture Multiplexer Service, Verba Centile Connector Service, Verba Media Collector and Proxy Service,
Verba Speech Analytics Service, Verba Import Service, Verba Unified Call Recorder Service, Verba Unified IM Recorder Service, Verba Cisco Announcement Service, Verba SMS Recorder Service | 9.7.6.7735 | 2022-10-21 |
| RI-032808 | Security |
Multiple minor security and vulnerability fixes for the Web Application:
- No Content Security Policy (CSP) was Defined for the root / URI
- HTTP Strict Transport Security (HSTS) was Not Enforced at /verba/ssoAdal
- Client-side HTTP parameter pollution (reflected) fixes at multiple pages
- Login screen's password fields will have autocomplete="off", the other password fields remain autocomplete="new-password"
- Removed the unused Apache commons-text-1.6.jar library | 9.7.7.7871 | 2022-12-19 |
| RI-031565 | Recording - 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 | 9.7.1.7383 | 2022-05-19 |
| RI-031569 | Recording - 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 | 9.7.1.7383 | 2022-05-19 |
| RI-031616 | Recording - 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. | 9.7.1.7383 | 2022-05-19 |
| RI-031658 | Recording - 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 | 9.7.1.7383 | 2022-05-19 |
| RI-031972 | Recording - Cisco |
After a Unified Call Recorder Service crash, the recovered partial record was closed and the event was always sent to the first JTAPI service in the list, which if was down/non-existing but not removed from the configuration, then the call could not be closed in the database. | 9.7.4.7502 | 2022-07-19 |
| RI-032539 | Recording - Cisco |
The Owner User ID was not determined in some call scenarios and user assignment did not work for these call legs | 9.7.6.7735 | 2022-10-21 |
| RI-033533 | Recording - Cisco |
Very short recorded calls caused the Cisco JTAPI Service to unnecessarily store the CDR information in the memory for a few hours | 9.7.7.7871 | 2022-12-19 |
| RI-031884 | Recording - Lync/SfB |
The recording did not start after hold/resume if advanced relay mode was enabled | 9.7.2.7418 | 2022-06-01 |
| RI-033606 | Recording - Lync/SfB |
Microsoft Skype for Business and Teams interop call scenarios were not working when Citrix HDX RealTime Optimization Pack was used with VDI clients due to Citrix limitations. The issue impacted call scenarios with devices connecting external networks which require the SfB Edge servers. The new Citrix HDX version will be available, for more information, please contact your Citrix representative.
An earlier partial workaround was implemented for the issue, which is now removed. It is necessary to deploy the new version of the Verba Media Collector and Proxy Service along with the new Citrix HDX version to fully resolve the issue.
Update: the new Citrix HDX version is available for download at https://www.citrix.com/downloads/citrix-receiver/additional-client-software/hdx-realtime-media-engine-29600.html | 9.7.7.7871 | 2022-12-19 |
| RI-031783 | Recording - Lync/SfB IM |
The Skype for Business IM Filter service didn't parse the HTML message properly and skipped e.g. special characters in group chats. | 9.7.2.7418 | 2022-06-01 |
| RI-031695 | Recording - Microsoft Teams |
When a P2P call was escalated into a meeting while one of the participants put the call on hold, the media packets were skipped from recording. | 9.7.2.7418 | 2022-06-01 |
| RI-032033 | Recording - Microsoft Teams |
The Verba Microsoft Teams Bot Service stopped listening for incoming recorder connections after 5 unsuccessful attempts. | 9.7.4.7502 | 2022-07-19 |
| RI-032408 | Recording - Microsoft Teams |
In the case of sending the RAW PCM-16 audio stream to the recording service, the recorded audio content became static noise. | 9.7.5.7598 | 2022-08-30 |
| RI-032440 | Recording - Microsoft Teams |
In the case of participants with unknown UPN, the participant list filtered out the multiple participants with the same join time. | 9.7.5.7598 | 2022-08-30 |
| RI-032559 | Recording - Microsoft Teams |
If the meeting's organizer was not part of any provisioned tenants, the To Info doesn't contained the organizers display name. | 9.7.6.7735 | 2022-10-21 |
| RI-032561 | Recording - Microsoft Teams |
The 'Record Only If External User is Participating' configuration was applied for P2P calls too | 9.7.6.7735 | 2022-10-21 |
| RI-032659 | Recording - Microsoft Teams |
Microsoft Teams video playback or transcoding failed if PCM16 audio was recorded in VMF format | 9.7.6.7735 | 2022-10-21 |
| RI-033337 | Recording - Microsoft Teams |
The Microsoft Teams Bot service didn't continue recording after the hold-resume scenario when controlled recording was used. The issue affects 9.7.6 or later only. | 9.7.7.7871 | 2022-12-19 |
| RI-033338 | Recording - Microsoft Teams |
The Microsoft Teams Bot service didn't reread the environments.xml for changed multi-tenant configuration in the case of configuration reread. It required a service restart to apply the new tenant configuration. | 9.7.7.7871 | 2022-12-19 |
| RI-033339 | Recording - Microsoft Teams |
The direction of PSTN calls to a call queue service was not identified and the calls were stored as unidentified calls. The issue affects v9.7.6 or later only. | 9.7.7.7871 | 2022-12-19 |
| RI-033500 | Recording - Microsoft Teams |
The Microsoft Teams Bot was not prepared to handle transferors other than type user. In the cases of service transferred calls (e.g.: Call Queue) the bot failed to process the INVITE. The issue only affects v9.7.6 or later versions. | 9.7.7.7871 | 2022-12-19 |
| RI-033528 | Recording - Microsoft Teams |
When the Microsoft Teams Bot Service did not determine the direction of the call yet but the recording and show notification decisions had to be made, the recording was started but the recording notification was not shown. The issue only affects v9.7.6 or later versions. | 9.7.7.7871 | 2022-12-19 |
| RI-033672 | Recording - Microsoft Teams |
Stereo recording didn't work since v9.7.6. It caused both P2P and meeting stereo recording to produce one-way audio in the recordings. | 9.7.7.7871 | 2022-12-19 |
| RI-033674 | Recording - Microsoft Teams |
The Microsoft Teams Bot Service didn't use the participant information from the participant list in the case of failed Graph API queries. Graph API queries failed when the bot tried to query a tenant which is not a recorded/provisioned tenant by the bot. The issue only affects v9.7.6 or later versions. | 9.7.7.7871 | 2022-12-19 |
| RI-031835 | Recording - Microsoft Teams IM |
Microsoft Teams instant message archiving fixes:
- Archived channel from teams point of view: file share recording was evaluated only from the participants' point of view, i.e. if only the team was archived, file attachments were not fetched
- Webhook subscription license model change was not handled properly, did not delete the existing subscription but created a new subscription leading to subscription errors/alerts till the previous subscription expired
- CDR information was not always updated with participant changes for P2P and group chats (To and To Info fields)
- SQL insert error due to possible truncations revised
- Attachment download failed when the server returned the content with gzip/deflate content encoding
- In case of a high number of processing queues, the service stopped slowly
- Queue processing might have stuck if another process deleted the batch files meanwhile the service processed the queue folder | 9.7.2.7418 | 2022-06-01 |
| RI-031958 | Recording - Microsoft Teams IM |
If a participant left and rejoined a chat or channel later, the next join event was not added to the participation list. Also, if the service was stopped while someone left a chat or channel, the leave time was not updated after the service start. | 9.7.4.7502 | 2022-07-19 |
| RI-032442 | Recording - Microsoft Teams IM |
Upload could fail due to database error when multiple threads uploaded Microsoft Teams chat attachments related to the same chat or channel when multiple attachments were sent in a short timeframe. The system raised an alert and retired the upload. | 9.7.5.7598 | 2022-08-30 |
| RI-033040 | Recording - Microsoft Teams IM |
Microsoft Teams chat and channel attachment download did not work from SharePoint/OneDrive when the URL contained an already URL escaped character sequence. | 9.7.7.7871 | 2022-12-19 |
| RI-033117 | Recording - Microsoft Teams IM |
Microsoft Teams chat message history showed duplications for the Microsoft Teams Export API based integration. Channel messages were not impacted. | 9.7.7.7871 | 2022-12-19 |
| RI-033120 | Recording - Microsoft Teams IM |
Microsoft Teams chat message was not shown in the viewer when the Microsoft Teams Export API was used and the same message was recorded with a different timestamp for another user. Channel messages were not impacted. | 9.7.7.7871 | 2022-12-19 |
| RI-033152 | Recording - Microsoft Teams IM |
Microsoft Teams chat or channel attachments were not visible randomly in the viewer when stored on a network drive that needed custom credentials | 9.7.7.7871 | 2022-12-19 |
| RI-033198 | Recording - Microsoft Teams IM |
Search did not return Microsoft Teams messages when there was only a reply, edit or delete on the original message in the query interval, because the hourly activity markers were created based on the original message timestamp instead of the last modification timestamp leading to not creating activity for reply/modify/delete messages (if there wasn't any other activity in that hour). | 9.7.7.7871 | 2022-12-19 |
| RI-033350 | Recording - Microsoft Teams IM |
Microsoft Teams chat or channel attachment download failed with error code 404 (file not found) if the file name contained more than one space after each other | 9.7.7.7871 | 2022-12-19 |
| RI-033496 | Recording - Microsoft Teams IM |
Microsoft Export API based chat and channel archiving did not work for multitenant environments as extensions were not queried on the related Teams tenant's connection | 9.7.7.7871 | 2022-12-19 |
| RI-031706 | Recording - Unified Call Recorder |
Q.850 cause 31 ("normal, unspecified" call clearing) was considered as abnormal/premature call termination leading to call processing alerts in SIP integrations once the call was terminated with this reason. The issue was identified in a Ribbon SBC SIPREC based integration. | 9.7.2.7418 | 2022-06-01 |
| RI-032703 | Recording - Unified Call Recorder |
E-Dialer: if master call lookup query did not find the leg, it was not retried as desired, only at call start/end/timeout. The master call lookup query was slow and is now optimized to get benefit from some new indexing | 9.7.6.7735 | 2022-10-21 |
| RI-033276 | Recording - Unified Call Recorder |
The Unified Call Recorder service ignores the CDR-Only records when calculating the maximum concurrent call count for the service overload report because those records have no performance impact on the server. This improvement is relevant for configurations where the Media Recorder and the Recording Director roles are co-located and cross-connected. | 9.7.7.7871 | 2022-12-19 |
| RI-033282 | Recording - Unified Call Recorder |
After a long time, the communication between the Media Recorder and the Recording Director could have slowed down causing voice clipping at the beginning of the recordings if:
- the "Force Recording on Director" was enabled for a trader voice integration
- and the servers were cross-connected as remote Media Recorders | 9.7.7.7871 | 2022-12-19 |
| RI-032031 | Recording - IPTrade |
IPTrade turret playback with password authentication did not work | 9.7.4.7502 | 2022-07-19 |
| RI-032405 | Recording - IPTrade |
When using IP Trade SIPREC based integration, multiple TPO master legs in the same recording sessions were not handled properly, leading to incorrect turret side CDR information | 9.7.6.7735 | 2022-10-21 |
| RI-032523 | Recording - IPTrade |
IP Trade device type might have changed from/to 'Unknown' which caused CDR termination/new CDR because of the device change | 9.7.6.7735 | 2022-10-21 |
| RI-032666 | Recording - IPTrade |
IP Trade generates dummy CDRs with 'fakeuser' which are now filtered out | 9.7.6.7735 | 2022-10-21 |
| RI-033374 | Recording - IPTrade |
Conference participants were not stored properly for BT IP Trade SIPREC based integrations | 9.7.7.7871 | 2022-12-19 |
| RI-031649 | Recording - 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. | 9.7.1.7383 | 2022-05-19 |
| RI-031916 | Recording - Speakerbus |
When the system missed the initial call start event and the call was created based on the heartbeat event, the media stream - call association was shifted causing wrong mixing during playback. In the case of the first recording channel/mix, the system did not record the media stream and generated a "Media descriptors are not available for the call" alert.
Also, the metadata was not complete, because the system did not update the metadata using mid-call events causing incomplete data for segmented records. | 9.7.3.7434 | 2022-06-10 |
| RI-033212 | Recording - IPC |
IPC Unigy: if a call was extremely short, the related start/end event might have arrived out of order causing a stuck CDR record till a daily CTI connection refresh or trader logout or a new call on the line | 9.7.7.7871 | 2022-12-19 |
| RI-033495 | Recording - IPC |
IPC Unigy: race condition between SIP and CTI messages at agent logoff might have caused a false positive media mix lost alert | 9.7.7.7871 | 2022-12-19 |
| RI-032196 | Recording - Cloud9 |
Import Service used a high amount of memory and eventually crashed when the Cloud9 Recording System API integration was used with a load balancer. The fix includes:
- A new, specific health probe endpoint to separate the handling of these requests
- Memory cache optimization
- Work folder cleanup optimization | 9.7.5.7598 | 2022-08-30 |
| RI-032648 | Recording - Cloud9 |
When using the Cloud9 Recording System API based integration, after successfully importing the data, the C9 client expected a blank HTTP response with status code 201 | 9.7.6.7735 | 2022-10-21 |
| RI-032333 | Recording - Dial-in |
The playback feature did not work in the Dial-in Recorder Service for calls imported as MP3 or M4A audio files | 9.7.5.7598 | 2022-08-30 |
| RI-032420 | Recording - SMS |
SMS Recorder Service did not insert data into the right tenant, instead it inserted all data into the reference tenant in multi-tenant deployments | 9.7.5.7598 | 2022-08-30 |
| RI-031704 | Recording - Symphony |
Workaround implemented for late stream negotiations (where media starts coming before it is communicated with the recorder) which can cause issues with sharer/viewer role changes, resulting in missing a few video frames before the role has changed | 9.7.2.7418 | 2022-06-01 |
| RI-033383 | Recording - Genesys |
The Verba Genesys CTI Service sent a stop recording command to the Genesys T-Server in the case of hold scenarios even when the recording was not triggered by the CTI service. When the call was resumed, the CTI service didn't sent the start command therefore the T-Server never restarted the call recording. | 9.7.7.7871 | 2022-12-19 |
| RI-031557 | Recording - Zoom |
Workaround for missing participant leave date (unexpected) for Zoom Meeting imports | 9.7.1.7383 | 2022-05-19 |
| RI-032256 | Recording - Zoom |
Zoom import did not work due to timeout issues when the system was configured to retrieve a large amount of data via thousands of result pages | 9.7.5.7598 | 2022-08-30 |
| RI-032328 | Recording - Zoom |
Media upload did not work in certain regions due to unannounced changes in the authentication method in the Zoom APIs | 9.7.5.7598 | 2022-08-30 |
| RI-032414 | Recording - Zoom |
Zoom Meeting import did not work when a date field was empty (unexpectedly) | 9.7.5.7598 | 2022-08-30 |
| RI-032740 | Recording - Zoom |
Multiple Zoom Meeting and Phone import related fixes:
- Fixed a bug where meeting participants were missed if multiple recorded users joined a meeting at the same second
- Fixed a bug where meeting participation were recorded twice with different CDR IDs if two Verba Import Service on different servers import the same meeting within milliseconds of each other
- Fixed a media download issue for some storage host cloud regions of Zoom that required different authentication than others | 9.7.6.7735 | 2022-10-21 |
| RI-033323 | Recording - Zoom |
When using a redundant Zoom import configuration (multiple serves were enabled for importing the same data), in very rare cases, a single or few participants of a meeting were missed during import without error messages. The issue was related to a database lock. If CDR reconciliation was enabled, the system raised alerts for missing recordings. | 9.7.7.7871 | 2022-12-19 |
| RI-033369 | Recording - Zoom |
Import Service could have crashed when a Zoom phone/meeting import with CDR reconciliation was configured using no scheduling and the service level schedule was set to less than 60 seconds. | 9.7.7.7871 | 2022-12-19 |
| RI-031640 | UI - Web Interface |
Right-click options / Same day features on the conversations screen chose the day in UTC timezone instead of the user's timezone | 9.7.1.7383 | 2022-05-19 |
| RI-031644 | UI - Web Interface |
Advanced IM viewer (Microsoft Teams) failed to render a message if it was a message reference without a proper user display name. | 9.7.1.7383 | 2022-05-19 |
| RI-031757 | UI - Web Interface |
The Identity Providers were not saved when saving a Role, the issue only affects v9.7.1 and later | 9.7.2.7418 | 2022-06-01 |
| RI-031888 | UI - Web Interface |
The column names were not visible in the Excel list export because the color of the text was white | 9.7.2.7418 | 2022-06-01 |
| RI-031921 | UI - Web Interface |
Conversations without media files could not be deleted on the web interface | 9.7.3.7434 | 2022-06-10 |
| RI-032290 | UI - Web Interface |
The advanced export task couldn't be created in other tenants, only in the reference environment | 9.7.5.7598 | 2022-08-30 |
| RI-032335 | UI - Web Interface |
The Advanced Export Rename Files feature was not always available for the selected Storage Target depending on the selected type | 9.7.5.7598 | 2022-08-30 |
| RI-032417 | UI - Web Interface |
The "Do not request PIN on Recorder Line" configuration was not visible on the Extension detail screen | 9.7.5.7598 | 2022-08-30 |
| RI-032436 | UI - Web Interface |
The Synchronized Active Directory Group could not be removed from the Active Directory Profile when the Group Name could not be determined | 9.7.5.7598 | 2022-08-30 |
| RI-032438 | UI - Web Interface |
Reverse Proxy based SSO did not work for the first time, also added an option to turn off the Session ID renewal | 9.7.5.7598 | 2022-08-30 |
| RI-032506 | UI - Web Interface |
Transcript highlight was not followed when scrolling was needed, if manually scrolled it jumped back to the first sentence once releasing the scroll bar | 9.7.5.7598 | 2022-08-30 |
| RI-032549 | UI - Web Interface |
Microsoft Teams chat PDF export didn't download the generated PDF file in the Viewer | 9.7.6.7735 | 2022-10-21 |
| RI-032581 | UI - Web Interface |
The Recorded Voice Quality Issues dashboard widget search filter did not consider the Secondary flag when the Search menu opened through the widget | 9.7.6.7735 | 2022-10-21 |
| RI-032585 | UI - Web Interface |
The Change Configuration Settings screen's Refresh link displayed an error | 9.7.6.7735 | 2022-10-21 |
| RI-032586 | UI - Web Interface |
The back link at the "Configuration tasks to be executed" page caused an infinite loading screen | 9.7.6.7735 | 2022-10-21 |
| RI-032635 | UI - Web Interface |
Encrypted calls could not be played back when the Direct URL was used to open the Conversation Details | 9.7.6.7735 | 2022-10-21 |
| RI-032654 | UI - Web Interface |
When a Data Retention Policy / Role / Label Rule filter with "Matches a Value in the List" operation changed, and the "Matches a Value in the List" operation was chosen again, then the filter input field did not show | 9.7.6.7735 | 2022-10-21 |
| RI-032701 | UI - Web Interface |
The Audit Log entry details were missing for the Login event | 9.7.6.7735 | 2022-10-21 |
| RI-032702 | UI - Web Interface |
After a successful login and logout and one more successful login, the login screen was displayed instead of the main screen | 9.7.6.7735 | 2022-10-21 |
| RI-032708 | UI - Web Interface |
System error showed instead of a warning if the user tried to delete an Import Source (or Data Processor) that has been already tied to a policy | 9.7.6.7735 | 2022-10-21 |
| RI-033272 | UI - Web Interface |
Transcription displayed unnecessary Speaker entries in the viewer when the user searched for a phrase | 9.7.7.7871 | 2022-12-19 |
| RI-033296 | UI - Web Interface |
Search hit highlights were not displayed in the search list | 9.7.7.7871 | 2022-12-19 |
| RI-033352 | UI - Web Interface |
Phone Number Masking on the UI did not work for the Conversation Participants on the Conversation Detail and the Search page | 9.7.7.7871 | 2022-12-19 |
| RI-033680 | UI - Web Interface |
Azure Active Directory Synchronization Profile Group selection didn't work due to recent browser security enhancements | 9.7.7.7871 | 2022-12-19 |
| RI-031656 | UI - Reporting |
The Roles and Permissions report did not work when there was a Role with the "Unable to Access Conversations Older than | 9.7.1.7383 | 2022-05-19 |
| RI-031758 | UI - Reporting |
Dashboards couldn't be created by a user whose email address property was missing | 9.7.2.7418 | 2022-06-01 |
| RI-031941 | UI - Reporting |
The Not Recorded and Incorrect Conversations Details report only showed user related calls, while the Recording Assurance Dashboard has shown the non-user related ones too, thus the report was modified to show the non-user related calls too. Fixed the not user-related calls 'null' value to 'Unknown' and the reporter user's 'null' value to the creator user. | 9.7.4.7502 | 2022-07-19 |
| RI-032411 | UI - Reporting |
The Recorded Voice Quality Issues dashboard widget search filter did not correlate to the Search menu when opened through the widget | 9.7.5.7598 | 2022-08-30 |
| RI-032590 | UI - Reporting |
User Instant Messaging Details Report Participants - fixing "null" when having odd numbered participants | 9.7.6.7735 | 2022-10-21 |
| RI-032741 | UI - Reporting |
Roles and Permissions report did not work in v9.7.5 | 9.7.6.7735 | 2022-10-21 |
| RI-032855 | UI - Reporting |
Dashboard widgets showed "No displayable content" when the widget was opened in full screen mode before their content has been loaded completely. | 9.7.7.7871 | 2022-12-19 |
| RI-033320 | UI - Reporting |
Audit Log Details report displayed date values in the wrong timezone | 9.7.7.7871 | 2022-12-19 |
| RI-033080 | Solution - Quality Management |
The form designer in the case of a Multiple Choice Question showed the wrong default value. | 9.7.7.7871 | 2022-12-19 |
| RI-032147 | Platform - Announcement |
In case of the outbound announcement, on the outbound call leg invalid SDP was generated if application stream was offered as well on the inbound leg and it did not include stream level connection info | 9.7.5.7598 | 2022-08-30 |
| RI-031954 | Platform - API |
Verba Import API did not work in some cases and generated an error message about content length mismatch | 9.7.4.7502 | 2022-07-19 |
| RI-032410 | Platform - API |
HTTP Business API GetCallInformation endpoint result had a missing conversation "state" attribute on the "verbacdr" element. | 9.7.5.7598 | 2022-08-30 |
| RI-031568 | Platform - 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. | 9.7.1.7383 | 2022-05-19 |
| RI-031991 | Platform - Configuration |
Node Manager Service restart might randomly fail because a previous instance of the service was still running | 9.7.4.7502 | 2022-07-19 |
| RI-032733 | Platform - Configuration |
Directory settings generated by the installer from the Media Folder set during installation, could not be changed later (ondemand, playback cache folders). These settings can be changed under Directories in the server configuration. | 9.7.6.7735 | 2022-10-21 |
| RI-033351 | Platform - Configuration |
Import source selection based restriction for recorded extension configuration was not taken into account (except for Zoom and RingCentral) and the import sources used the extension regardless. | 9.7.7.7871 | 2022-12-19 |
| RI-032293 | Platform - Database |
Database maintenance job alert was raised if the job was not able to insert a NULL value in the job logs table | 9.7.5.7598 | 2022-08-30 |
| RI-033151 | Platform - Database |
Index rebuild could have stuck when estimating really long time for the index rebuild during the database maintenance process. This could have impacted the other processes in the database maintenance such as automatic labeling, moving data from temp tables to the final table, etc. The index rebuild job which got stuck generated a large amount of maintenance log entries. | 9.7.7.7871 | 2022-12-19 |
| RI-033259 | Platform - Database |
Search related features became unavailable when an index rebuild was started while an advanced export was running at the same time. | 9.7.7.7871 | 2022-12-19 |
| RI-032014 | Platform - Media Processing |
VOH/ViQ media converter did not create the G.722 codec stream if the source MP4 audio track had a greater than 16 kHz sampling rate | 9.7.4.7502 | 2022-07-19 |
| RI-032029 | Platform - Monitoring |
The Unfiied Call Recorder, the Unified IM Recorder, the Passive Recorder and the Media Collector and Proxy services could have crashed if the service statistics could not be retrieved in a timely fashion (for deadlock detection) in the case of 3rd party processes running from a network share. | 9.7.4.7502 | 2022-07-19 |
| RI-032726 | Platform - Monitoring |
Missing event ID object in the alert definitions in the SNMP MIB | 9.7.6.7735 | 2022-10-21 |
| RI-031572 | Platform - Storage Management |
Certain Storage Management functions were not automatically retried after recoverable database errors | 9.7.1.7383 | 2022-05-19 |
| RI-031589 | Platform - 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 | 9.7.1.7383 | 2022-05-19 |
| RI-031600 | Platform - 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 | 9.7.1.7383 | 2022-05-19 |
| RI-031691 | Platform - Storage Management |
Playback/download/export/delete features did not work on S3 Compatible storage targets when virtual hosted addressing mode was used and the storage platform did not support double slash in the URL (e.g. IBM COS) | 9.7.1.7385 | 2022-05-20 |
| RI-031703 | Platform - Storage Management |
After transcoding a media in the local cache (non-SMB storages), the MP4 file was uploaded with the wrong filename in the case of SFTP target, causing the overwriting of the original media file (vmf/msrdp). | 9.7.2.7418 | 2022-06-01 |
| RI-031785 | Platform - Storage Management |
Deduplication storage action was unable to find the 2N pairs of a call when 'timestamp-based policy' was enabled. | 9.7.2.7418 | 2022-06-01 |
| RI-031802 | Platform - Storage Management |
Shared recorder/remote cluster ongoing recordings were considered as crashed recordings too at recorder service startup if those were recorded by other recording service running on the same server. This could lead to healthy ongoing calls being terminated by the other recording service running on the same server prematurely in the database, but media was still fully recorded and uploaded properly. | 9.7.2.7418 | 2022-06-01 |
| RI-031919 | Platform - Storage Management |
Advanced Export did not work in 9.7.2 | 9.7.3.7434 | 2022-06-10 |
| RI-031922 | Platform - Storage Management |
FilePath metadata field in Advanced Export was not determined correctly when the file was renamed during transcoding (to mp3 for example) | 9.7.3.7434 | 2022-06-10 |
| RI-031927 | Platform - Storage Management |
Amazon S3 and S3 compatible storage targets did not work since 9.7.2 due to an authentication issue caused by a recent change in the HTTP library | 9.7.3.7434 | 2022-06-10 |
| RI-031957 | Platform - Storage Management |
Move policy was applied to calls under Legal Hold on Amazon S3 Storage Targets even if the Enable Object Lock and Legal Hold setting was turned on | 9.7.4.7502 | 2022-07-19 |
| RI-031981 | Platform - Storage Management |
Hitachi Content Platform storage target did not recognize if files were already uploaded and under retention, and the second try caused an error and an upload failure alert was raised | 9.7.4.7502 | 2022-07-19 |
| RI-031987 | Platform - Storage Management |
AWS S3 virtual host style addressing has been changed on the AWS side and the integration did not work outside of Europe. Previously the virtual path was https://bucket-name.s3-region.amazonaws.com while the new format is https://bucket-name.s3.region.amazonaws.com | 9.7.4.7502 | 2022-07-19 |
| RI-032037 | Platform - Storage Management |
Advanced export did not work for Microsoft Teams IM if the content included adaptive cards/polls or inline image | 9.7.4.7502 | 2022-07-19 |
| RI-032042 | Platform - Storage Management |
False dead transcoding detection (and service restart) during ad hoc transcoding if upload to WORM storage from processing cache did not finish within the dead session timeout. | 9.7.4.7502 | 2022-07-19 |
| RI-032044 | Platform - Storage Management |
SMTP export using plain text was using HTML content type when there was a HTML tag in the content | 9.7.4.7502 | 2022-07-19 |
| RI-032137 | Platform - Storage Management |
EMC Centera Storage Target: when retention was not set for upload or when the calculated retention was pointing to the past then the system set 0 seconds for retention. This caused upload issues when the Centera Pool had a minimum retention configured. From now on if the calculated retention is zero or not set, the system does not set the retention on Centera. | 9.7.4.7502 | 2022-07-19 |
| RI-032332 | Platform - Storage Management |
In the case of dual archiving, if the retention elapsed on one of the storage targets but was not set or not yet elapsed on the other storage target, the automatic deletion entering from a scheduled policy tried to delete both instances. If WORM storage targets were configured, the storage platform did not allow the deletion. | 9.7.5.7598 | 2022-08-30 |
| RI-032362 | Platform - Storage Management |
Trader voice ongoing stitched media files might have been included in call exports if at the time of export they were present in the media cache on the Media Reposirty / Application Servers | 9.7.5.7598 | 2022-08-30 |
| RI-032365 | Platform - Storage Management |
For non policy based uploads, Azure Blob target was not working when the Account Name and Key were set in the service configuration. Instead, it only worked when the Azure Storage Connection String was set. | 9.7.5.7598 | 2022-08-30 |
| RI-032374 | Platform - Storage Management |
Multiple deduplication issues fixed:
- Media records were not deleted during the deduplication process for trader voice conversations for v9.6.17 or later
- Better scoring logic to prefer keeping primary records with configurable thresholds
- Possible crash at deduplication if another server/thread has already deleted the current CDR | 9.7.5.7598 | 2022-08-30 |
| RI-032386 | Platform - Storage Management |
For Amazon S3 and S3 Compatible storage targets, if the Enable Object Lock and Legal Hold setting was not enabled, the system did not apply the retention at all (not even in the database) | 9.7.5.7598 | 2022-08-30 |
| RI-032391 | Platform - Storage Management |
Voice quality check scores were only inserted into the reference tenant in multi tenant configurations | 9.7.5.7598 | 2022-08-30 |
| RI-032418 | Platform - Storage Management |
Policy based IM export failed for Skype for Business chat messages when the URL field of the chat's CDR record was empty | 9.7.5.7598 | 2022-08-30 |
| RI-032602 | Platform - Storage Management |
The ConferenceParticipants placeholder in the SMTP storage target was formatting e-mail addresses wrongly | 9.7.6.7735 | 2022-10-21 |
| RI-032622 | Platform - Storage Management |
SMTP export imTranscript4HTML template fixes:
- Removed quoted printable formatting
- Html linebreaks <br> are used instead of /r/n linebreaks. So replies will appear in multiple lines instead of a single line format
- Reactions are reformatted | 9.7.6.7735 | 2022-10-21 |
| RI-032663 | Platform - Storage Management |
Media files with .ongoing postfix in the file name were generated during export or playback of CDR-Only records without media | 9.7.6.7735 | 2022-10-21 |
| RI-032697 | Platform - Storage Management |
At least two short (<3 sec threshold) device swaps on the same line and mix in trader voice recordings caused multiple 2N pairs matching for deduplication and so skipping deduplication of these short records | 9.7.6.7735 | 2022-10-21 |
| RI-032699 | Platform - Storage Management |
Advanced IM export policy could export attachments multiple times when the Microsoft Teams Export API based integration was used | 9.7.6.7735 | 2022-10-21 |
| RI-032719 | Platform - Storage Management |
When using call based policy execution (default), at determining policies to be executed, the conversation change created by the previous policy was not taken into account in the current policy. For instance, when a Move policy set retention and there was a following Delete policy matching the same call, the system deleted the record even if it was under retention (unless a WROM storage was used). | 9.7.6.7735 | 2022-10-21 |
| RI-032720 | Platform - Storage Management |
If there was an SQL query error in the policy manager thread, the thread exited, and the policy execution has stopped | 9.7.6.7735 | 2022-10-21 |
| RI-032734 | Platform - Storage Management |
WORM/Media stitching cache path (which defaults to media path) could not be an SMB share due to multiple MRs could not properly separate their cache management | 9.7.6.7735 | 2022-10-21 |
| RI-032759 | Platform - Storage Management |
SMTP export fixes for converting URLs to HTML links:
- Long URLs might not be parsed properly
- URLs copied from Microsoft Edge were not parsed properly
- Default date format containing -0000 at the end fix
- Fix for handling URLs with reactions | 9.7.6.7735 | 2022-10-21 |
| RI-032830 | Platform - Storage Management |
The integration with an S3 compatible storage target using the v2 authentication has stopped working in October. The issue affects all S3 compatible storages which requires v2 signature for authentication (e.g. EMC ECS). It caused that all S3 operation failed due to authentication failure, i.e. files could not be uploaded/downloaded/deleted, and the related data management policy actions failed triggering policy processing alerts. The error does not cause data loss as the Recording Servers are able to cache the files up to the capacity of the local disk. | 9.7.7.7871 | 2022-12-19 |
| RI-032885 | Platform - Storage Management |
Verba Secure File Transfer (VSFT) server port did not take into account the TLS cipher restrictions configured under Server Certificate/Advanced TLS Settings/Suite Constraints | 9.7.7.7871 | 2022-12-19 |
| RI-032992 | Platform - Storage Management |
Move policy did not apply retention settings if it was not the first data management policy to be executed for a call and policy execution on call basis (default mode) was set | 9.7.7.7871 | 2022-12-19 |
| RI-033154 | Platform - Storage Management |
Amazon S3 and S3 Compatible storage targets do not support subfolders, only the root folder of the bucket is supported. However, the storage target configuration page allowed to enter a subfolder in the REST API endpoint configuration field, while the Storage Management service discarded that /subfolder and used the root folder for the action. In an extreme configuration, this could even cause data loss. For more details, see RI-033280.
The Storage Management service now fails and raises the appropriate alert if an invalid bucket/container name or API endpoint is configured. | 9.7.7.7871 | 2022-12-19 |
| RI-033166 | Platform - Storage Management |
SMTP advanced IM export (Microsoft Teams) participant query returned duplicated entries | 9.7.7.7871 | 2022-12-19 |
| RI-033218 | Platform - Storage Management |
No limit (0) SMPT attachment (Storage Management/Storge Targets/SMTP/Attachment Size Limit (Mbyte)) did not work, the system applied a 5 MByte file limit instead. | 9.7.7.7871 | 2022-12-19 |
| RI-033219 | Platform - Storage Management |
"Call based" data retention policy processing might have stopped prematurely if failed records count was less than half of the batch but more than 1/10th of the batch. E.g. a move policy stopped if 481 records could not be moved for some reason (the policy processed 1000 records in a batch). | 9.7.7.7871 | 2022-12-19 |
| RI-033220 | Platform - Storage Management |
Small resource/memory leak resolved in Amazon S3, S3 Compatible, EMC Centera, and SFTP storage targets. There was no impact on the behavior of the Storage Management service. | 9.7.7.7871 | 2022-12-19 |
| RI-033280 | Platform - Storage Management |
If multiple storage targets were configured in the system pointing to the same storage location/folder, and a Move policy was configured to move data from one of the storage targets to the other, the system permanently deleted the data causing data loss in the system. For instance, 2 Amazon S3 storage targets are configured as follows:
- Target1, Bucket1
- Target2, Bucket1 (the same bucket as Target1)
- Data uploaded to Target1 from Recording Servers
- Move policy configured to move data to Target2
- This configuration will result in deleting all data
A new check validates if the source and the destination storage targets are pointing to the same storage location/folder. Previously, the system only validated if the source and the destination are on the same storage targets configured in the system. | 9.7.7.7871 | 2022-12-19 |
| RI-033284 | Platform - Storage Management |
Verint WFO export target: media files were duplicated in ingest requests if the record type was standard causing Verint WFO to mix the files and generate strange artifacts in media | 9.7.7.7871 | 2022-12-19 |
| RI-033292 | Platform - Storage Management |
Policy based encryption of calls already uploaded or transcoding of encrypted calls might have collided with playback or advanced export, in very rare cases, when the policy was executed on the same record which was being played back at the same time. This might have led to losing encryption information making the encrypted or transcoded file corrupt, and causing data loss. | 9.7.7.7871 | 2022-12-19 |
| RI-033295 | Platform - Storage Management |
Background task page counter fixes:
- If data management policy processing failed, the background tasks/total processed counter became invalid as it summed the number of total calls and failed calls.
- For scheduled policies, the background task counter when the policy finished became invalid, it contained all other policy results which were processed starting from this policy (call based policy processing, default).
- Policy execution in background tasks was not closed if it wasn't the policy from where the processing of call started (call based processing, default) | 9.7.7.7871 | 2022-12-19 |
| RI-033326 | Platform - Storage Management |
When the database update for a move policy failed (the destination storage target could not be updated in the database), but the file move was successful, when the policy retried the action next time, the move action failed, since the file was no longer on the source location. These records could not be played back, downloaded, or exported. | 9.7.7.7871 | 2022-12-19 |
| RI-033480 | Platform - Storage Management |
Playback did not work for migrated calls from a Verint WFO v11/v15 system if the files were stored on EMC Centera, and there were multiple archive copies for the same call | 9.7.7.7871 | 2022-12-19 |
| RI-033567 | Platform - Storage Management |
A false alert was raised during transcoding when the media file was encrypted and the file was already in the right format | 9.7.7.7871 | 2022-12-19 |
| RI-031889 | Installer - Servers |
The installer should not accept commas when providing a port for the SQL server connection | 9.7.3.7434 | 2022-06-10 |
| RI-032263 | Installer - Servers |
The Lync Filter service user password encryption was missing in the PowerShell Deployment Toolkit | 9.7.5.7598 | 2022-08-30 |
| RI-032762 | Installer - Servers |
Replaced the comma with colon in the registry when using custom SQL port. PowerShell Deployment Toolkit raised an error when using a custom SQL port during the test phase. | 9.7.6.7735 | 2022-10-21 |
| RI-032806 | Installer - Servers |
PowerShell Deployment Toolkit failed when using Windows Authentication for SQL with encrypted passwords | 9.7.7.7871 | 2022-12-19 |
| RI-033301 | Installer - Servers |
The installer always asked if the user wanted to partition the database, even if it was already partitioned and partition update scripts should have been run. The installer will automatically run these updates if the database is partitioned. | 9.7.7.7871 | 2022-12-19 |
| RI-031973 | Platform - CDR and Archived Content Import |
Skype for Business CDR reconciliation for application share calls could not take into account the QoE database and related stream statistics leading to false positive recording failure alerts of not established/failed app share sessions | 9.7.4.7502 | 2022-07-19 |
| RI-032024 | Platform - CDR and Archived Content Import |
Skype for Business CDR reconciliation reported already processed non-recorded conversations in some cases | 9.7.4.7502 | 2022-07-19 |
| RI-032360 | Platform - CDR and Archived Content Import |
The system did not set the retention period for the imported CDRs created during the CDR reconciliation process. The system now creates metadata XML files and sets the retention accordingly (when configured). | 9.7.5.7598 | 2022-08-30 |
| RI-031546 | Platform - Import |
Generic Import - IM Content fields were duplicated in case of doing export or doing field mapping testing. | 9.7.1.7383 | 2022-05-19 |
| RI-031553 | Platform - Import |
Generic Import Source: testing with chat data did not work | 9.7.1.7383 | 2022-05-19 |
| RI-031670 | Platform - 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. | 9.7.1.7383 | 2022-05-19 |
| RI-031899 | Platform - Import |
In peer-to-peer Cisco Webex Teams chat when an external participant was present (from another Cisco Webex Team) the Form/To fields could contain special characters that were stored incorrectly. This caused character encoding issues, and the UI showed malformed information. | 9.7.3.7434 | 2022-06-10 |
| RI-031932 | Platform - Import |
Generic Import - Field mapping with a function couldn't be saved. Field with child fields with settings saving issue is resolved (saving only for the child field and save instant changes). | 9.7.3.7434 | 2022-06-10 |
| RI-032278 | Platform - Import |
Custom scheduled import policy configuration was enabled for Cisco Webex Teams (Cisco Spark) chat import sources while this integration does not support scheduled policies | 9.7.5.7598 | 2022-08-30 |
| RI-032329 | Platform - Import |
When no recoding rules were enabled for an import source and the import source was not created in the reference tenant (multi tenant system), the imported records were created in the reference tenant instead of the tenant where the import policy was running. | 9.7.5.7598 | 2022-08-30 |
| RI-032371 | Platform - Import |
Import service crashed when importing Skype for Business archived content | 9.7.5.7598 | 2022-08-30 |
| RI-032511 | Platform - Import |
Vodafone mobile recording import source fixes implementing comprehensive Vodafone API support with a focus on edge cases, reliability and unexpected conditions, and the creation of detailed Vodafone metadata template for faster troubleshooting. | 9.7.5.7598 | 2022-08-30 |
| RI-032545 | Platform - Import |
Generic import source could not find media files with case sensitive file names | 9.7.6.7735 | 2022-10-21 |
| RI-032552 | Platform - Import |
Segmented IM integrations such as Webex Teams or TeleMessage no longer create CDR XMLs in the media folder | 9.7.6.7735 | 2022-10-21 |
| RI-032584 | Platform - Import |
Import sources determined the validity of the extensions in a wrong way using the validity of the last entry in the configuration for all extensions in v9.7.5. This might have caused missing records during the import process. | 9.7.6.7735 | 2022-10-21 |
| RI-032757 | Platform - Import |
When using External Server configuration, if the alerts raised by the external servers were imported by multiple servers (Import Service were enabled on the multiple servers for high availability), after the first server succeeded, the other serves raised errors | 9.7.6.7735 | 2022-10-21 |
| RI-033285 | Platform - Import |
Generic import could have used the wrong media file name if a filename was contained by another filename, then a false match occurred. For example for a metadata file called sample.xml the related file can be sample.wav, but not asample.wav. | 9.7.7.7871 | 2022-12-19 |