CPM Monitoring and CPM Analytics take their data from different sources, and it is therefore possible that data may not match.
CPM Monitoring takes real-time data feeds from the endpoints and infrastructure, and reflects this in the CPM Monitoring module.
CPM Analytics takes historical data, such as call records and system configuration, and processes these for display in the CPM Analytics module.
There is there potential for mismatch when either CPM Monitoring or CPM Analytics does not receive all of the relevant data.
For example, consider a CUCM for which FTP transfers to the data collector are blocked at the network level.
In this case, CPM Monitoring may 'see' the calls via the CUCM's JTAPI interface, but CPM Analytics would not receive any call records, and therefore 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.
The general case is that both real-time and call record information must be available in order to ensure that the calls displayed in Monitoring will match those in Analytics.
There remains one further cause of apparent mis-match. 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 CPM Analytics has been subject to considerable processing, call legs are often merged in this display when they represent redundant data.