Configuring Cisco CDR Reconciliation

For an overview of the CDR Reconciliation feature, refer to the CDR reconciliation article.

The configuration of the CDR Reconciliation was changed in Verba version 9.0. The settings need to be manually moved from the server configuration to the import policy configuration when upgrading systems from earlier releases. Before an upgrade, save your current CDR connection configuration and reimplement it in an Import policy after the upgrade. This information in earlier versions can be found in the server configuration of the Media Repository server under CDR and Archived Content Importer

Cisco-side configuration

The CUCM can be configured in a way to automatically export the contents of the CDR database to a defined SFTP storage. The Verba CDR reconciliation service imports the Cisco CDR data from this SFTP storage and compares the data found there with the data in the Verba database.

For the configuration steps, see: Configuring Cisco CAR

Configuration steps

Follow the steps below to configure CDR reconciliation:

Step 1 - Follow the instructions in the Cisco-side configuration section down below

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

Step 3 - In the Verba web interface, navigate to Data > Import Sources

Step 4 - Click on the Add New Import Source button at the top-right corner of the page

Step 5 - Define the name of the Import Source. This name identifies this source in the system

Step 6 - For the type, select Cisco IPT CDR

Step 7 - Configure the Settings section, based on the information that is shown in the Import Source Configuration Reference section down below

Step 8 - Click on the Save icon to save your settings

Step 9 - In the Verba web interface, navigate to Data > Data Management Policies

Step 10 - Click on the Add New Data Management Policy button at the top-right corner of the page

Step 11 - For the action, select Data Import

Step 12 - Under Available Import Sources, select the Import Source that you created, then click on the Add button just below the text field

Step 13 - Configure the policy details, based on the information that is shown in the Data Import Policy Configuration reference section down below

Step 14 - Set up how frequently the CDR Reconciliation should be run in the Scheduling section

Step 15 - Click on Save

Import Source Configuration reference

Configuration Parameter NameDescription
CDR Files FolderPath to where the Cisco CDR files are exported 
Store SIP URI When AvailableStore SIP URI instead of Number when available
Store Owner IDStore Owner ID instead of Number/URI when available
Import Not Established ConversationsImports not established conversations
On Completion

Defines what should happen to the files in the shared folder after Verba imported the CDRs

Delete Files - The files will be deleted from the drive

Move Files - The files can be moved to another location if a copy of them should be kept on the network drives

Move To (optional)Specify where the files should be moved after Verba has processed them. Only available if the Move Files option is selected

Data Import Policy Configuration reference

Configuration Parameter NameDescription
Enable Recording RulesSpecifies 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 ReconciliationEnables the reconciliation process on the imported CDRs
SIP URI ModificationThis 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 CallsIf 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 system will send alerts only at this frequency (max)
Database Connection Retry Period [msec]Defines the CDR database connections retry period 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]The service will ignore calls that were shorter than the defined duration
Execute Only on Selected ServersIf enabled, a specific server can be chosen that will run this policy

Service level Configuration reference

Configuration Parameter Name
Cisco CDR Column FiltersCustom filter based on Cisco CDR csv fields. If the defined field matches the specified regex then the record is skipped from processing. The config lines should be in field:regex format. Matching is case insensitive
Cisco External Device/IP CriteriaReconciliation is done only on behalf of internal Cisco phones' side. By default each party is considered internal. This might lead to false matches (on behalf of remote extension) in case of inter-cluster or specially routed calls. To make sure we check the call only on "internal" extension's behalf, here a list of regexps can be defined which describes trunk, gw names or IPs. Matching is case insensitive