Cisco Cisco Administrative Workstation User Guide

IP IVR cannot notify Unified ICM that the call abandoned because it does not yet have the call
object information. For reporting, the call is reported as an error, and a Route_Call_Detail record
is cut for the call.

None

IPIVR cannot notify Unified ICM that the call abandoned because it does not yet have the call
object information.

The call flow was that the call was translation routed to the IVR, but it did not get there. The
Router encountered a translation route time out.

None required.

Call Type reports and Overflow Out Column

Call Types reports, both real time and Historical, might seem to not peg correctly, based on the
call counts in the "flow out" column.

The reports affected are caltyp20, caltyp21, caltyp22, caltyp23, caltyp24, caltyp35, and caltyp36.

None

Overflow Out is incremented when one of the following occurs:

1. The Call Type associated with the current call is changed through use of a Call Type or

Requalify node.

2. 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.

3. 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.

Reporting Guide for Cisco Unified ICM Enterprise & Hosted Release 7.2(1)