Configuring Lync - SfB CDR Reconciliation
- Kiss, Mate
- Toth, Istvan
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
Configuration steps
Follow the steps below to configure CDR reconciliation:
Step 1 - 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 2 - In the Verba web interface, navigate to Data > Import Sources
Step 3 - Click on the Add New Import Source button at the top-right corner of the page
Step 4 -Â Define the name of the Import Source. This name identifies this source in the system
Step 5 -Â For the type, select Lync/SfB CDR
Step 6 - Configure the Settings section, based on the information that is shown in the Import Source Configuration Reference section down below
Step 7 - Click on the Save icon to save your settings
Step 8 - In the Verba web interface, navigate to Data > Data Management Policies
Step 9 - Click on the Add New Data Management Policy button at the top-right corner of the page
Step 10 - For the action, select Data Import
Step 11 - Under Available Import Sources, select the Import Source that you created, then click on the Add button just below the text field
Step 12 - Configure the policy details, based on the information that is shown in the Data Import Policy Configuration reference section down below
Step 13 - Set up how frequently the CDR Reconciliation should be run in the Scheduling section
Step 14 - Click on Save
Import Source Configuration reference
| Configuration Parameter Name | Description |
|---|---|
| Database Hostname | Hostname or IP address of the SfB/Lync SQL Server |
| Database Name | Name of the CDR database (RTC), e.g. LcsCDR |
| Database QoE Name | Name of the database that holds the QoE data. Default value is QoEMetrics |
| Database Login | Username for SQL authentication (Read right required only) |
| Database Password | Password for SQL authentication |
| Failover Partner | Hostname or IP address of the SQL Server mirroring failover partner |
| Database Multi-Subnet Failover | Should be enabled if multi-subnet failover is turned on in the database |
| Windows Authentication | Enables Windows authentication for the SQL Server connection, the system will use the Windows service credentials configured for the Verba CDR and Archived Content Importer Service |
| SSL Encryption | Enables SSL based SQL Server connections |
| Import not Established Conversations | Allows importing not established calls such as not answered, busy, etc. |
| Lync Version | Version of the system, the following values apply:
|
| Use QoE Metrics | QoE metrics helps to determine RTP packet utilization and discard calls where no, or just a few RTP packets were sent |
| Import Conference Participants | Data of conference participants can be collected if the meeting was hosted in the home pool where the CDR info comes from. With this option set to yes, conference participant information will be imported. |
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 |
| 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 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 |
| Skip Calls without QoE Reports | The service will ignore calls where no QoE reports can be found |
| Execute Only on Selected Servers | If enabled, a specific server can be chosen that will run this policy |