Introduction
This article explains why Tech Insights Monitoring and Tech Insights Analytics can display different call data, based on their distinct data sources, collection methods, and processing logic.
Causes for Data Mismatch
Tech Insights Monitoring and Tech Insights Analytics use different data sources, so the data may not match.
Tech Insights Monitoring takes real-time data feeds from endpoints and infrastructure and reflects them in the Tech Insights Monitoring module.
Tech Insights Analytics takes historical data, such as call records and system configuration, and processes these for display in the Tech Insights Analytics module.
There is potential for a mismatch if either Tech Insights Monitoring or Tech Insights Analytics does not receive all relevant data.
For example, consider a CUCM for which FTP transfers to the data collector are blocked at the network level.
In this case, Tech Insights Monitoring may 'see' the calls via the CUCM's JTAPI interface, but Tech Insights Analytics would not receive any call records, and therefore would not display any analytical data for those calls.
Similarly, if it were not possible to contact the Call Manager service on the CUCM, but the CDR records were successfully delivered, then Monitoring may not show a call that Analytics does.
In general, both real-time and call record information must be available to ensure that the calls displayed in Monitoring match those in Analytics.
There remains one further cause of apparent mismatch. Because of the nature of the real-time data, it is possible that individual call legs associated with a call may display separately. Since the data displayed in Tech Insights Analytics has been subject to considerable processing, call legs are often merged in this display when they represent redundant data.
Contact Us
For any assistance, create a support case or email support@wxp.hp.com.