RI-010012 | Security |
Installer logs contained passwords in clear text in certain cases | 8.9.4983.0 | 2016-10-19 |
RI-010839 | Recording - Proxy |
PSTN inbound calls to a Cisco huntgroup was not recorded using the Cisco Proxy based recording solution | 8.9.5032.0 | 2017-06-06 |
RI-012587 | Recording - Proxy |
False alerts might be generated for Proxy - Recorder connections due to improper Keep Alive message handling in the proxy service in case of ungraceful termination of TCP connections | 8.9.5067.0 | 2017-11-20 |
RI-009679 | Recording - Cisco |
When JTAPI information is not available, then the system uses the recorded extension's last known Partition information | 8.9.4989.0 | 2016-12-21 |
RI-009815 | Recording - Cisco |
Issue in Cisco XCC/WSAPI based gateway recording generated false connection alerts | 8.9.4983.0 | 2016-11-29 |
RI-009888 | Recording - Cisco |
False "Cannot update call on media recorder" alerts were sent for very short calls (< 1 sec) | 8.9.4983.0 | 2016-11-16 |
RI-010122 | Recording - Cisco |
The recorder service might crash using Cisco gateway based recording (WSAPI/XCC) when the recorded call was initiated from an analogue port | 8.9.4983.0 | 2016-09-23 |
RI-010481 | Recording - Cisco |
Cisco JTAPI Service did not write modality information into the database | 8.9.4994.0 | 2017-01-06 |
RI-010827 | Recording - Cisco |
Mute XML Phone Service did not work with MAC Address parameter | 8.9.5035.0 | 2017-06-16 |
RI-010857 | Recording - Cisco |
The system did not capture the video streams for Cisco DX series video endpoints when forward error correction was used | 8.9.5031.0 | 2017-06-28 |
RI-012569 | Recording - Cisco |
Cisco JTAPI Controlled Recording "Start" record did not show the correct MAC Address after a transfer | 8.9.5073.0 | 2017-11-30 |
RI-012591 | Recording - Cisco |
Using Cisco JTAPI controlled recording, the conversation was not displayed on the user interface after call transfer | 8.9.5067.0 | 2017-11-20 |
RI-012622 | Recording - Cisco |
An application deadlock could occur in The Cisco JTAPI Service and SQL INSERTS could stop. A restart of the service was required to continue. | 8.9.5059.0 | 2017-10-02 |
RI-012630 | Recording - Cisco |
JTAPI information was missing after the recorded phone has been transferred | 8.9.5058.0 | 2017-09-26 |
RI-012924 | Recording - Cisco |
Large backward jumps in RTP stream sequence numbering was not handled properly | 8.9.5044.0 | 2017-12-20 |
RI-009820 | Recording - Cisco IM |
Maintenance mode did not work and the Cisco IM&P connections could not be restored | 8.9.4983.0 | 2016-11-28 |
RI-010173 | Recording - Cisco IM |
Group chat legs were not assigned to the recorded user in the database | 8.9.4983.0 | 2016-09-01 |
RI-010829 | Recording - Cisco IM |
The Verba Cisco Compliance Service did not take the extension configuration into account when there was no extension configured with IM modality, and started to capture all IM conversations | 8.9.5035.0 | 2017-06-15 |
RI-012649 | Recording - Cisco IM |
Mobile Cisco Jabber app could not parse HTML based notification only plain text | 8.9.5053.0 | 2017-08-30 |
RI-009792 | Recording - Lync/SfB |
SfB/Lync mobile calls were not recorded when the mobile phone was connected to the Internet on 4G networks and the provider was using NAT | 8.9.4983.0 | 2016-12-01 |
RI-009843 | Recording - Lync/SfB |
The direction of SfB/Lync RGS conversations were not stored properly in case of multiple Verba proxy servers | 8.9.4983.0 | 2016-11-24 |
RI-009896 | Recording - Lync/SfB |
SfB/Lync app and screen share streams were not established when announcement was configured for the recorded user with announcement configured | 8.9.4983.0 | 2016-11-16 |
RI-010236 | Recording - Lync/SfB |
One way audio recording with O365 hosted conference calls when recorded SfB 2016 clients (on-prem) join | 8.9.4983.0 | 2016-12-31 |
RI-010593 | Recording - Lync/SfB |
SfB/Lync file transfer and content import recordings were not decrypted before downloading | 8.9.5013.0 | 2017-02-17 |
RI-010623 | Recording - Lync/SfB |
Multiple announcements were triggered when there was no online proxy server available for SfB/Lync recording | 8.9.5009.0 | 2017-01-27 |
RI-010684 | Recording - Lync/SfB |
Incorrect direction was set (based on pattern) in case of incoming calls from PBXs connected to the SfB/Lync environment | 8.9.4997.0 | 2017-02-21 |
RI-010711 | Recording - Lync/SfB |
The system did not recognize re-invites when the SfB/Lync system was connected to other PBXs (e.g. Avaya) via SIP trunk and retargeted the re-invites for announcement | 8.9.5009.0 | 2017-01-27 |
RI-010742 | Recording - Lync/SfB |
After a network issue, the Verba Front-End Filter Service was not able to properly identify the connection status and tried to send SIP messages to the Verba Proxy Service while the connection was not active. This resulted in increased SIP queue size and slower call setup. Keep-Alive mechanism and connection failover are improved in the Verba Front-End Call Filter Service. | 8.9.5031.0 | 2017-05-22 |
RI-010743 | Recording - Lync/SfB |
Meta information was updated with wrong information for SfB/Lync calls in case of certain character patterns in the conversation subject.
New configurations added to the Verba Passive Recorder Service and the Verba Media Collector & Proxy Service to explicitly enable or disable SfB/Lync contact center integrations. | 8.9.5031.0 | 2017-05-22 |
RI-012602 | Recording - Lync/SfB |
The Verba SfB/Lync IM Recorder Service inadvertently closed the ongoing voice/video conversation part of the conference call in the database (media files were not affected) when there was a SfB/Lync IM Recorder failover during the conference. | 8.9.5064.0 | 2017-11-03 |
RI-012671 | Recording - Lync/SfB |
Streams using TCP over the Lync/SfB Edge server might not be processed properly in rare cases which led to packet loss in recording which is critical for RDP and file transfer recording and affected the quality of the voice recordings | 8.9.5045.0 | 2017-08-02 |
RI-010765 | Recording - Lync/SfB IM |
Invalid CDR XMLs were created for SfB/Lync recordings which caused storage upload policy failure | 8.9.5026.0 | 2017-03-27 |
RI-010824 | Recording - Lync/SfB IM |
The Verba SfB/Lync IM Filter Service was not able to connect to the Verba SfB/Lync IM Recorder Service due to TLS 1.2 enforcement issue | 8.9.5036.0 | 2017-06-23 |
RI-012613 | Recording - Lync/SfB IM |
Instant messages sent by a Web Client with Sfb Web Component (noticed at 6.0.9319.272) did not get recorded/captured | 8.9.5061.0 | 2017-10-26 |
RI-009676 | Recording - Avaya |
When a call was ringing out and put on hold then resumed, the CDR information was missing the other party number | 8.9.4989.0 | 2016-12-21 |
RI-010596 | Recording - Avaya |
Avaya ServerConnectionDown events were triggering complete re-initialization, even if it was not necessary | 8.9.5012.0 | 2017-02-14 |
RI-010192 | Recording - Unified Call Recorder |
SIPREC: video call recording was not working properly | 8.9.4983.0 | 2016-08-26 |
RI-010607 | Recording - Unified Call Recorder |
Shared recorder/remote Verba related SQL files are now written to the right folder | 8.9.5010.0 | 2017-02-06 |
RI-009688 | Recording - Speakerbus |
Speakerbus 5th channel address was not parsed properly in heartbeat messages, recording was lost for the 5th channel in case of recovery mode | 8.9.4987.0 | 2016-12-19 |
RI-009850 | Recording - Desktop |
Primary screen might not be identified properly, and instead of the secondary or both were included in agent view/real-time monitoring | 8.9.4983.0 | 2016-11-22 |
RI-010455 | Recording - Desktop |
Capture agent now tries to reconnect in case of recorder connection failure before considering failed connection (and so stopping screen recording) | 8.9.4995.0 | 2017-01-11 |
RI-010470 | Recording - Desktop |
When the connection between the screen capturing agent and the recorder was lost, and screen capturing stopped, the separate conversation entry in the database had invalid end time value | 8.9.4994.0 | 2017-01-09 |
RI-010513 | Recording - Desktop |
When the connection between the screen capturing agent and the recorder was lost, the multiplexer generated invalid filename for the multiplexed file | 8.9.4997.0 | 2017-01-16 |
RI-010514 | Recording - Desktop |
Screen recording was triggered not just by voice/video but file and application/screen share recording sessions as well | 8.9.4997.0 | 2017-01-16 |
RI-012790 | Recording - Desktop |
If screen capturing was paused by the user and before the call-end it was not resumed then the state was held for the next call as well and recording was started in paused state | 8.9.5074.0 | 2017-12-12 |
RI-010821 | Recording - SIPRec |
ACME SIPREC: no media received if SBC initiated the sessions with inactive streams then changed them active | 8.9.5038.0 | 2017-06-27 |
RI-009685 | UI - Web Interface |
Agent View Scope permissions were in the wrong precedence order ('On the phone' screen only, 'On the phone' and idle screens) | 8.9.4987.0 | 2016-12-19 |
RI-009729 | UI - Web Interface |
"Number of wrong logins" were not reset after a successful login | 8.9.4986.0 | 2016-12-10 |
RI-009731 | UI - Web Interface |
Publishing Server users were unable to log in to the Publishing Server | 8.9.4986.0 | 2016-12-10 |
RI-009736 | UI - Web Interface |
Filtering for Custom User Attributes did not work on Users List screen | 8.9.4985.0 | 2016-12-09 |
RI-009752 | UI - Web Interface |
Name and Auto-Approve filters did not work on Workflows List | 8.9.4984.0 | 2016-12-07 |
RI-009757 | UI - Web Interface |
New Case with Legal Hold enabled could not be created | 8.9.4984.0 | 2016-12-07 |
RI-009765 | UI - Web Interface |
Download did not work on View Shared Items screen | 8.9.4983.0 | 2016-12-06 |
RI-009847 | UI - Web Interface |
Shared Items screen filters did not work | 8.9.4983.0 | 2016-11-23 |
RI-009854 | UI - Web Interface |
Agent View: Improved handling of desktop agent registration. When the desktop agent is registering again then the web application is not clearing the current image store for the agent. | 8.9.4983.0 | 2016-11-22 |
RI-009940 | UI - Web Interface |
Password change did not work when "Passwords History Count" was set to a value greater than zero | 8.9.4983.0 | 2016-11-02 |
RI-009971 | UI - Web Interface |
In a Multi-Tenant Environment, Database Purging worked on the root tenant only | 8.9.4983.0 | 2016-10-25 |
RI-010030 | UI - Web Interface |
Storage Target and Verba Server usage charts did not work with IE | 8.9.4983.0 | 2016-10-14 |
RI-010129 | UI - Web Interface |
When the user tried to create a Role with a name that was already used by another Role, an error page was shown | 8.9.4983.0 | 2016-09-21 |
RI-010451 | UI - Web Interface |
Viewer/Player disappeared after manually transcoding a recording sfB/Lync screen/application share recording (RDP) to MP4 | 8.9.4996.0 | 2017-01-12 |
RI-010462 | UI - Web Interface |
Active Directory synchronization error was not available on the web interface when some users were successfully synchronized | 8.9.4995.0 | 2017-01-11 |
RI-010471 | UI - Web Interface |
On the Communication Policy details screen, if one clicked very fast on the checkbox to select a modality (turn on blocking) and then unselect it, then the selection disappeared | 8.9.4994.0 | 2017-01-09 |
RI-010472 | UI - Web Interface |
The QM icon appeared on the search interface (to add a conversation to a project) even if the customer did not have QM licenses | 8.9.4994.0 | 2017-01-08 |
RI-010474 | UI - Web Interface |
In case of error in Verba Viewer/Player, the whole page had to be refreshed | 8.9.4994.0 | 2017-01-08 |
RI-010531 | UI - Web Interface |
List filter disappeared on refresh on the Ongoing Conversations page | 8.9.4997.0 | 2017-01-12 |
RI-010559 | UI - Web Interface |
Agent View idle screens were displayed when Group or Grid size setting were changed | 8.9.5017.0 | 2017-03-02 |
RI-010561 | UI - Web Interface |
Changing the playback speed did not work after pause in Internet Explorer | 8.9.5017.0 | 2017-03-02 |
RI-010605 | UI - Web Interface |
The application generated duplicate Playback events due to a Chrome browser bug | 8.9.5010.0 | 2017-02-07 |
RI-010624 | UI - Web Interface |
An error occurred when a non-supervisor user tried to filter for Conversation Identifier | 8.9.5009.0 | 2017-01-27 |
RI-010627 | UI - Web Interface |
Silent Monitoring did not work without play permission | 8.9.5007.0 | 2017-01-26 |
RI-010730 | UI - Web Interface |
Apply extension configuration was not triggered automatically after a new Verba Announcement Server registration | 8.9.5022.0 | 2017-03-16 |
RI-010755 | UI - Web Interface |
Group Membership administration sometimes did not work because a SQL Server bug (DATETIME values cannot be filtered with an exact time) | 8.9.5029.0 | 2017-04-07 |
RI-010760 | UI - Web Interface |
Users without download permission (but with play) were able to download conversations with the multiple selection feature. | 8.9.5028.0 | 2017-04-03 |
RI-010769 | UI - Web Interface |
Location change history always showed 0 items when was opened from the location details screen "View Change History" | 8.9.5025.0 | 2017-03-24 |
RI-010806 | UI - Web Interface |
Two Active Directory synchronization profiles could start simultaneously in case of SQL connection issues and could invalidate users | 8.9.5042.0 | 2017-07-10 |
RI-010828 | UI - Web Interface |
If the user had Preview Conversation right but did not have Download right, then the user cannot playback at all | 8.9.5035.0 | 2017-06-16 |
RI-010830 | UI - Web Interface |
When a user data contained a newline character, the CSV user export created an invalid CSV file | 8.9.5035.0 | 2017-06-12 |
RI-010843 | UI - Web Interface |
Query description for Search audit log entries for boolean values generated an invalid XHTML | 8.9.5032.0 | 2017-05-26 |
RI-012572 | UI - Web Interface |
Checkboxes were disabled on the Conversation Export page when the target was SFTP | 8.9.5072.0 | 2017-11-30 |
RI-012603 | UI - Web Interface |
New Bulk User Update could not be saved when some update fields were configured | 8.9.5064.0 | 2017-11-03 |
RI-012604 | UI - Web Interface |
On-Demand Call Buffer paging did not work properly, the page is now integrated into the main Search screen | 8.9.5064.0 | 2017-11-03 |
RI-012634 | UI - Web Interface |
In Multi-Tenant mode, the Server List always showed servers in the reference environment (0000) | 8.9.5057.0 | 2017-09-17 |
RI-012641 | UI - Web Interface |
Storage Target administration did not work properly (throw JavaScript error) | 8.9.5055.0 | 2017-09-11 |
RI-012648 | UI - Web Interface |
Multi-Tenant Public IP min/max validation did not work on the Extension detail screen | 8.9.5053.0 | 2017-09-04 |
RI-009680 | UI - Reporting |
CDR Reconciliation Summary and Users CDR Reconciliation Summary reports were showing incorrect data when there were extensions not assigned to users | 8.9.4989.0 | 2016-12-21 |
RI-009703 | UI - Reporting |
Users CDR Reconciliation Summary report was showing months in wrong order | 8.9.4987.0 | 2016-12-16 |
RI-009800 | UI - Reporting |
Reports were showing incorrect direction values for the new directions | 8.9.4983.0 | 2016-11-30 |
RI-009839 | UI - Reporting |
Reporting did not work when "Past" or "Previous" text inputs did not contain a valid number | 8.9.4983.0 | 2016-11-24 |
RI-009931 | UI - Reporting |
False email sending failures were displayed on the reporting page when there were previous errors | 8.9.4983.0 | 2016-11-03 |
RI-009978 | UI - Reporting |
Not Recorded and Incorrect Conversation Details report did not show calls with End Cause is Unobtainable | 8.9.4983.0 | 2016-10-25 |
RI-010121 | UI - Reporting |
Scorecard Calibration Details report did not work when text fields were added to scorecards | 8.9.4983.0 | 2016-09-23 |
RI-010478 | UI - Reporting |
Simultaneous Calls Trend report did not work | 8.9.4994.0 | 2017-01-07 |
RI-010507 | UI - Reporting |
Ethical wall report issues resolved:
- No data displayed in the Content Policy Summary report
- Content Policy Details report did not show which communication and content policies were fired
- Session Blocking Summary report showed incorrect information on the chart
- Users Content Policy Summary report did not show all of the users and showed incorrect data
- Users Session Blocking Summary report showed incorrect information on the chart | 8.9.4997.0 | 2017-01-16 |
RI-010552 | UI - Reporting |
An error in the direction handling script caused infinite loop then an exception | 8.9.5018.0 | 2017-03-07 |
RI-010578 | UI - Reporting |
Investigator group permission was missing in the Users Roles Permissions and Groups Report | 8.9.5015.0 | 2017-03-01 |
RI-010579 | UI - Reporting |
Certain fields were split and truncated over a certain size depending on the available length of the fields | 8.9.5015.0 | 2017-02-28 |
RI-010632 | UI - Reporting |
Agents Evaluation Details report did not show text and numeric questions | 8.9.5007.0 | 2017-01-26 |
RI-010650 | UI - Reporting |
Agents Call Activity Summary report failed when the call end time field was set to 1900-01-01 due to recording error | 8.9.5003.0 | 2017-01-19 |
RI-012680 | UI - Reporting |
Not Recorded and Incorrect Conversations Details report fixes:
- missing property files caused empty lines in the report
- SQL error when media length field was 0
- incorrect data was shown due to changes in the database fields | 8.9.5045.0 | 2017-07-31 |
RI-009949 | Solution - Ethical Wall |
The system was unable to subscribe to events in case of CUPS 9.x | 8.9.4983.0 | 2016-10-27 |
RI-010382 | Solution - Ethical Wall |
Content Filter for File was using OR logic between the filename regexp match condition and the allowed maximum file condition, now it uses AND operator. OR logic can be achieved by creating multiple content filters. | 8.9.4944.0 | 2016-09-12 |
RI-010750 | Solution - Ethical Wall |
Communication Policies were not applied automatically after Active Directory synchronization | 8.9.5031.0 | 2017-04-21 |
RI-012632 | Solution - Ethical Wall |
Communication Policies: the system did not check if at least one participant or "Everyone" was selected for "Participant A" and "Participant B" | 8.9.5058.0 | 2017-09-25 |
RI-012705 | Solution - Ethical Wall |
Participants containing special characters were not handled properly, causing errors in rule processing | 8.9.5044.0 | 2017-11-27 |
RI-012718 | Solution - Ethical Wall |
Only the first 3rd party notification was sent when multiple values were defined | 8.9.5044.0 | 2017-10-12 |
RI-009918 | Solution - Quality Management |
# of calls displayed the wrong number in the QM module | 8.9.4983.0 | 2016-11-08 |
RI-010548 | Solution - Quality Management |
QA scores counted text fields too if they contained numbers | 8.9.5019.0 | 2017-03-08 |
RI-010566 | Solution - Quality Management |
Quality Management / Show Evaluations page was displaying evaluations which were not assigned to the evaluator | 8.9.5016.0 | 2017-03-01 |
RI-010586 | Solution - Quality Management |
QM project update did not work after the project was started | 8.9.5014.0 | 2017-02-27 |
RI-012612 | Solution - Speech Analytics |
Delete Phonetic Index policy was not working | 8.9.5061.0 | 2017-10-27 |
RI-010587 | Platform - Announcement |
Incoming SfB/Lync announcement did not support the call direction pattern | 8.9.5014.0 | 2017-02-27 |
RI-010610 | Platform - Announcement |
Announcement service might invite participants to an IM conference which is not yet setup completely. It caused unwanted errors in SfB/Lync reports, there was no impact on user experience. | 8.9.5010.0 | 2017-02-02 |
RI-010841 | Platform - Announcement |
Using the Cisco inbound announcement, when a CURRI request arrived for a non-configured extension number, the system did not send a response to the CUCM | 8.9.5032.0 | 2017-06-06 |
RI-012600 | Platform - Announcement |
The SfB/Lync Announcement Service ignored the maintenance mode | 8.9.5064.0 | 2017-11-07 |
RI-012619 | Platform - Announcement |
Lync/SfB announcement service crashed randomly after playing announcements for inbound or outbound peer-to-peer calls | 8.9.5059.0 | 2017-10-05 |
RI-009924 | Platform - API |
NullPointerException was thrown when SearchCalls API call was used without a user | 8.9.4983.0 | 2016-11-04 |
RI-009925 | Platform - API |
HTTP Business API's HTML and JSON formats did not work properly when additional information had to be returned (metadata, instant messages, etc.) | 8.9.4983.0 | 2016-11-04 |
RI-009926 | Platform - API |
meta_relation parameter did not work in GWT Direct Call Search and HTTP Business API | 8.9.4983.0 | 2016-11-04 |
RI-009927 | Platform - API |
Error was thrown when multiple metadata filters were specified in GWT Direct Call Search and HTTP Business API | 8.9.4983.0 | 2016-11-04 |
RI-010209 | Platform - API |
Metadata field's relation combo box was not selected properly when the user used the Direct Search URL feature with meta field values. | 8.9.4983.0 | 2016-08-22 |
RI-010749 | Platform - API |
Newlines were not escaped properly in the HTTP Business API JSON response | 8.9.5031.0 | 2017-05-03 |
RI-012597 | Platform - API |
AddMarker API call "start" and "end" mode did not work | 8.9.5065.0 | 2017-11-08 |
RI-012620 | Platform - API |
Search Calls API did not work with metadata filters | 8.9.5059.0 | 2017-10-05 |
RI-012584 | Platform - Configuration |
Encrypted database connection could not be configured for the Web Application | 8.9.5067.0 | 2017-11-23 |
RI-012588 | Platform - Configuration |
Configuration settings longer than 1024 (in case of multiple values) / 8000 (in case of single values) could not be stored | 8.9.5067.0 | 2017-11-20 |
RI-010259 | Platform - Database |
SQL Server multi-subnet failover setting was not applied properly using the ODBC 13.1 driver | 8.9.4980.0 | 2016-11-30 |
RI-010249 | Platform - Media Processing |
Bad voice quality due to Silk decoding issue during silent monitoring and video call playback (recording was not affected) | 8.9.4983.0 | 2016-12-07 |
RI-010585 | Platform - Media Processing |
MP4 multiplexing did not work for video calls longer than 15 minutes | 8.9.5014.0 | 2017-02-27 |
RI-010860 | Platform - Media Processing |
VMF playback did not work for specific resolutions | 8.9.5031.0 | 2017-06-26 |
RI-012660 | Platform - Media Processing |
If a video call did not contain video or there was a big audio or video gap, MP4 transcoding stalled | 8.9.5048.0 | 2017-08-10 |
RI-010516 | Platform - Monitoring |
The system monitor service couldn't refresh the SfB/Lync Announcement Service counters | 8.9.4997.0 | 2017-01-16 |
RI-010522 | Platform - Monitoring |
The Verba SfB/Lync Call Filter, the Verba SfB/Lync IM Filter and the Verba SfB/Lync Communication Policy services were using incorrect alert types in case of connectivity issues | 8.9.4997.0 | 2017-01-13 |
RI-010818 | Platform - Monitoring |
Alerts longer than 4000 characters could not be inserted into the database | 8.9.5040.0 | 2017-06-28 |
RI-009710 | Platform - Storage Management |
Video files were kept and the modality of the recording showed video when transcoding video recordings to audio recordings | 8.9.4987.0 | 2016-12-14 |
RI-009717 | Platform - Storage Management |
Background task total counter was maximized at 1000 (batch size) showing inaccurate status information | 8.9.4986.0 | 2016-12-12 |
RI-009720 | Platform - Storage Management |
WORM storage target cache for playback was not properly updated on configuration changes and required service restart to take the new settings into account | 8.9.4986.0 | 2016-12-12 |
RI-009748 | Platform - Storage Management |
Recordings without media file were not handled properly and generated alerts and error log entries | 8.9.4984.0 | 2016-12-08 |
RI-009801 | Platform - Storage Management |
Issue with directory listing for network folders (SMB) might cause significant delay in file operations | 8.9.4983.0 | 2016-11-30 |
RI-009805 | Platform - Storage Management |
Storage Management service crashed when recordings without media files were in the WORM cache | 8.9.4983.0 | 2016-11-30 |
RI-009808 | Platform - Storage Management |
Transcoding process could not find the related voice call for application/screen share recording when the not recorded party initiated the voice session and the recorded party started the share session (or vice versa) | 8.9.4983.0 | 2016-11-29 |
RI-010251 | Platform - Storage Management |
When there are multiple CA certificates in the Windows Certificate Store, the certificates used by the system were only validated against the first matching CA certificate and this might cause that the certificate was considered invalid | 8.9.4983.0 | 2016-12-05 |
RI-010489 | Platform - Storage Management |
Transcoding of SfB/Lync screen/application share recordings (RDP) did not work when encryption was enabled | 8.9.4994.0 | 2017-01-06 |
RI-010576 | Platform - Storage Management |
Storage Management service might crash if RDP based application share transcoding session is terminated prematurely (because of error during processing or application exit) | 8.9.5015.0 | 2017-03-01 |
RI-010577 | Platform - Storage Management |
If preceding transcoding policy processing fails for an application share conversation, due to waiting for voice part, the current policy is still processed | 8.9.5015.0 | 2017-03-01 |
RI-010584 | Platform - Storage Management |
When a video transcoding job is canceled (service stop), the service closed the transcoding as a successful job | 8.9.5014.0 | 2017-02-27 |
RI-010606 | Platform - Storage Management |
The increase retention time storage policy did not update the retention time property in the Verba database accordingly (the field on the storage platform was updated properly) | 8.9.5010.0 | 2017-02-06 |
RI-010739 | Platform - Storage Management |
Upload policy did not work when the source and destination was EMC Centera, O365 Compliance Archive or SMTP. | 8.9.5031.0 | 2017-05-24 |
RI-010783 | Platform - Storage Management |
In some rare cases, encryption failed and the upload process was not able to upload the recordings | 8.9.5023.0 | 2017-04-21 |
RI-010799 | Platform - Storage Management |
The increase retention time policy did not update the retention period filed in the database in case of archived conversations | 8.9.5043.0 | 2017-07-12 |
RI-010804 | Platform - Storage Management |
During the execution of the storage policies, the service did not properly recognize the result of the operation which led to inconsistency in the database. Reported retention policies affected by the issue: Move, Upload. | 8.9.5042.0 | 2017-07-12 |
RI-010807 | Platform - Storage Management |
Playback and export did not work for conversations retrieved from EMC Centera | 8.9.5042.0 | 2017-07-05 |
RI-012571 | Platform - Storage Management |
Export to Hitachi Content Platform, EMC Centera, IBM TSM, Amazon S3, Azure Storage, EMC ECS did not follow the YYYY/MM/DD folder structure | 8.9.5072.0 | 2017-11-30 |
RI-012580 | Platform - Storage Management |
Export from EMC Centera did not export metadata XML files | 8.9.5068.0 | 2017-11-28 |
RI-012606 | Platform - Storage Management |
Hitachi Content Platform upload failed with "Upload from/to the same location is not allowed" error message | 8.9.5063.0 | 2017-11-03 |
RI-012615 | Platform - Storage Management |
IM export did not follow the YYYY/MM/DD folder structure | 8.9.5061.0 | 2017-10-26 |
RI-012625 | Platform - Storage Management |
Encrypt and Sign policy: if the files have not yet been uploaded and the policy run on these conversations then despite the missing files the processing was considered successful | 8.9.5058.0 | 2017-09-28 |
RI-012679 | Installer - Servers |
SQL script execution failed during installation due to timeout | 8.9.5045.0 | 2017-08-01 |
RI-010545 | Platform - CDR and Archived Content Import |
Certain fields were not properly truncated during the CDR reconciliation process, led to SQL error | 8.9.5019.0 | 2017-03-08 |