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-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-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-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-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-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-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-031557 | Recording - Zoom |
Workaround for missing participant leave date (unexpected) for Zoom Meeting imports | 9.7.1.7383 | 2022-05-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-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-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-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-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-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-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 |