Verba Release Notes

General availability of the new communication policies component allowing organizations to implement ethical walls and information boundaries, using session blocking, content filtering, disclaimer notifications, and presence control. - learn more

New configuration option to detect call directions properly by providing phone number and/or domain patterns for internal endpoints. - learn more

New integration with Smarsh compliance archive service allowing archiving or exporting IM, voice and video recordings from Verba.

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

Network port mirroring based SIP and SCCP recording might suffer from memory leak due to a TCP session cleanup bug found in TCP/IP reassembling

Am I affected?

All 8.4 and 8.5 port mirroring based recording deployments are affected. However Lync/SfB recording deployments are not affected, unless Mediation server based recording is used and standard SIP traffic is captured with the same component.

Impact

If the process runs out of memory and memory allocation fails for recorded sessions, then loss of recording might occur until the service restarts. The amount/speed of the memory leak highly depends on the amount of monitored traffic and the number of total TCP sessions monitored.

Workaround

There is no known workaround.

HTTP basic auth and redirection support implemented for media downloading related to Cisco MediaSense 9.1.

Extensions are automatically added to the Extension list: - only for Cisco Central Recorder's recordings - never adding "Conference" conversations - add an extension only if it was recorded two days in a row (to avoid false registrations or temporary configurations) - the Extension's description will be e.g. "Automatically added at 2015.07.06 16:07"

Dynamic event registration option is added to the configuration for Cisco IM&P 9 or below.

New performance counter based load balancing options for Lync/SfB Filter and Proxy, Lync/SfB Filter and Announcement, Proxy and Recorder connections. The new options allow configuring load balancing based on maximum number of sessions, current CPU and network load.

New send email with audio attachment feature after a recording is finished

New menu structure on the user interface for optimized view and greater clarity.

New AD synchronization settings to check the completeness of the sync process

AttachMetadata API call improvements: new parameters supported: metaTemplateId, metaTemplateName, metaTemplateType looking for the field not by the business_id column but by the uccx_id field too.

New audit log entries are created on metadata value changes

New Users Roles Permissions Groups report detailing role, permission and group membership settings for users

V4 license support introduced, support for older license versions is maintained.

New Storage Type: External Verba Media Repository

Improved SMTP configuration page in the installers

Issue with TCP reassembling of SIP messages resulted discarded complete messages

When "Advanced Recording Rules" is enabled, and "RTP Started" event received before "Established" event (JTAPI), then the call were not recorded in some cases (observed with Jabber clients only).

In case of large number of monitored phones, Cisco silent monitoring service (JTAPI) resulted OutOfMemoryError.

TLS connection error fixes, increased timeout settings and thread handling fixes in Lync/SfB Filter component.

When a recorded voice call was escalated to a video call, the recorder created a separate recording in VMF format instead of the configured voice media format.

Fixed an issue related to Skype for Business video conferences when only one stream was properly established with each endpoint, other participants could not be viewed properly.

Media Collector and Proxy service might crash intermittently when UCMA B2B call is terminated. It affects UCMA B2B call flows where both call legs of the same media session are recorded, and media is still being sent after one call leg is ended.

Conference announcement reference counting: even if announcement was not involved (due to no media) it was disconnected from conference at recording end which resulted in prematurely drop the service from the conference.

Fixed SIP sequence counting issue which caused missing messages in rare circumstances

Outgoing Bridged Appearance calls were not recorded in some cases.

IP Trade recorder inserts calls to ongoing table as other services. Timestamp on turret can be converted from UTC to configured timezone local time

Email address may not be synchronized if it was initially empty and later it has been set in the AD.

On webapp start, remove "restart" task not only for the simple host name but for the canonical host name as well.

Player may displayed warning "Only secure content displayed"

Wrong user was associated with a conversation when the agent_id field was empty.

Quality Assurance may not worked in Multi-Tenant mode

Lync Recording Announcement settings were overwritten by AD Sync (from now on, it is effective only when creating a new user or moving to another AD Sync Profile)

When sharing an IM conversation, the conversation was treated as a voice recording and the media player was opened on playback.

When an environment was changed by the user on the search screen, the auto-search was performed for the previously selected environment.

Call redirection to the announcement service in the SfB/Lync Filter was not backward compatible with server-only settings, where there were no user based announcement settings. Now, you can have system wide announcement settings, without the need to configure announcement for each individual user.

In case of primary key violation earlier the recorder deleted the call from local cache. Now it just marks as inserted into SQL. This issue might occur if query timeout happens even so the call is inserted, so at next try the recorder detects PK violation.

When RTP processing received a packet which was not divisible by the fixed length of the codec payload (G.711/G.722/G.729), the decoding process might crashed.

STUN parsing changes to provide backward compatibility with RFC 3489 for SNOM phones.

Archive and export policies did not consider a situation when files are not available on source storage but according to the database, the call has media url specified.

Data Retention Policies: do not allow Schedule for Upload policies initialize Time of Next Execution to the current time when creating a new policy