Verba Release Notes

Azure Key Vault is now available to use for file encryption.

OpenSSL library is updated to the latest release, version 3.2.1.

Upgraded the OpenSSL version of the Web Application to 3.0.13.

Updated the Moment.js library to version 2.30.1 and the jQuery library to version 3.7.1.

Configuring the secure Cisco JTAPI connection for Cisco UCM 14 SU2 is now supported.

The Microsoft Teams Bot Service now updates the recording decision after every direction change and it starts or stops the recording accordingly.

The Microsoft Teams Thread ID is now stored in the Meeting ID metadata field.

Controlled recording can now be configured to prohibit stopping the recording if an external party joins the call or meeting.

Export API License issue alert has been extended with listing non-existent users in the tenant.

Introduced performance optimizations to reduce Graph API usage and improve processing speed.

The IPC N+1 failover intervals and the number of probes are now configurable, and the checks are now done for each server level instead of each zone.

The import of breakout rooms in Zoom Meetings is now supported. Breakout rooms show as individual meetings separate from the host meeting they were created in, but the Topic field of the breakout room record contains a reference to the host meeting.

The buttons to move column items up, down, and between lists on the Conversation List Layout Configuration page are now disabled if the operation cannot be executed.

Apache Tomcat version is upgraded to 9.0.84.

For certain languages, the player transcript no longer incorrectly includes spaces between characters.

Updated the root Web Application cookie context installer.

Microsoft renamed Azure Active Directory to Microsoft Entra ID. In line with these changes, references to Azure Active Directory, Azure AD, AAD, and related concepts have been updated on the user interface and in the documentation.

Added a new Referrer-Policy HTTP response header with the same-origin option.

The Technical ID value could not be added to the custom CSV metadata file in Advanced Export.

Conversations can now be deleted. Under Workflows, users can now request the deletion of conversations with a specific label applied. These requests can be approved by selected users. Once conversations are deleted in the web application, they are first moved to the Trash, and after a preconfigured time, the conversations are permanently deleted from the database and archives. Users with the Access Trash permission can also view and restore conversations that have been moved to the Trash before permanent deletion.

On the Collect Configuration and Logs page, a new collection can now be started from any server, not just the server on which the last collected configurations are stored.

The new Users Under Legal Hold report lists the users with conversations under Legal Hold. For each user, the report shows the first and last conversations under Legal Hold, and the labels and cases associated with the user.

Increased the default SQL DB query timeout from 15 to 300 seconds.

The SQL Agent Maintenance Job creator script can now be executed on the secondary database servers without errors.

The Last Version flag is no longer updated in Microsoft Teams IM message records to reduce SQL server resource use.

Improved the speed of the upgrade process to release 9.9 in deployments with large trader voice databases.

Voice Quality Check can now detect voice breakups more accurately.

The Advanced IM Export policy now accepts up to 90 days of delay between the time the message is sent and the time the message is captured.

The initialization of creating Azure Blob or Azure FileShare storage targets is improved to decrease the Azure API usage.

When the Keep the Worse Copy Too option is selected, the deduplication policy can now be prevented from swapping the Primary and Secondary designations if the secondary copy is better quality.

Zoom Meeting CDR reconciliation now uses exact timestamps (hours, minutes, and seconds) instead of full days to query the API for CDR data. This enhancement significantly reduces API usage and speeds up the reconciliation process for large deployments.

The migration process no longer sets the update timestamp of conversations migrated from WFO. This means that data management policies that have already processed records past the conversation start time of the migrated items no longer process these migrated records.

The passive recorder service could crash for Skype for Business or SIP SPAN recording when processing transferred calls in the database.

The database connection handler was initialized with the wrong value for connection timeout, causing it to intermittently fail to execute queries.

The Skype for Business IM recorder service created transcript XML files for empty chat sessions, which caused export failures.

The Microsoft Teams-specific filter criteria in Recording Rules were misleading.

The recorder connection manager was not properly discarded at call termination, which could lead to a memory leak.

The Microsoft Teams Bot Service could not process the call termination event if the termination signal did not contain the display name of the call participant that the termination originated from.

The Microsoft Teams Bot Service did not properly exit when the service was stopped, causing a service restart and issues on the next start-up.

The Microsoft Teams Bot service did not restart recording if a user put the call on hold and switched devices before resuming the call.

In rare cases, unhandled race conditions could lead to database up/down SQL errors and snapshot violation transaction exceptions.

If a bot initiated a chat, the From and To fields and the participant list was empty until a human participant interacted with the chat.

Attachment download failures did not update the attachment items in the database with the failure status. Affected versions 9.9.0 and later.

Fixed issue with IPC Unigy recording, where existing trader login sessions were sometimes considered not to be recorded at the agent list polling stage, causing a recording to be triggered. The issue only affected multitenant deployments if a zone was shared between multiple tenants. Affected VFC versions: 9.8.5-9.8.7.

