Verba Release Notes

Support for CUCM 10.0

Support the load balancing in proxy recording mode

P2P chat recording

Provisioning API Version 2.0

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.

Openssl updated to 1.0.1h

Improved call ID (Native ID) algorithm for SIP, H323 and SCCP using protocol sequence numbers

Call timeout handling is done from dedicated timer thread instead of capture threads

Meeting URI/ID handling added

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

Recorder queue size, signaling and RTP wait times are now configurable

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#

JTAPI logging improvements

Automatic reconfiguration on the fly in Cisco IM recorder

More recording control options for Lync IM recording

Improved Lync B2B call handling: if both legs have the same CDR info (caller/callee) we process only the first one.

Call blocking mode is added to the Lync Filter, recorded calls will not connect when there is no available recorder, configurable

Automatic provisioning support is added to the UCMA based announcement service

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

Avaya Recorder configuration auto-refresh for extensions

CDR information is now sent to media receiver

Desktop agent mute function can now "mute voice only" or "mute voice and discard screen"

Firefox support for auto pause feature has been implemented

SIPREC parser improved with uniform handling of blocked caller ID

Average Score by Question report added

Terminology change: "Caller" changed to "From", "Called" changed to "To"

SearchCalls API call accepts new parameters

HTTP Business API supports a new parameter when searching for calls: nativeID (Technical Call Identifier)

Support for LDAP over SSL is added to Active Directory synchronization

Bulk phrase update

Playback reporting has been added

New Webapp configuration parameter: continue or Web player can now either continue or pause playback at the end of markers

Time of creation and time period included in the report email template

"Auto fail" on quality management questions where evaluated as "lower than", now it becomes "lower or equal".

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

Minor UI improvements

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

Improvements in multi-tenant recording and access control

New CDR parameters

Verba web application is now compatible with Tomcat 7, tested with Tomcat 7.0.39, APR 1.1.27 (still compatible with Tomcat 6)

Support of multiplexing Lync appsharing triggered recordings (no audio to mux with)

Improvements in silence detection implementation

Audio and video mixing optimization in case of RTP time misalignment

Email alert header provides more information about the issue (host, service, alert 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

SIP parser now prefers MS-PAI over from/to, remote-party-id and p-asserted-id headers as caller/callee. This reflects always the original/non-normalized caller in case of Lync PSTN outbound call.

Better timeout mechanism when multiple remote capture sources are used for recording

Problem with configuration reread fixed

SIP/Skinny/H.323 session timeout calculation in case of multiple remote capture sources with out-of-sync clocks might intermittently lead to unexpected sessions termination

Connection Up trap/alert was sent only until the first packet arrived over the connection, in case of remote capture connections this delayed sending until the first call

Improved SIP/Skinny session timeout calculation in case of multiple remote capture sources

Changes in UCMA B2B call agent call flow support

Potentional resource leak (timed out sessions) due to improper RTP proxy session timeout calculation

Rare crash during graceful shutdown

Uninitialized variables related to SDP modification might cause exception and skip processing of SIP message

NIC capture thread exited in case of any capture exception (NIC link down, NIC disabled...). Now the capture thread tries to recover periodically from these error states

Improved purging of unused RTP connections

In certain cases participant list not filled properly when a call was transferred multiple times

In rare cases to and from party might be swapped in Lync RGS calls

Rare issue with thread synchronization fixed

IVR number parsing error is fixed

Caller and Callee CDR info was swapped in Lync Response Group calls (IVR mode only)

Management issue with Lync Filter

Some sessions might stuck in ongoing conversations during service shutdown

Issues with SQL Server reconnections

If an extension was removed and then re-added, it was not registered again by the recorder service

IP Trade recorder is now filling the recorded_party CDR column

Rare issue with SIPREC recording decision

Some SIPRec sessions might be inserted into DB with null start time

Issues with recording and ondemand decisions in multitenant environments when recording SIPREC

Feedback sending did not work properly with Chrome, especially when the popup windows were blocked by the browser

Retry database searches when snapshot isolation error occurs (maximum X times)

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

Some API calls related to Markers did not release the database connection properly. This may led connections to be exhausted so the web application may became inaccessible.

Search Calls API did not work when returnSharedItems was set to 1

Markers added by unauthenticated API calls were not shown in the player

Fixes on the ongoing calls screen

Overall Call Direction Trend widget on dashboard did not work if direction field was null in the database

Silent monitoring might crash while initializing the session in rare circumstance

Mono media handling fixes

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

In multi-server environment a server might use an other server config data when a value is rolled back to the profile value and the other server had a custom setting for that config

Transcoding issue when one call matches multiple storage policies

Database issue related to chat recording

Automatic call markers might not get inserted if a call is not assigned to a user

If number of processing threads are not explicitly specified, we default to 'number of cores x 2' (instead of 'number of cores')

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

VMF framwork H.264 SVC MST mode fixes and audio/video mixing improvements

VMF - H.264 SVC decoding fixes

RTP dejitter buffer might fail to propagate EOS to leading to unstopped silent monitoring session after call ends

Possible deadlock between encoder control (keyframe, bitrate control) and media sender threads fixed

H.263 depacketization fix

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

CallTimeouts increased from 30 to 300 sec in proxies, 30 to 180 sec in passive recorders

Resolved problems multipart content in SIP

Resolved potential deadlock in multithreaded SIP processing

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

PrairieFyer contact center metadata parsing fix