Verba Release Notes

Support for SfB/Lync persistent chat room recording

New maintenance mode feature is introduced to gracefully shut down a Verba server or selected services for maintenance. When maintenance mode is activated, the system will notify all affected services and will gracefully stop the main functionality of the service(s) to prevent data loss or interruption. - learn more

New IBM Tivoli Storage Manager based storage target is added - learn more

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.

New service performance counters added including average message count per sec, number of blocked events, etc.

If the agent is not recorded but the ACD group is, we can duplicate the record and import on behalf of the agent as well.

Conversation Export enhanced so it supports a timezone setting at the "Rename Files" section.

If there are no extension ranges configured for a tenant, then allow any extension to be set up.

New option for conversation export to support exporting without creating sub folders.

Conversation export now supports filtering based on media type.

Do not roll back the AD synchronization of a user if the group changes can not be performed.

New configuration values are added to existing configuration templates (even if not default) during an upgrade.

On-the-fly MP4 video encoding during recording

VMF media processing framework was limited to support only 3 audio and video mixing layout. Now any number of streams are supported. Video layout is set dynamically according to current number of active main, presentation and panoramic videos. Lync panoramic video was shown twice in the recording of sender in case of conference call (MCU sent back the same panoramic stream, now this is filtered and not shown).

New alerts are available to monitor SIP trunk state changes.

Memory alert template has been changed to show the list of processes too

Screen capture multiplexer now support if voice media is in different storage folder than the uploaded screen file

Newest version of Tomcat 8 is included in the installer (v8.30)

Small memory leak caused by OpenSSL as it allocates an error stack for each thread calling any OpenSSL function but does not deallocate it.

Deadlock occurred when a session operation didn't succeed and another thread tried to open the same session.

The SfB/Lync Filter did not listen to certain events on the application connection object. It could cause operation errors, e.g. the FE server dropped the connection but the filter couldn't notice that.

The SfB/Lync Filter component relayed all conference call legs when the conference host was recorded, even if other calls should not have been recorded.

In SfB/Lync RGS, if agent anonymity is enabled and the recorded caller is transferred by a non-recorded agent to other non-recorded agent, the transferred leg was not recorded.

The filter did not send the error response to the proxy, because of a NullReferenceException in a allocatedproxy store.

Recording may stopped if a non-answered incoming call arrived to the recorded station during another active call.

Recordings could not be deleted on the user interface when the underlying storage did not support file rename. Data retention policies were not affected.

Special characters were not searchable in metadata and markers.

The lack of a primary group membership may caused a user to not be synchronized by AD Sync.

In multi-tenant mode, group modification may threw an exception.

When participant set reached or exceeded 20 items the later additions of the items failed.

Agent View is now working with cloud mode. Minor fixes on the Agent View GUI.

The SfB/Lync Filter component did not recognize the call direction properly and the announcement was not played when multiple SIP domains were configured.

GetExtension method in the provisioning API did not work when only the active extensions were queried.

When a recording inserted into the database, the user association trigger used the current time instead of the recording's start time.

Transcoder did not change video flag to audio flag when transcoding from video to mp3.

The system monitoring service during start did not send alerts in some cases.

The description of the Windows Event Log entries were not properly configured and system error messages were displayed.

Data retention policies did not filter for group member flag when filtering for group memberships.