Data Collection Troubleshooting Checklist

Data Collection Troubleshooting Checklist for MiContact Center Business using MiVoice Business

When a system is not collecting data, please ensure the following questions are asked and answered before logging a ticket.

1. Can we ping the PBX? Telnet to ports 15373 and 1752?

• If we do not see data via telnet, it is a PBX/hardware or network issue; but if we see data in the above tests we should be able to collect it.

2. Check whether data flowing in data link in YourSite Explorer.

3. Check raw ACD/SMDR txt files.

4. Ensure the system is properly licensed (e.g. if you have several PBXs, ensure that a Network License is present) 

5. Check YSE > Servers for a server object with the correct name and IP. The name should match what you get when running the HOSTNAME command at the command prompt, and the IP should match the IP address you get from running the IPCONFIG command. (If the server has dual NICs, it must be the IP of the NIC on the voice network.)

• If there is more than one object with the correct name, rename all but one.  Normally the newest added server is the one to be renamed.
• Ensure that the hostname of the MiContact Center server is 15 characters or less.  Data collection will not start if the hostname exceeds 15 characters.

6. YSE > Servers, select the good server object, and look at its properties. There is a field named “Domain”. It must have the IP of the CCM server specified (if the server has dual NICs, it must be the IP of the NIC on the voice network.) If this is wrong, fix it (it’s a drop-down, so just select the right IP), and save changes in YSE.

7. Go to the registry, and in HKEY_LOCAL_MACHINE > Software > wowo6432node> prairieFyre software inc > CCM > Common, ensure that the ComputerName and EnterpriseIPAddress values are the same as what we have above (correct hostname, and IP on the data network if you have dual NICs). IMPORTANT: If these values are incorrect, re-run the Configuration Wizard to correct them; we do not recommend manually editing them in the registry).

8. Check YSE > Media Servers; open the properties of Media Server being investigated.

• In the General tab, ensure that the correct server object is selected (see above).
• Go to the Data Collection tab, and ensure that TCP is highlighted in orange on the left side of the lower pane.

9. Check buffereddatadirectory (in [InstallDir]\bufferdatadirectory) to ensure collector is not filing data there. If it is, then we are looking at an issue where the collector cannot connect to the enterprise.

10. Restart enterprise and collector services.  If restarting these services corrects the issue, please collect a support package.