Verba Release Notes

New Avaya recording service based on the Unified Call Recording service providing enhanced recording capabilities such as the ability to record encrypted streams, secure connection with the Avaya AES servers, enhanced meta information for complex call scenarios, load balancing and failover, storing DNIS, and more.

New EMC Centera integration added as a new storage target supporting WORM features - learn more

Summary

Siren7 decoding problem is causing garbled decoding of voice in certain cases.

Am I affected?

All Lync/SfB recording deployments are affected.

Impact

- Intermittently causes garbled voice recording when Siren7 voice codec is used for the call - The recording quality is varying for the garbled recordings, from light impact to severe degradation of quality - Siren7 voice codec is mainly used for Lync 2010 Windows endpoints and Skype for Business 2015 IOS/Android devices when network is degraded - Siren7 voice codec is also used for Lync 2010/2013 and Skype for Business 2015 meetings during poor network conditions

Workaround

- currently there are no known workarounds

Summary

Lync / Skype for Business IM conversations might not be recorded after recording and processing 10,000 RTF based messages.

Am I affected?

All Lync / Skype for Business IM recording deployments are affected. This issue affects IM conversations which are using the RTF format. Lync 2013 or newer desktop clients are using the RTF format for P2P IM conversation when both participants are using a desktop client. Conferences, mobile, and consumer Skype conversations are not affected by this issue.

Impact

- When the instant message is transmitted using the RTF format, the Verba Lync / SfB IM Filter application (on the FE servers) can use all available Window handles due to the improper deallocation of the RTF parser. - The service stops processing RTF based instant messages after approx. 10,000 RTF messages (after all Windows handles are consumed) - No alert or notification sent when the issue occurs

Workaround

- The RTF message format can be disabled by a client policy, for more information see https://docs.microsoft.com/en-us/powershell/module/skype/set-csclientpolicy, DisableRTFIM

Summary

Certain calls between Skype for Business and Teams or Azure VoiceMail cannot be recorded

Am I affected?

All Sykpe for Business recording installations are affected where the recorded users can call Teams users or place voicemail messages in Azure VoiceMail.

Impact

Certain Skype for Business calls cannot be recorded when a recorded Skype for Business user is calling a Teams user and one of the participants is outside of the corporate network, or a recorded Skype for Business user is placing an Azure VoiceMail message. This limitation is caused by the new call setup procedure, and specifically in ICE negotiation, introduced in Teams and Azure VoiceMail, which prevents the recording system to redirect and force the calls to the Skype for Business Edge Server where the Media collector can fork the related media streams. Since the system is not able to capture the media streams related to these calls, these calls are not recorded. No alerts are raised unless CDR reconciliation is enabled.

Workaround

Currently there is no workaround other than disabling Teams or Azure VM calling entirely for the recorded users. We are actively working on implementing a new solution which extends the capabilities of the Proxy Server to be able to relay these type of calls too. It requires a major change in the architecture by allowing the Proxy Server to relay calls with external participants through a public interface. It also means that that calls which are currently routed through the Skype for Business Edge Server and forked by the Media Collector Service will be routed through the Proxy Servers that same way as calls with internal or PSTN participants. We are currently targeting July 2020 with the enhanced version of the Proxy Server.

New alert notification is sent by the SfB/Lync Call Filter when the proxy configuration is missing or invalid.

SfB/Lync Call Filter support audio/video call blocking in case of Media Collector failure on the Edge servers.

Enhanced meta information for Call Park and Bridged Appearance scenarios

Removing and re-adding listeners when an extension is successfully re-registered to the AES

New and improved alert notifications are implemented such as screen capture failures, pause failure, recorder connection failure.

The default Standard User Role does not have Share Conversations and E-mail permissions from now on.

New alert notification on failed login attempts (disabled by default).

Additional safeguards are implemented to eliminate CSRF (Cross-Site Request Forgery) vulnerability.

Do not allow manual AD sync execution on servers where AD sync is disabled.

New LDAP failover servers can be configured for AD synchronization with a comma-separated list of host names

New default content filter rules are added during installation

