Verba Release Notes

Support for CUCM 10.0

Support the load balancing in proxy recording mode

Load balancing and failover for Lync Announcer services

Conference chat recording

New mobile optimized beta web interface (login - https://<server>/verba/mobile, SSO/AD - https://<server>/verba/sso?ssotarget=mobile&nowb=1)

Verba Media Player supports HTML5 audio tag for voice recording playback. It is able to playback audio calls in Chrome and Firefox on every OS without Windows Media Player plugin. Internet Explorer still uses WMP ActiveX controls for playback. Playback for Verba Media Format and player based silent monitoring still requires WMP and Verba Codec plugin.

New load-balancing concept based on recorder mirror groups (those get traffic at the same time) and group priorities (load-balancing is done between recorders at the same priority level)

Actiance Vantage integration initial version

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

Cisco-GUID SIP header is now gathered for each call if present. Intended to use for UCCE/X integration

Optional SIP message reordering support

Lync application sharing sessions now generate call events to trigger desktop screen recorder

Load balancer will route all data of a call to the same recorder proxy to avoid duplicates

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

More detailed stats about recorder groups/connections

Optionally recorder can now detect participant roles (caller/callee) for BiB based recording

Calls to Hunt Group address displays the Agent Extension

JTAPI logging improvements

Automatic reconfiguration on the fly in Cisco IM recorder

Multiple Cisco IM&P servers can be configured on a single Recording Server to provide support for failover scenarios

Chat sessions are handled separately based on participants' point of view. If both participants are recorded the service creates separate recordings for each party.

P2P announcement settings are added to the Lync filter configuration

Lync call direction detection based on recognizing mediation servers

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

Configuration improvements

New SIP URI parser in Lync Filter

Verba Meeting Recorder Extension for Lync Client supports both Lync 2010 and 2013 without need to configure Lync version

Remote traffic capture service added to Lync filter installer

KeepAlive implementation added to Lync Announcement service

The Lync filter can optionally trigger announcement for Lync 2 Lync calls

Platform call id CDR field of Lync conference calls is changed from MS-Conversation id to meeting id

Storing information about multiple participants

Improved manageability of Lync IM Recorder service

No direct DB access needed from IM service installed Lync FE servers

Ondemand recording mode for Lync IM recording

Lync IM recorder service now supports windows authentication for SQL connections

Advanced recording rules feature added to Avaya Recorder

Minor logging improvements

Conversation list in IPTrade now display local time instead of UTC

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

Firefox support for auto pause feature has been implemented

Desktop screen pop-up is now shown on all terminal sessions, when the user has more than one, screen capturing works only on the last session

New Active Directory Synchronization attribute: "User Matching ID". Use "ObjectGUID" in this field when the login name can be changed in the AD. If "User Matching ID" attribute is set up, Verba will match AD users with Verba user using this attribute.

New option in Active Directory Synchronization: "Screen Capture Enabled"

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)

"Record non-configured extensions" checkbox removed from Verba Server Configuration. Defaults to "false", should be manually turned of off existing servers.

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

OpenSSL version used by Tomcat is changed from 1.0.1g to 1.0.1h

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

Initial version of Ethical wall configuration parser

Added Ethical Wall rules for Cisco phone calls

Agents Quality vs. Productivity (Calls Handled) report shows the total number of calls selected for evaluation for each agent

Decryption of SRTP streams not followed from the beginning (e.g. silent monitoring, controlled recording)

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

IM recording related database updates

Recorded party field written into CDR when applicable

Optional script to automatically share recordings of Verba group named "Auto-Share"

License page usage notification limit changed from 90% to 95%

Automatic registration of unconfigured, but recorded extensions (e.g. in case of Cisco forking recording)

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)

Optional filter makes sure recorders are assigned by the first RTP packets and not by STUN pings

Improved SIP Subscribe-Notify based conference event handling

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

The RS role's contains the latest filter settings

Tomcat7, and Java7 support is added to the installer

Verba services are now installed with service user if the Windows Authentication is selected in the SQL server dialog

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

Command line option for LyncFilter installer to avoid asking for SQL credentials

UCMA calls can now optionally be detected based on configured user agent names. To avoid duplicate/unexpected CDRs, caller and callee information is retrieved from non-UCMA participants' URIs. B2B call ids are registered for each session, if Geomant Contact Expert does not return metainfo based on SIP call id0 we try id1

OpenSSL TLS ctx is now set not to resuse existing sessions

Change Password menu is not shown to users who are only allowed to log in with SSO

Access control problem related to Private tag

Video codec ID in CDR is filled only if video was recorded in the current call

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

Caller and callee might be swapped in Lync 2010 RGS calls

Lync RGS fix

