Verba Release Notes

Cisco Jabber Client User Interface integration - learn more

Mobile optimized web interface - learn more

Completed Collaboration Compliance feature set - learn more

Real time agent desktop monitoring. New Agent View page allowing supervisors to monitor real time screen activity on agent desktop computers. - learn more

Recording notifications in email (part of automatic labeling) - learn more

Media collectors can send recording streams to multiple recorders simultaneously - learn more

Compliance Store integration - Actiance Vantage (available in private beta) - learn more

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.

Cisco Fabric Path encapsulation between Cisco switches supported (https://tools.cisco.com/bugsearch/bug/CSCun74440/?referring_site=ss)

IP range based load balancing method is introduced for announcement endpoints

The proxy connection setting separator is changed from ' ' to '|', the filter can read both of them for backward compatibility.

Video forwarding to the recorder can be disabled in the RTP proxy if video is not recorded

Synway SDK update

User and Extension search filter works with all conference participants now

Delete emails from the database after 30 days (configurable)

New Roles column on User list

New monitoring permission for listing background running storage/label/speech tasks

Microsoft SQL Server Windows Authentication and Failover Partner support added to Verba Cisco IM Recorder service

Conversation detail record extended with new voicemail flag

Terminology change: Recorder Proxy is not called "Media Collector and Proxy" for clarity

NetApp SDK added for storage integration support

Installer can now grant "Service log on" right for the selected Win Auth user automatically

New Verba Announcement Server role is introduced

Direct MP3 transcoded upload for Actiance Vantage

Fixes an issue related to SIP unattended transfers when the transferred leg was not recorded, the transfer info was not saved to CDR

In some circumstances RTP events are not received so that Controlled records were not insert into the database. Now in such case the DB Service uses the other party's RTP events.

Lync filter connection statistics and counters are now referenced both by host name and IP address (earlier we tried to do host name lookup, which might result in the same host name for each filter behind DNS load-balancing)

Audiocodes phones send early media SDP offer in Ringing response instead of standard 183 Early media response, this flaw is now handled properly by our engine

Prevent multiple announcements in p2p calls, fix call drops during the announcement

Lync 2010 client doesn't receive the first message in IM conference from all participants

If Speech Analytics was enabled then the administrator was able to list Speech related data retention policies only.

Improved protection for Unvalidated Redirects and Forwards

After all recorder servers go down, when any of them come back the ongoing calls were not reassigned to the newly available recorder (if at least one remained online there is no problem). This issue was introduced by the new recorder group feature.

SDP - media negotiation fix: if peer1 offers stereo capability of an audio codec but peer2 accepts only mono capability for the same codec then the negotiated codec on peer1 is also degraded to mono as it should be.

When a storage policy contained filter for a label, then after the policy created, only the label ID was displayed.

Line ending '\n' is now replaced with '\r\n' in HTTP API calls