Verba Release Notes

Recording Notifications for Lync - New user based notification/announcement configuration settings. Notifications can be enabled/disabled, audio prompts can be defined for PSTN inbound and conference calls. - learn more

Quality Management for Instant Messages - IM conversations are now presented in the same view as audio, video and screen calls, ready for use in Quality Management

Summary

Call length mismatch due to silence suppression If there is no RTP sent in any direction since both side are on mute/do not talk Lync stops sending RTP (or at call start does not start sending RTP). These gaps between voice parts (where RTP is sent) are filled, but the gap (if there is any) between call start - first voice RTP and last voice RTP - call end cannot filled.

Impact

- this issue leads to losing silent segments, but not actual voice recording - it leads to time difference between presented recording time and actual recording time of media - mostly conference calls are affected, especially the first participant who is on mute until others arrive

Workaround

- there are currently no known workarounds

Summary

Using a very large AD might cause timeout issues in the AD sync process. An AD timeout can lead to unwanted reconfiguration of the recorded users when only a subset of the configured users are retrieved from the AD during the sync process due to timeout.

Impact

- if the AD query runs too long, it can lead to unwanted reconfiguration of the recorded users, which can result to loss of recordings - there is no indication or alert if timeout occurs

Workaround

- include (ObjectCategory=person) in the search filter to reduce search time - increasing the timeout value on the AD side might prevent this issue

Summary

There is one way audio in recordings after SIP re-invites when media bypass is active. The SfB/Lync Filter service does not recognize the SIP re-invite messages properly when media bypass is active, and the call is only partially rerouted through the proxy. This results in one way audio in the recordings after the first re-invite. The re-invite period is controlled by the session timer configured for the connection between the gateway and the SfB/Lync system.

Am I affected?

All 7.0 and later SfB/Lync recording deployments using proxy based recording are affected where media bypass is configured with SIP session timer.

Impact

The Verba SfB/Lync Filter does not recognize SIP re-invite messages properly when media bypass is active and the call is only partially rerouted through the proxy. This results in one way audio in the recordings after the first re-invite. The re-invite period is controlled by the session timer configured for the connection between the gateway and the SfB/Lync system. When the default SIP session timer setting (1800s) is used, the first re-invite is sent after 15 minutes. Thus all inbound or outbound calls longer than 15 minutes are affected. Prior to the re-invite, recordings contain both directions.

Workaround

Disabling the session timer or media bypass completely resolves the issue

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.

Summary

Reconnect issue between the Verba Lync Filter and the Verba Media Collector & Proxy components In case a large number of Filters are trying to reconnect to the Media Collector & Proxy service at the same time, none of them will be able to connect due to an issue in the connection handling process. This could be the case when there are at least 8-10 or more Filter applications in the system and the Media Collector & Proxy service is restarted. This issue only occurs if there are a relatively large number of Filters (8-10 or more) trying to reconnect at the same time.

Impact

- If the Filter component is not able to connect to the Media Collector & Proxy service, signaling information cannot be shared, leading to a call recording service outage - If system monitoring is enabled and configured properly, the system sends alerts for all Filter connection errors when the Media Collector & Proxy service goes down - All Verba v8.3 deployments for Microsoft Lync 2010/2013 and Skype for Business whith Proxy, Edge, Mediation and AVMCU based recording are affected

Workaround

- First all Filter services need to be stopped, and then started in a sequential fashion

RTP proxy now supports a separate port range for video

Failed/crashed recordings can be restored partially after service restart in Cisco central/RTP forking based recorders and Cisco GW recorders

Recorders can optionally hide transfers to the recording announcement service (improves presentation of recordings)

Business related metadata can be retrieved from Avaya phone system (e.g. customer IDs)

Failed/crashed recordings can be restored partially after service restart in Dial-in recorders

IM conversations are displayed in the same view as audio and video media, former Verba Player is now called Conversation View to accommodate this change

New custom user fields introduced

User/Group permission separated to three permissions: "Users", "Groups", "Group Membership Administration"

Simplified Conversations menu

User lookup is now available for custom user fields as well in participant sets.

Timezone option added to Conversation Export scheduling configuration.

Recent Than filter option added on conversation export page

New Users Instant Message Activity Details report

Sending generated report files as attachments can be turned off in the notification email.

"Run Each Active Directory Profile Now" is now only visible for users with Read Only access to Active Directory Profiles (Update/Create not needed)

When multiple MRs are deployed, if the first MR successfully executed every AD Sync profiles, then the other MRs will not run AD Sync. The server host name added to the AD Sync log tab (it will make finding the proper log file easier). Comparing the last user read in normal order to the first user read in reverse order. Comparing the number of users read in normal / reverse order (turned off by default). Rolling back every operation if the rate of the users that would be deactivated is larger than 10% (turned off by default).

The secondary and primary copies of a recording are marked for as related conversations.

More lenient handling of case insensitivity in SIP processing

The SQL Server Native Client installation is now optional

Windows Service account page added to the main installer

Label Creation event was not visible in Audit list

Microsoft SQL Server JDBC library updated to 2.0. The previous version had a bug when connecting securely to a SQL Server that has a certificate larger than 4 kbytes. The error message was: "The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: The TDS protocol stream is not valid"

XCC provider registration lost alerts are not sent at timeout but if registration cannot be reestablished. Could not reproduce the issue with 15.3.3x IOS, but at customer with 15.2.2 IOS stopped after a while sending solicit probing resulting in registration lost alert on our side (even so call events were sent to us).

New option for XCC alerting level to workaround some false alerts due to registration timeout in case of 15.2.2 IOS

Port allocation is incremental in the defined port range, ports used recently will not be reused for the next call, only when the port range end is reached, and allocation starts from the range begin.

Database issue when XML writing is turned off

SDP update issue when media-bypass enabled with SRTP capable gateways

Only alive/connected Lync announcement services are involved in the load-balancing to avoid connection establishment overhead

Duplicated conversation legs were stored for certain conferences

RTP processing failed for Telex ROIP packets

PDF export option missing on certain list pages

Issues with Data Retention Policy list search on GUI

User Save threw Exception if the user came from the Extensions List

Audit log was not created for modality configuration change on recorded extensions (other than voice)

Conversations / My Conversations displayed the results in GMT. It worked after clicking on the Search button again though.

When an older system upgraded and Legacy roles created, 'Comment (Legacy)' role was not granted 'Comment' permission

Sometimes calendar hid select elements without a reason (very old browser may not be compatible with this change)

Storage Target field on the conversation export page was not initialized properly in case of an already existing export task.

Quality Management: Date interval / To jumped back to current day on Save when Type was "One time conversation selection"

Deny type ACL fixes in recorders

Media length was calculated incorrectly when silence suppression was used and the media ended with a silent period

Alert description in XML was not escaped

Email notification handling fixes

SQL connection and execution checks are improved with better error handling and logging

Actiance Vantage integration fixes related to call deduplication and load-balancing