Verba Release Notes

Multiple security enhancements for the Web Application and other services: - Application level encryption (client side asymmetric certificate based encryption using RSA/ECB/PKCS1Padding) for sensitive information (e.g. passwords) above the encrypted transport layer - Allow only strong ciphers on the Verba API Server Socket

New metadata fields added to Cisco BroadWorks integration: ACD User, ACD Number, ACD Name, Announcement

The Skype for Business IM recorder now properly tracks the user participation in the case of group chats.

The Microsoft Teams Bot service now matches the Display Name and the Object ID against the internal domain regular expression.

Microsoft Teams bot grouping feature added for recording. Bot Grouping means one Compliance Recording (CR) bot instance can handle multiple users with recording policy assigned in a call or meeting at the same time. It is an optimization for large meeting cases to make sure fewer CR bots can handle more users. Bot grouping is applied when Recorded Users, who share the same Compliance Recording Policy, enter the same Teams meeting. In this scenario, the Bot Grouping feature eases infrastructure load by establishing only a single call for a defined number of users. For example, 50 recorded users can share the same Teams – Bot Service call, whereas previously 50 bot calls would have been established. Unlike in the first version in v9.6.15, when the first version of bot grouping was introduced, it is a complete implementation without any limitations.

New integration option for Microsoft Teams chat and channel archiving using the Microsoft Teams Export API: - Export API based integration, which allows querying and downloading chat messages for users, and channel messages for teams - Support for on-prem, cloud and hybrid deployments - Supports all instant message scenarios, channels, P2P, and meeting chats - Supports all formatting options, emojis, giphys, stickers, and other apps - Supports selective capturing/archiving for users and teams

Microsoft Teams chat archiving: Sharepoint attachments are now first tried with their download URL instead of file listing and filename matching

If non-trader voice call was too short and no media was received, the calls were displayed as non-recorded calls on the dashboard and reporting. These calls will have the end cause Cancelled going forward.

IPC Unigy zone level multitenancy implemented. The Verba tenant ID (environment ID) can be configured optionally for a zone to support multitenant configurations where the same trader ID is used across multiple tenants and zones.

Auto pause/resume recording support added for Microsoft Edge and Opera browsers

The Data Management Policy Events page has been deprecated and removed on the Conversation Detail page

Added the Participants field to the Export metadata, and Conversation List Layout

Active Directory Synchronization will not overwrite: - Users' Custom User attributes when they are not configured in the Active Directory Synchronization Profile - Users' Retention settings when they are not configured in the Active Directory Synchronization Profile

Log Out of All Sessions feature added to the User details screen allowing administrators to forcibly log out a user

Change string "Recorded Extension" to "Owner Identification" to better reflect the content of this field

Improved the speed of the User Suggest (autocomplete) feature

Group filter added to Users Without Recording Report

New Report: CDR Reconciliation for Skype for Business Summary added to show some of the new diagnostics information created for Skype For Business CDRs if the call was missing or not correctly recorded (recording errors were detected)

New Intelligent Voice (compatibility mode) processor added for basic speech transcription integration with the Intelligent Voice solution. The integration supports single language transcription and diarization.

SearchCalls and GetCallInformation APIs returns the attached labels if the returnLabels=1 parameter is added to the request

Media stitching for advanced voice data (e.g. trader voice) performance improved for GSM-FR based audio

Media files that are corrupted now automatically have the worst voice quality score instead of being ignored.

Enhancements for IM transcript files exported by an Advanced IM export policy (Microsoft Teams): - Original JSON content, received via the Microsoft Graph API, is added to the exported IM transcript file (XML files with .im extension) - Attachment information (original filename, attachment location on storage) is added to the exported IM transcript file (XML files with .im extension)

SMTP target attachment options are improved: - The type Media File means file attachments only in the case of IM conversations (the IM transcript files with .im extension will no longer be attached with this option) - New type "IM Transcript File" attaches the .im IM transcript file if available With these new settings, someone can configure the system to attach the IM transcript files without attaching the files shared in the chat conversations.

SMTP Header To address field could only contain/use the first email address when multiple addresses were defined. From now on it will support multiple email addresses.

