Reporting - Cisco Contact Center Gateway Deployments: Double counting in a Unified CCX Deployment

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (Bot: Adding {{Template:Required Metadata}})
m (1 revision)
 
(One intermediate revision not shown)
Line 1: Line 1:
-
{{Template:Required Metadata}}
 
== Double counting in a Unified CCX Deployment ==
== Double counting in a Unified CCX Deployment ==
Line 10: Line 9:
</td></tr><tr><td> '''Recommended Action''' </td><td>None. This issue occurs in all Unified CCX deployments, whether standalone or with Cisco Contact Center Gateway.  
</td></tr><tr><td> '''Recommended Action''' </td><td>None. This issue occurs in all Unified CCX deployments, whether standalone or with Cisco Contact Center Gateway.  
-
</td></tr><tr><td> '''Release''' </td><td>Release 7.5(1)</td></tr><tr><td> '''Associated CDETS&nbsp;#''' </td><td> None. </td></tr></table>
+
</td></tr><tr><td> '''Release''' </td><td>Release 7.5(1) and 8.0</td></tr><tr><td> '''Associated CDETS&nbsp;#''' </td><td> None. </td></tr></table>
[[Category:Unified ICM/CCE & Hosted, Release 7.5]]
[[Category:Unified ICM/CCE & Hosted, Release 7.5]]
 +
[[Category:Unified CCE, Release 8.0]]

Latest revision as of 23:53, 12 March 2010

Double counting in a Unified CCX Deployment

Problem Summary 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.
Error Message None. However, the report shows two calls with the same sessionID but two sessionSeqNums.
Possible 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).
Recommended Action None. This issue occurs in all Unified CCX deployments, whether standalone or with Cisco Contact Center Gateway.
Release Release 7.5(1) and 8.0
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools