Verba Release Notes

Recording redundancy for SIPRec based Cisco gateway recording

P2P chat recording

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.

Optional SIP message reordering support

Call direction can be detected now based on user-agent type, in Lync environment PSTN call direction is detected based on Mediation server participant now by default

IP Phone Service can be used without the need of configuring the login name for each device. Additional parameters to use the new feature: byDeviceOrIp=1&name=#DEVICENAME#

New configuration parameter (Cisco UCCX IP Addresses) and warning to restart service after changing UCCX Metadata Templates

Improved configuration tree for Cisco IM Recorder

Lync call direction detection based on recognizing mediation servers

Proxy loadbalacing is added to the filter service. The filter supports multiple proxies, and the filter balance the load between them based on the network configuration

Option not to show Lync Trusted-UCMA users (announcements, music....) in conference participant lists

Recorder reliability improvement when the SQL Server is offline

New HTTP API for Dictaphone control

Option to avoid manual resume during screen capture auto pause

Support for LDAP over SSL is added to Active Directory synchronization

Style enhancements for auto-complete fields

experimental version of new HTML5 media player

New "Quality Management Enabled" user setting, only enabled users calls can be selected for evaluation

Passive recorders now insert marker for silence and talkover periods if voice activity detection is enabled

Improvements in multi-tenant recording and access control

Recorded party field written into CDR when applicable

Memory allocation optimizations

Fixes for stability issues related to intermittent memory corruption

Support for L8 and L16 RTP/AVP audio and video payload type

Improved SDP handling for better compatibility, c line is added both at media and global level now

New "upload protocol" added to recorders: local file move

Tomcat7, and Java7 support is added to the installer

The recorder dialog window has been removed from the Lync Filter installer

OpenSSL TLS ctx is now set not to resuse existing sessions

TCP reassembling might stuck due to lost segments

Issues with SIP UPDATE and reINVITE based B2B transfers

RTP proxy was not aware of SDPs with application/gw-sdp content type (related to Lync Mediation bypass)

SDP compiler changes due to compatibility issues with Kirk Wireless Server

RTP relaying modification to make possible ICE connectivity check in early SIP dialog phase (when SDPs are partially exchanged in B2B calls)

Improved purging of unused RTP connections

Extra newline at end of Cisco IM sessions

Management issue with Lync Filter

IP Trade recorder is now filling the recorded_party CDR column

If ACL was disabled calls recorded via SIPREC/Cisco CUBE were duplicated as if both participant were to be recorded. Now if ACL is disabled only one instance of the call is recorded.

Cisco SIPREC parsing improvements

Agents Call Activity Summary and Recording Servers Call Activity Summary reports did not work when there was a Group filter set up and the output format was other than PDF.

User lockout (because of wrong login attempts) did not work.

Fixes on the ongoing calls screen

Silent monitoring might crash while initializing the session in rare circumstance

Markers might be generated for voice analytics with invalid timestamp causing DB insert failure

Node manager agent might return false error codes to GUI

Multiple events of the same SQL connection error is logged once to avoid flooding the log.

After huge packetloss the H.264 SVC decoder might produce output with non-display order frames

VMF - H.264 SVC decoding fixes

H.263 depacketization fix

DB and call activity monitoring configuration issue found when weekend days were not configured

"SIP Uri Modification" parameter default changed to "Remove domain part for numbers only"

SDP/ICE parsing improvements

File upload batch listing now skips files not ready for uploading (.part, .ongoing)