Instant message export via SMTP displays the participant join and leave events at the right place (at the right time) in the message flow. Before the join events were listed at the beginning of the conversation (regardless of when the participants joined) and the leave events were displayed at the end of the conversation.

New Add Media Error Fields setting, under Storage/Export for advanced export which allows exporting the media errors

New option to disable Voice Quality Check for Skype for Business screen share recordings under Storage Management / Voice Quality Check / Process Skype for Business Appshare Conversations (by default is is enabled)

Multiple improvements for the installer: - Check if the database is already partitioned when upgrading - Ability to provide encrypted passwords as parameters in the installer and the PS deployment toolkit - Removed the deprecated Media Sorter service from the SCOM management pack

New Vodafone Import Source added to enable the integration with Vodafone Mobile Recording solution. The integration utilizes the FACE API to download and ingest the recordings from the Vodafone platform.

Cisco Webex Teams import source was slow due to participant chance inefficiencies: - automatic cache cleanup - 404 not found users won't be queried for each conversation - logging improvements

Import sources use the valid from and to values from the recorded extension configuration to determine if the conversation record related to the extension should be imported or not when recording rules are enabled. Before the service only used the extension change log database table which did not allow configuring extensions valid before the installation date of the system.

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

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

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

The Owner User ID was not determined in some call scenarios and user assignment did not work for these call legs

The Skype for Business IM Filter service didn't parse the HTML message properly and skipped e.g. special characters in group chats.

The Verba Microsoft Teams Bot Service stopped listening for incoming recorder connections after 5 unsuccessful attempts.

In the case of participants with unknown UPN, the participant list filtered out the multiple participants with the same join time.

The 'Record Only If External User is Participating' configuration was applied for P2P calls too

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

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.

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

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

IP Trade generates dummy CDRs with 'fakeuser' which are now filtered out

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.

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

SMS Recorder Service did not insert data into the right tenant, instead it inserted all data into the reference tenant in multi-tenant deployments

Workaround for missing participant leave date (unexpected) for Zoom Meeting imports

Media upload did not work in certain regions due to unannounced changes in the authentication method in the Zoom APIs

Multiple Zoom Meeting and Phone import reéated 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

Advanced IM viewer (Microsoft Teams) failed to render a message if it was a message reference without a proper user display name.

The column names were not visible in the Excel list export because the color of the text was white

The advanced export task couldn't be created in other tenants, only in the reference environment

The "Do not request PIN on Recorder Line" configuration was not visible on the Extension detail screen

Reverse Proxy based SSO did not work for the first time, also added an option to turn off the Session ID renewal

Microsoft Teams chat PDF export didn't download the generated PDF file in the Viewer

The Change Configuration Settings screen's Refresh link displayed an error

Encrypted calls could not be played back when the Direct URL was used to open the Conversation Details

The Audit Log entry details were missing for the Login event

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

Dashboards couldn't be created by a user whose email address property was missing

The Recorded Voice Quality Issues dashboard widget search filter did not correlate to the Search menu when opened through the widget

Roles and Permissions report did not work in v9.7.5

Verba Import API did not work in some cases and generated an error message about content length mismatch

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.

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.

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

Missing event ID object in the alert definitions in the SNMP MIB

Storage Management Service could have raised false alerts on upload failures (no matching policy) due to race conditions in database and file operations

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)

Deduplication storage action was unable to find the 2N pairs of a call when 'timestamp-based policy' was enabled.

Advanced Export did not work in 9.7.2

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

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

Advanced export did not work for Microsoft Teams IM if the content included adaptive cards/polls or inline image

SMTP export using plain text was using HTML content type when there was a HTML tag in the content

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.

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.

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)

Policy based IM export failed for Skype for Business chat messages when the URL field of the chat's CDR record was empty

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

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

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).

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

The installer should not accept commas when providing a port for the SQL server connection

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.

Skype for Business CDR reconciliation reported already processed non-recorded conversations in some cases

Generic Import - IM Content fields were duplicated in case of doing export or doing field mapping testing.

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.

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).

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.

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.

Segmented IM integrations such as Webex Teams or TeleMessage no longer create CDR XMLs in the media folder

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