Enhanced disclaimer and content policies allowing more flexible and fine grained configuration.

Scorecards are locked when an evaluator starts the evaluation, so other evaluators can not open them

Custom delay can be configured for prompts in conferences for PSTN participants to avoid collision with SfB/Lync Conference Announcement Service prompts

New Verba API to retrieve call mute state has been implemented

Significant optimization for database operations to related to file checks on playback.

Support for re-encrypting and signing legacy encrypted VF recordings with new, standard based encryption and signing.

Apache Tomcat version is upgraded to 8.0.36

Using Cisco network based recording, when a very short call is terminated, a false alert was generated intermittently related to call update failure.

Controlled recording mode was not handled properly when the new Unified Call Recorder service was used for Cisco recording with JTAPI integration, and recording was not started.

Cisco phone based silent monitoring listed every monitor-able call even if the user did not have rights to see them

When unexpected or malformed packets have received the compliance server could not create a proper response which caused the stuck of the connection between IM&P and compliance server. Now a default response is introduced. The default response can be configured available values are pass and handle.

Connection issue resolved between SfB/Lync Filter and recorder components, the system was unable to establish the connection between the servers during service startup.

Lync/SfB video mixing layout in conferences: there were cases when two or more video screens were mixed to the same position.

When a SIP session on hold was destroyed after 5 minutes, contact center headers for Luware integration were lost too

Simulring calls were not recorded when one of the devices sent a BYE request for the call and after that one of the other devices answered the call

Race condition error has been fixed which caused a missing initial message when the target user was logged in from multiple endpoints

Avaya JTAPI connection was not reconnected properly after disconnect

When special characters were included in the UUI field, calls were not recorded

When the Recording Director component tried to connect with invalid credentials too many alerts were sent.

Not unique session IDs generated by IP Trade turrets led to intermittent media processing and media timeouts when there was a collision between session IDs.

Screen content was not multiplexed to recovered recordings after a recording service failure

Using the Verba Screen Capture Codec, several artifacts were present when black text was on red or blue background

When a video call was imported, it was shown as an audio call.

User Group History shows effective group rights, and updates both "direct" and "effective" rights.

User deletion intermittently led to database deadlock, and caused failed operation.

Start search using this Label / Phrase did not work.

New Label Rule did not work when the user came from the Ongoing Conversations screen.

When a user did not have the right to see important calls under conversations, the important flag still appeared in the Verba player and the user was able to mark calls as important

Intermittent "NullPointerException" happened when "Recording Failed" column was added to the Search List Layout

Group hierarchy was not handled properly when a user removed from a group via the AD synchronization (he was not removed from the parent groups)

After the "User Must Change Password at Next Logon" checkbox was turned on for a user, the system asked for the new password but the user was not able to change it because the web application has kept asking the new password again and again.

"Non Recorded and Incorrect Conversations Details" report failed when group filters were used.

Groups Evaluation Summary and Group Performance Summary reports displayed different number of group members

Reports did not work if a special character was in the company name

Phrase filter takes into account non-alphabetic chars as whitespaces. Phrase filtering did not work for non-Latin1 characters.

Values of text type questions were not saved

New node manager certificate is added to the installer meeting Java Runtime 1.8 u72 security requirements

IM search did not work when Full-Text Search feature was not installed on the SQL Server

In case of Redundant Audio Payload (RED, Lync/SfB might use it in case of network degradation) the media processing buffers were underestimated for G.722 stereo payloads. This could lead to recording degradation or loss of streams in recording.

When the monitoring service could not query the service executable for version information, the service-related performance counters were not available

File deletion initiated from the web application randomly led to service crash for IBM TSM, Amazon S3 file caches.

Timed out download sessions (Amazon S3, IBM TSM) may result service crash intermittently.

Policy scheduler at startup might adjust next run date to incorrect date when no scheduling is set and date is Feb 29 in leap years. The incorrect date is considered as config violation and service will not start.

When transcoding was enabled in an export job, the system exported the original file as well, not just the transcoded version.

Wrong service user account was used for the installation if Windows authentication was selected and tested first and after it was changed back to Local System account.