/mcpdatabase) to perform the extraction. You can index the table on the custom database according to the custom reporting needs. Related Tables • Call_Type, on page 112 (through CallTypeID) • Dialed_Number, on page 215 (through DialedNumberID) • Network_Target, on page 310 (through NetworkTargetID) • Route, on page 379 (through RouteID) • Route_Call_Variable, on page 391 (RecoveryKey maps to Route_Call_Variable.RCDRecoveryKey) • Routing_Client, on page 416 (through RoutingClientID) • Script, on page 441 (through ScriptID) • Script_Cross_Reference, on page 443 (through FinalObjectID) • Termination_Call_Detail, on page 566 (through Day + RouterCallKey) Table 330: Indexes for Route_Call_Detail Table index_keys index_description index_name RecoveryKey Primary key Note Unlike the default, this primary key is nonclustered. XPKRoute_Call_Detail DateTime Inversion key XIE1Route_Call_Detail DbDateTime Inversion key XIE2Route_Call_Detail DateTime, RouterCallKey, RouterCallKeySequenceNumber Inversion key XIE3Route_Call_Detail Table 331: Fields in Route_Call_Detail Table Keys and NULL Option Data Type Description Name NULL VNAME32 Automatic Number Identification, identifies the calling party. ANI NULL DBINT Foreign key to the Application_Gateway table and represents the instance that is selected by the Contact sharing node for this route. ApplicationGatewayID NULL DBDATETIME A new time stamp that indicates when the call entered the current CallType. BeganCallTypeDateTime Database Schema Handbook for Cisco Unified Contact Center Enterprise, Release 15.0(1) 381 All Tables Route_Call_Detail