Failure to start record when one of the configured NICs are not available

Issues with SIP UPDATE and reINVITE based B2B transfers

Rare issue in passive recorder load balancing

Fixes for handling escalation of audio calls to video

RGS caller/callee was swapped in certain calls on Snom phones

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

Recorder connection management fixes, during connection establishment and login socket timeouts are handled now properly

Recording stream stickiness algorithm used in load balancing did not work in certain scenarios leading to double recording

Minor bug related to Call ID handling

Store the actual extension number instead of the Hunt Group number when a Hunt Group number is called.

Configuration improvements for Cisco Silent Monitoring and Coaching

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

In case of large amounts of Cisco phones with RTP forking OutOfMemoryError might appear on systems with <1 GB free RAM. This is no longer the case.

Patch for Lync 2010 Response Group recording

Lync filter might crash when third party tool tries to connect to configuration port

Log level of keepAlive sent log entry changed from Debug to Insight

Simulring issue is fixed when one of the clients is not audio/video capable

Improved keepalive resolves timeout issues

SSL read timeout set for the proxy connection (15 sec)

Resolved issue in recording rule handling, Asserted identity field is checked with URI and without uri (forwarded calls to PSTN)

IPv6 address parser issue caused skipping the whole call, even if media connected via IPv4 candidates. This affected edge and mediation based recording only.

Memory leak in P2P announcement service

Bug fixed when the non-recorded party cannot join to a conference

Lync announcement service might can make announcement twice for P2P calls

Internal locking issue in proxy mode might lead to unexpected service stop

Race condition may lead to multiple Lync announcements

Announcement can be heard multiple times by some participants intermittently

Some sessions might stuck in ongoing conversations during service shutdown

Issues with SQL Server reconnections

IM service did not start up with certain valid configuration parameters

Minor fix for the Lync IM recording when guest users are joining to the conference

Using extension numbers instead of the DeviceID to track transfers improves data in certain cases

IP Trade recorder is now filling the recorded_party CDR column

HTTP API triggered dictaphone recording now updates Dictaphone UI state as well

Auto pause/resume might be triggered by URL in out of focus IE window

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)

SSO and Jabber Client related fixes in mobile web client

Ondemand Calls Buffer might throw exception when Private field was displayed on the call list layout

Multiple token-input values could not be added when the ID field was not string

Due IE 11 bug Extension edit page did not work when the Avaya password field was filled in

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

Fixes on the ongoing calls screen

IM conversation icon issues

Storage folder in data retention policy is no longer mandatory for "transcode" action, but it is mandatory for "export" actions

Request and response header fixes in media streamer proxy

Possible integer division by zero exception fixed in waveform generator

Simultaneous Calls Dashboard/Report might show incorrect values

Yes/No/NA type of question on an evaluation form could not be saved if the default selection was N/A

Silent monitoring media is now always sent from the same IP address where the monitoring session request was received, this improves support for multiple NICs in recorders and NAT.

Mono media handling fixes

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

Provisioning v2 SOAP interface issue leading to users with multiple primary groups

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

Servers installed in cloud mode were not registering the node at first startup

CDR database inserter now takes into account if voice activity statistics generation is enabled and writes silence percent, threshold percent, longest silence sec even if all values are 0

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

Licensing correction - IM sessions do not count in "# of Recorded Hours Per Day"

On-Demand extensions in certain cases were counted twice in license usage

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

If multiplexer does not find a voice file and the task is rescheduled, sometimes it might be reprocessed only after a very long delay

At codec change during playback the previous codec was not properly flushed out before initializing the new one

Fixed RTP payload types are always added to RTP processor, because CUBE does not handle calls properly if not the first codec is selected from the SDP answer

Video playback via VMF framework might freeze/jump in case of voice stream with silence suppression (Lync video), since video playback is synchronized to audio and audio timestamps might jump too big in case of long silence periods. Mixing algorithm redesigned to support silence suppression in video calls properly.

Rare deadlock scenario fixed in networking code

VMF recorder sink might overwrite the initial stream descriptors with the final ones at closing the file leading to improper decoding parameters at the first segment in case of mid-call codec/stream changes

In certain situations H.263 decoder swapped U and V channel resulting in blueish colors

VMF buffering and mixing changes to improve silent monitoring

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

If primary record has to be overwritten with secondary one in media sync mode now the start and endtime is also updated

Upload management related fixes

The Verba Dial-in Recorder is now available on all Verba server roles

Debug messages removed from the installation process

Reread of LogLevel configuration in Lync Filter fixed

Geomant Contact Expert stability fixes

Geomant call id is now stripped till last #

Recorder can detect Geomant Contact Expert calls based on UCMA app name in SIP useragent field and sends metainfo request through multiple connections