Verba Release Notes

Support for Lync Panoramic Video conferences

New mobile phone recording integration with Singtel

Lync / Skype for Business announcer service supports new call scenarios: PSTN outbound and inbound/outbound federated calls - learn more

New generic SMTP storage target for exporting conversation to SMTP based compliance archives. Flexible configuration parameters to customize email content and metadata - 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.

Summary

Data retention policies (except upload and export) using the global schedule (not custom) are not executed.

Am I affected?

All 8.4 and 8.5 versions are affected.

Impact

This issue can not lead to data loss, however storage policies with non-custom schedules will not be executed. The following storage policies will only be executed when custom schedules are used: Archive in DB and Move Media, Archive in DB, Move Media, Delete, Export, Transcode, Create Phonetic Index, Delete Phonetic Index. The system does not send alerts or notification messages, there is no indication of the problem other than the policies are not running.

Workaround

Configuring a custom schedule for your data retention policy will enable the policy.

Alerts about SfB / Lync and recorder connection drop/reconnection. Earlier these alerts were triggered from filter/recorder side only, which could lead to delayed alerts when these components lost network connectivity or server crashed and did not recover within a short period of time.

Cisco persistent chat rooms now available as recording rules allowing capturing the entire traffic of the room

New alert when Lync / SfB Front-End connection is inactive If the Lync / SfB Front-End service is started after the Verba SfB/Lync Call Filter Service or the Verba SfB/Lync Communication Policy Service or the Verba SfB/Lync IM Filter Service, the Lync / SfB Server API might not start sending messages to these Verba services. This issue can cause loss of recording, because the application will not receive SIP messages from the API connection. This scenario can now be detected and the application automatically tries to reconnect to the server, and sends an alert.

Multi-tenant support is introduced in the Lync IM recorder

Verify station registration every time a recording initiated.

New permission: Customize own conversation layout

When a user is deactivated manually, the system asks the user if the associated extensions should be deactivated too.

Possibility to run single AD sync profile even if deactivated

New configuration option: "Send email notification on successful AD sync runs"

The announcement service configuration and load balancing has been changed. The announcement servers shouldn't be listed in the filter configuration, just the announcement uri is required. The system is now using the Lync/SfB provided load balancing and failover feature.

New service statistics are implemented in the announcement service.

New extension types: "User/Agent ID" and "Persistent Chat Room"

SQL JDBC Driver updated to version 4.2.

Dedicated media IP address can be configured now for the RTP stack, by default if this config is empty it reverts to server IP config

Media IP and SIP IP can now be configured as different/dedicated one for the stack

SIP reassembling and processing part revised and reorganized to gain more performance

New authentication option for SMB network folders. In addition to service user based authentication, custom credentials can be configured too.

Java 8 support is introduced and added to the installer, it supports both Java 7 and Java 8. The preferred version is Java 8.

On-demand call handling support is introduced in Lync/SfB extension window. The users are able to keep their recordings (audio/video only) using the Lync/SfB Extension Window.

TCP reassembling: TCP seq number overflow was not taken into account when current stream byte position was calculated. This could lead to discard subsequent TCP chunks

When SCCP call caller id is blocked the CDR shows same caller and callee number leading to duplicated recordings as both caller and callee are provisioned for recording. The SCCP parser is fixed and in this case the blocked cid is identified, shown in CDR as anonymus.

Lync/SfB PSTN caller from bypass enabled trunk, simulring: in rare cases when someone has already accepted the call but Lync/SfB still forks INVITEs to other parties, the INVITE received in connected state triggers deallocating caller side ports (one negotiated SDP vs 3 new offered in multipart content) and allocating new one leading to media connectivity failure at caller side.

Relay session was terminated if BYE was initiated by caller regardless which subsession the BYE was issued to. Now only the related subsession is terminated. If callee sent BYE the service worked properly.

Invalid STUN messages (length sanity check) were unintentionally discarded which might lead to ICE issues (Polycom Kirk)

When the internal pattern was not provided, the recorder could not work properly.

On session close, the service now checks if the session is already closed. Identification of conference packets is improved.

The Lync Filter component handled a SIP request as non-recorded one which has been already relayed on a proxy server and it lead to one way audio issue in simulring, team-call, and delegate scenarios.

SfB / Lync RGS Agent anonymity: recorded caller - RGS UCMA B2B agent call legs transferred into each other could not be matched leading to two recordings: one containing only some sec of media, other containing the rest of the call ending with timeout. UCMA B2B - agent leg was handled properly

Using mediation based recording, the ACL didn't worked correctly in some cases and led to loss of recording. It does not affect proxy based, edge based and AVMCU based recording.

Do not start recording after a transferred event, but wait for the Established event instead on conference+park events - if we parked the call, then stop the recording, but do not start a new recording. - if not we parked the call, then do nothing

Alert was not sent when RTP timeout occurred on an extension.

CDR metadata parsing fix

In multitenant environment, tenant matching was always done by BW group id, matching purely based on extension could not be set.

Player did not work with IE 10 + Compatibility Mode (because console object is undefined)

"Time of the day" filter removed from the Search panel

When the webapp looked for related calls, it may throw an error (SQLServerException: The index 6 is out of range)

Active Directory Profile's Password was logged in the Audit Log as clear text.

Call Deletion will not create backup files from now on (due to issues with WORM storage systems), instead it deletes the "main" media the last.

License problems were not sent to users who had permission to see the License screen (the emails were sent to the target email set in the Email Settings, though).

Firefox automatically filled the Valid Until and Avaya Password fields on the Extension details screen.

After playing back a call that was stored on a storage target accessible through the Storage API, the media might got deleted.

When a QA "Auto-Fail" question failed the whole scorecard, then some points were not set to zero

Ethical Wall events were counted in "# of Simultaneous Calls..." and "# of Recorded Hours Per Day..." license usage

Several report displayed time values in GMT instead of the report timezone.

Improved handling of conference data share modality.

Central Cisco Silent Monitoring: the target party was not highlighted in red and bold style.

SearchCalls API returned zero rows when status=ongoing parameter applied.

Update SQL script threw an error during an upgrade if Full-Text Search was available and the full-text index was already added to the section_chat table.

VMF header size was limited to 16kb which is too small in case of Lync video conferences with ICE and a high amount of SVC layers for many video streams. Now it is increased to 64kb. Old codec will not be able to decode new VMF and Silent monitoring

SIP stack: now the SRTP keys are properly negotiated based on the local capabilities instead of just accepting the first key offered by the remote side

Old policy based export did not provide proper path for copying media after transcoding

Export: filenames are always postfixed with some guid when rename pattern is used to make sure filenames are unique. Now if the rename pattern contains guid elements this postfix is not concatenated

Email regex pattern is changed on the email configuration page, and the installation can be continued if the email address is not standard, the installer will just warn

When media is not recorded by remote cluster's shared recorder the ongoing call in local cluster db is deleted instead of closed. That way CDR reconciliation can detect the failure if call was neither remotely nor locally recorded

When a Lync/SfB recorded user was invited into the conference on a mobile/work phone not set for recording (contact card) the CDR caller uri was filled with the recording provisioned Lync uri causing false matches in the CDR reconciliation process.

Call healing: the process could not be stopped on graceful shutdown leading to wait for processing all the previously stucked calls