Technical References

Keys and
Null
Option:
Data Type:Description:Field Name:
RingTime is added to the AbandonedRingTimeToHalf Skill Group and
Agent Skill Group half-hour tables when the call completes.
RingTime is also used to compute the following Route and Service
half-hour values:
DelayQAbandTimeToHalf
LongestCallDelayQTimeToHalf
LongestCallAbandTimeToHalf
FK NULLDBINT
Identies the route where the call was sent. The value (for example,
6), is unique among all routes in the enterprise. It is taken from the
RouteID
Route table in the ICM central database. Route IDs are generated
automatically when a route is congured in the Route Conguration
window of ICM Conguration Manager.
NULLDBINT
This value is created by the ICM software and forms the unique portion
of the 64-bit key for the call. The ICM resets this counter at midnight.
RouterCallKey
Note: This eld contains a value only if the call was translation-routed
or sent to an IPCC Enterprise agent.
NULLDBINT
The day that the call was taken and the Termination_Call_Detail record
was created. This eld contains a value only for calls that were
translation-routed or post-routed to or from an ACD.
RouterCallKeyDay
Together with RouterCallKey, the Day value forms a unique 64-bit key
for the call. The PG might not have this information for all calls, but if
it does, it allows you to track all states of a call between the
Route_Call_Detail and the Termination_Call_Detail tables by using
the cradle-to-grave call tracking facility. (For calls that span a day, the
day may not correspond to the day specied in the DateTime eld.)
Note: This eld contains a value only if the call was translation-routed,
post-routed to/from an ACD, or sent to an IPCC Enterprise agent.
NULLDBINT
A sequence number used for ordering rows for cradle-to-grave call
tracking.
RouterCallKeySequenceNumber
This number is a best effort to describe the order in which call legs
were created and bears no relation to the order in which calls ended.
This is not the order in which the Termination_Call_Detail records
were created. (This eld also exists in the Route_Call_Detail table,
where it denes the order in which the route requests were created.)
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
414
Chapter 2: All Tables
Termination_Call_Detail Table