Skip to end of metadata
Go to start of metadata
Available in version 9.2 and later

This article describes the data retention policies with the Deduplication action.

This data management action makes possible correlating 2N/dual-stream records and keeps the best quality record of the two. To determine which copy/instance is better either the voice quality result (if available) or the number of RTP packets processed counter is used. Correlation of records is based on telephony platform call id (which can be ambiguous) and record start - end time.

Currently, the following platforms/recording methods are supported:

  • Skype for Business
  • SPAN-based SIP recording
  • SPAN-based Skinny recording
  • Cisco Proxy
  • IPTrade
  • Speakerbus
  • IPC Unigy

 

Recorder server's clock must be synced, max 5 sec drift is allowed for 2N correlation

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

  • Recorder server clocks are out of sync so call start time of the two copies differ more than 5 sec
  • Length of recorded media differs more than 3 sec
  • Processed RTP counters differ more than 200 RTP packets
  • There is a midcall failover at one of the recorders. This scenario leads to violating the first 3 point/requirements for the ongoing records involved in the failover
  • Trading Turret integrations: when one recorder starts later than the other leading to start recording the ongoing calls much later than the other. This scenario leads to violating the first 3 point/requirements for those records
  • Recording is under retention

To create a Deduplication Policy, follow the steps below:

Step 1 - Follow the generic policy creation steps described on the following page: Data management policies

Step 2 - Select Deduplicate Recordings as the action

Step 3 - Select your filters to specify which conversations should be uploaded by this policy

  • No labels