Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

To enable the collection and reconciliation of Microsoft Teams CDRs, you need to create a Microsoft Teams CDR import source and a Data Import data management policy.

Configuration steps

Follow the steps below to configure CDR reconciliation:

  1. Create an app registration in Azure with the following permissions:

    1. CallRecords.Read.All

    2. Directory.Read.All

    3. User.Read.All

  2. Enable the Verba Import Service on one of your Verba servers. We recommend running the service on servers with the Media Repository role

  3. Create an import source:

    1. In the Verba web application, go to Data and select Import sources.

    2. Select Add New Import Source.

    3. Enter a name for the import source.

    4. For Type, select Microsoft Teams CDR.

    5. Configure the required information under Settings. See Import Source Configuration reference for more information.

    6. Click Save.

  4. Create a data management policy:

    1. In the Verba web application, go to Data and select Data Management Policies.

    2. Select Add New Data Management Policy.

    3. For Action, select Data Import.

    4. Under Available Import Sources, select the import source created in steps 2a-2f, and select Add.

    5. Configure the required parameters for the data management policy. See Data Import Policy Configuration reference for more information.

    6. Under Scheduling, configure how frequently the CDR reconciliation should run.

    7. Click Save.

Import Source Configuration reference

Configuration parameter name

Description

Application (client) ID

The unique ID of the app registration created in step 1 of the configuration process.

Directory (tenant) ID

The Azure Directory ID or Tenant ID of the app registration created in step 1 of the configuration process.

Client Secret

The secret of the app registration created in step 1 of the configuration process.

TLS Certificate File / Thumbprint

The certificate file / certificate thumbprint that is being used for the Microsoft Graph API connection. If left empty, the service uses the Verba default certificate.

TLS Key File

The file where the certificate key is stored if not in the Windows Certificate Store.

TLS Key Password

The password for the file that contains the certificate keys.

TLS Trust List

The list of certificates that Verba trusts from a 3rd-party connection. Available options:

  • .pem file with a list of certificates

  • comma separated certificate thumbprints

  • comma separated CA thumbprints

Data Import Policy Configuration reference

Configuration Parameter Name

Description

Enable Recording Rules

Specifies if all data should be processed in the imported data set or just the records of the recorded users as configured in Verba.

Enable CDR Reconciliation

Enables the reconciliation process on the imported CDRs.

Mandatory.

SIP URI Modification

This setting controls how the system should transform the SIP URI found in the CDRs. It has to be in line with the settings used for the recorder services.

Send Alerts for Not Recorded Calls

If enabled, the service will send alerts if it detects not recorded conversations. The system alert message contains a summary of the number of not recorded conversations. It is useful if the administrators want to be notified of these errors. For standard users, you should use the built-in reporting option or the standard search page.

Alerts Threshold [sec]

The time delay that specifies how often the system sends alerts, in seconds.

Database Connection Retry Period [msec]

The frequency of connection attempts to the CDR database, in milliseconds.

Media Length Check Threshold [sec]

The service compares the length of the media files to the duration of the conversations (based on the information available in the database) only for conversation where the media is longer than this value in seconds.

Media Length Mismatch Threshold [%]

Defines a percentage value used in considering media length mismatch if the length difference is greater than this value. For instance, if the difference is greater than 3%, the system will mark the conversation with media length mismatch error.

Ignore Calls Shorter Than [sec]

Calls that were shorter than the defined duration are not processed by the policy.

Execute Only on Selected Servers

If enabled, only specific servers run this policy.

Limitations

  • The reconciliation process runs with a delay of at least 4-6 hours due to data validation processes.

  • In Hold and Resume call scenarios, the CDR reconciliation process does not require all segments to be successfully validated to consider the recording successful. This also means that the reconciliation process cannot detect if the recordings of some segments are missing if at least one segment has been successfully validated.

  • CDR reconciliation in call forwarding, transfer, and queue scenarios is only available for the calling and final answering parties, not the original dialled (forwarding) party.

  • CDR reconciliation does not happen when a call is answered by voicemail.

  • Modality changes cannot be accurately detected.

  • Ad hoc and On Demand recording is not supported for CDR reconciliation.

  • In call segmentation scenarios, CDR reconciliation does not require all segments to be successfully validated to consider the recording successful.

  • Teams-specific advanced and selective recording rules cannot be evaluated for CDR reconciliation.

  • No labels