Cisco Cisco Administrative Workstation Technische Referenzen
2-262
Cisco ICM Software Database Schema Handbook
78-11677-04
Chapter 2 Table Details
Termination_Call_Detail Table
PeripheralID
Identifies which peripheral handled the call.
This value (for example, 5002), is unique
among all peripherals in the enterprise. It is
taken from the Peripheral table in the ICM
central database. Peripheral IDs are generated
automatically when a peripheral is configured
in the Peripheral Configuration window of
Configure ICM.
This value (for example, 5002), is unique
among all peripherals in the enterprise. It is
taken from the Peripheral table in the ICM
central database. Peripheral IDs are generated
automatically when a peripheral is configured
in the Peripheral Configuration window of
Configure ICM.
smallint
FK, AK2, NOT
NULL
NULL
RouteID
Identifies 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
Route table in the ICM central database. Route
IDs are generated automatically when a route is
configured in the Route Configuration window
of Configure ICM.
value (for example, 6), is unique among all
routes in the enterprise. It is taken from the
Route table in the ICM central database. Route
IDs are generated automatically when a route is
configured in the Route Configuration window
of Configure ICM.
int
FK, NULL
RouterCallKeyDay
The day that the call was taken and the
Termination_Call_Detail record was created.
This field contains a value only for calls that
were translation-routed or post-routed to or
from an ACD.
Termination_Call_Detail record was created.
This field contains a value only for calls that
were translation-routed or post-routed to or
from an ACD.
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 specified in the
DateTime field.)
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 specified in the
DateTime field.)
Note
This field contains a value only if the
call was translation-routed, post-routed
to/from an ACD, or sent to an IPCC
agent.
call was translation-routed, post-routed
to/from an ACD, or sent to an IPCC
agent.
int
NULL
RouterCallKey
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.
forms the unique portion of the 64-bit key for
the call. The ICM resets this counter at
midnight.
Note
This field contains a value only if the
call was translation-routed, post-routed
to/from an ACD, or sent to an IPCC
agent.
call was translation-routed, post-routed
to/from an ACD, or sent to an IPCC
agent.
int
NULL
DateTime
Central Controller date and time that the
termination call detail record was written to the
database.
termination call detail record was written to the
database.
datetime
AK2, IE1, NOT
NULL
NULL
Table 2-180 Termination_Call_Detail Table (continued)
Field Name
Description
Data Type
Keys and Null
Option
Option