In rare cases, the VOX history for "Do not record open lines without VOX" was not properly closed if the recorder crashed, leading to keeping more CTI segments than necessary.

Unknown callers in Metaswitch Perimeta interconnect calls were not handled correctly, causing the CDR fields for both the calling party and the called party to be "unknown".

The participant lists for BT IPTrade conference calls contained TPO slots, causing incorrect participation times.

After a TPO failover, the CTI records created for ongoing calls did not show the Turret IDs in the From Device and To Device CDR fields.

Speakerbus conference call recording could time out prematurely if no CTI events happened until the call timeout limit was reached.

If a zone was shared between multiple tenants in a multi-tenant VFC configuration, the recording could stop at the agent list polling stage.

The start and end time values for conference participants were incorrectly set to be the current time in the database.

Percent encoding in the sender and the recipient was not handled, causing a service crash at application termination.

Zoom Phone: Added support for sharedOffice type calls.

If multiple columns were selected in the Added Columns list of the Conversation List Layout Configuration page, the move up/down action only applied to one of the selected columns.

In rare cases, the Web Application tried to access the database with the domain account that was configured for a storage target.

In some cases, the Microsoft Entra ID (formerly known as Azure Active Directory) synchronization was stuck running after a failure, and no further changes on the Entra ID source were synchronized to VFC.

When a user opened the root web application URL without specifying the full path with /verba at the end, duplicate JSESSIONID cookies were created.

If the SQL connection was intentionally closed by a maintenance process in the web application, an unnecessary warning log entry was written to the logs.

XLS exports opened in older versions of Microsoft Office could enable formula injection vulnerabilities.

Searching conversations by Group name did not return results in multi-tenant environments.

Mobile UI playback events were not included in the Audit Log.

The report header was missing from the PDF outputs of the Recorded Users and Extensions, Server Capacity, Service Provider Extension License, and Storage Target Capacity reports.

The Peak Concurrent values were not showing in the Server Capacity report.

The Transcription Summary dashboard widget did not ignore calls for which transcription results were not possible or intended.

The Speech Transcription service crashed when it attempted to write Intelligent Voice topics to the database.

Intelligent Voice transcription topics were showing incorrectly if multiple Intelligent Voice groups were configured.

The Intelligent Voice transcription did not work when an existing, not Intelligent Voice-type data processor was changed to Intelligent Voice.

Fixed intermittent failures in the Provisioning Web Service that prevented the creation of environments in multitenant deployments.

The Delete policy failed when processing records that were migrated from WFO and their retention period passed.

System monitoring skipped alerts with excessively large bodies, causing these alerts to not be saved in the database.

Deduplication was not successful for IPC open lines.

When voice recordings were exported to Bloomberg Vault, the Trader Name and Direction fields were not filled out properly.

The export process failed if the target directory could not be created during a file copy operation.

The export of Microsoft Teams chat messages fails if the data is compressed and is larger than 16 kilobytes.

Transcript files could not be uploaded if the call was encrypted with a Key Management Service (Azure Key Vault) key.

Advanced IM export background task was not closed if the Storage Management service crashed or was forcefully terminated.

Fixed a file encryption issue in the storage service that caused the signing method to be set to an unknown value in releases 9.9.2 and older.

The Move data retention policy failed when processing IM attachment files.

The Encrypt And Sign data management policy did not update the database with the new encryption ID for IM attachment files when Windows Certificate Store was used for key management.

Some installer SQL scripts threw errors for Azure SQL databases.

Regression in the recording recheck functionality resulted in reconciled and failed Cisco and Skype for Business calls not being rechecked.

The Zoom CDR import service now reattempts downloading 0 byte successful downloads three times.

Short CDR-only records were sometimes not closed on call termination if both the start and end of the call happened while the system was busy with call segmentation.

If IM insertion related SQL error happened, the reinsertion of the conversation was not retried but considered successfully imported

Genesys Cloud import source logs now show time values in the UTC time zone.

The appending of Telemessage and Cisco Webex Teams(Spark) chats to the previous session within a time interval did not work due to recent database optimizations. Messages appended to CDR sessions that were created earlier were in the database with the wrong start time, and the player could not show them.

Fixed problems with Chinese characters and chat message ordering in the Telemessage import source.

The SMS import service did not drop the connection to the Short Message Service Centre (SMS-C) if the parsing failed when processing non-standard or malformed protocol data units (PDUs). With this fix, the service now skips processing the faulty message, proceeds to the next message, and raises an alert.

The Verint import source created duplicate CDR records with invalid metadata when importing OpenTrade calls with a muted section in the conversation.

The Avaya Contact Recorder (ACR) import source did not import any calls if the Data Management Policy Recording Rules setting was not selected.