Cisco Cisco Unified Contact Center Enterprise 9.0(2) Guida All'Installazione

Pagina di 97
Double counting in a Unified CCX Deployment
Symptom:
A call is placed to a route point, a script executes the Call Redirect step, and sends the call to
another route point. The report, instead of showing one inbound call, displays two separate
inbound calls.
Message:
None. However, the report will show two calls with the same sessionID but two sessionSeqNums.
Cause:
A Unified CCX script using the Call Redirect step to send the call to the second route point.
Using the Call Redirect step in a Unified CCX script causes calls to be double-counted in reports.
This happens because the Redirect step internally creates two contacts (one for the initial inbound
call and the second for the Redirect step, which are counted as two separate inbound calls).
Action:
None. This issue occurs in all Unified CCX deployments, whether standalone or with IPCC
Gateway.
Data elements do not match
Symptom:
ACD database item yyy does not match the Unified ICME Schema element yyy.
Message:
None.
Cause:
You are probably trying to match unlike data elements when comparing Unified ICME and
ACD data. If you attempt to match unlike elements from the Unified ICME and ACD, you will
see discrepancies in the reporting data.
Action:
Determine exactly which database table you are attempting to compare. This will help to ensure
that the comparison is matching like elements.
Some report columns are blank
Symptom:
Cisco IPCC Gateway Deployment Guide for Unified ICME, Unified CCE, and Unified CCX, Enterprise Releases 7.2(1) and Express Release 5.0(1)
84
Chapter 4: - Understanding Reporting in an IPCC Gateway Deployment
Troubleshooting Reports in IPCC Gateway Deployments