Reporting - Call Type and Skill Group Reports: Call Type reports and Overflow Out Column

Revision as of 23:53, 12 March 2010 by Cchetty (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Call Type reports and Overflow Out Column

Problem Summary	Call Types reports, both real time and Historical, might seem to not peg correctly, based on the call counts in the "flow out" column.
Error Message	None
Possible Cause	Overflow Out is incremented when one of the following occurs: The Call Type associated with the current call is changed through use of a Call Type or Requalify node. The call is redirected. When a call is redirected, the PIM no longer can receive events for the call and has no way of referencing or tracking the call. For example, the call might have been redirected to a non-ICM monitored device and then returned to the switch with a different call ID. The ICM generates the termination call detail record with only the data originally tracked for the call. Calls marked as Redirected are counted as OverflowOut calls in the ICM service and route tables. The call is sent to a label using a label node. The call was not default-routed, and the label was not a ring, busy, or announcement label. The call hits a release node.
Recommended Action	Consider these conditions by which Overflow Out is incremented when you analyze the Overflow Out columns in Call Type reports.
Release	Release 7.5(1) and 8.0
Associated CDETS #	None.

Rating: 0.0/5 (0 votes cast)