Introduction
Use this article to troubleshoot common issues that stop Cisco Meeting Server (CMS/Acano) CDR data from being collected by WXP Collaboration. It outlines validation steps in the WXP Collaboration Admin Portal and CMS Configuration Portal, along with connectivity and network checks to help identify and resolve CDR collection failures efficiently.
Resolution Steps
We have created this knowledge document to address common troubleshooting issues that prevent WXP Collaboration from collecting CMS CDR data. Before following these steps, please perform the following tasks:
Log in to WXP Collaboration with your administrative username and password.
From the top left corner, navigate to the admin portal
Select the Infrastructure section to view the list of your infrastructure. In this list, locate the CMS server with collection issues, then click the "edit" button (pencil icon) on the right. Step through the settings to confirm the IP address, username, and password are correct. Then click "Validate" to ensure it passes validation. If there's any validation issue, please ensure the IP address, username, and password are correct.
If the above three steps work, but you are still not getting CMR CDR data, please do the following steps:
Next, log in to your CMS Configuration Portal with your administrator credentials, then click the CDR settings tab.
Check that one of the URLs in the CDR settings tab contains the collector machine's address and specifies port 22180.
After a couple of minutes, check your CMS logs for any errors related to connecting to the data collector (IPaddr:22180). A common issue is that a port or network setting has been changed, or that the IP address of the server that is hosting the vAnalytics data collector has changed.
If you believe the URL in the CMS is correct but we are seeing issues, open a browser on the collector machine and paste the URL from the CMS CDR settings page. If you can connect to the server on port 22180, you should see an OK response in your browser.
If you do not receive the OK and are receiving an error, then open a command window and run the following command:
netstat -an | findstr 22180
From the result of the above command, you should see a 0.0.0.0:22180 in LISTENING mode. If you don't see this, verify that your data collector is running in the services panel. If it is, please reach out to WXP Collaboration support for further assistance.
If you can connect locally, try connecting to the server from another machine on the same network segment as your CMS server. You won't be able to test this on your CMS server, but if you have a Windows server, you can try it in a browser; if you have a Linux/Unix server, you can try 'curl <url-from-notepad>' and see the response.
If you are still unable to connect, you may need to contact your network team for further troubleshooting. Please reach out to WXP Collaboration support if you need further assistance.
Contact Us
For any assistance, create a support case or email support@wxp.hp.com.