Network Management

CDR/CMR data are associated with the wrong Cisco Call Manager

If VNQM is assigning CDR/CMR data to the wrong device, this is caused by monitoring multiple Cisco CallManager cluster with the same name. This article provides instructions for resolving the issue.

First published date

10/19/2018 7:51 PM

Last published date

10/19/2018 7:51 PM

Overview

VNQM assigns CDR/CMR data to the wrong device.

Product section

VoIP & Network Quality Manager

Cause

The issue is caused by monitoring multiple Cisco CallManager clusters with the same name.

Resolution

All cluster names should be unique. Rename one of the clusters and restart the appropriate CallManager.

Rename Clusters

Follow the steps below to rename clusters:

Open Cisco Unified Communications Manager.
Select System > Enterprise Parameters.
Change the Cluster ID.
In VNQM, this is called "cluster name". Use a string comprising of max. 50 characters such as A-Z, a-z, 0-9.

Restart the CallManager

Follow the steps below to restart the Cisco CallManager:

Log in to Cisco Unified Serviceability on the CallManager.
Select the Tools drop down and Control Center - Feature Services.
Select CallManager/Server IP and click Go.
Under CM Services, select Cisco CallManager.
Scroll to bottom and select Restart to restart the service.
Select the Tools drop down and then Control Center - Network Services.
Select CallManager/Server IP and click Go.
Under Service Name, select Cisco RIS Data Collector.
Scroll to the bottom and select Restart to restart the service.

If it is not possible to rename your call manager clusters, create a separate folder on your FTP server so that each device with the same name has its own FTP folder. You must also edit the call manager node in VNQM to associate the device with the correct FTP folder.

For more information about adding FTP servers for call managers, consult the article VoIP & Network Quality Manager - What Do You Need to Know about Call Managers on THWACK.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.