Versions Compared

Old Version 3

changes.mady.by.user Balázs Oláh

Saved on

compared with

New Version 4

changes.mady.by.user Balázs Oláh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Deduplication does not remove any copy in case of the following ambiguous situations:

  • The clock of the Recording Servers are out of sync, the start time of the two records differ more than 5 seconds.
  • The length of recorded media files differs for more than 3 seconds.
  • The RTP packet counters differ more than 200 RTP packets.
  • There is a mid-call failover at one of the recorders. This scenario leads to violating the first 3 requirements for the ongoing records involved in the failover.
  • For trading turret integrations, when one recorder starts later than the other leading to starting the recording of the ongoing calls later than the other. This scenario leads to violating the first 3 requirements for those records.

As of Verba

Status
colourGrey
title9.8.3.8284
the deduplication policy will skip and never process again 2N records when the records are under legal hold and/or retention. The only exception is the case when the primary record should be kept and the primary record has legal hold and/or retention, the secondary record should be deleted and the secondary record does not have legal hold or retention applied.

If you want to execute a deduplication policy on a skipped record (due to legal hold and/or retention) you need to configure a new deduplication policy to do so.

...

Warning

The deduplication policy does not support custom metadata or markers added by users. It means that if this information is added to the copy (primary, secondary) which will not be kept, the data will be lost.

As of Verba

Status
title9.8.3.8284
custom metadata, markers and labels will be kept, the data will not be lost. (When the primary record is to be deleted and the secondary record is to be promoted to primary the data will be copied over and kept)

...