/mcpKeys and NULL Option Data Type Description Name NULL DBINT This value is created by the system software and forms the unique portion of the 64-bit key for the call. Unified CCE resets this counter at midnight. Note This field contains a value only if the call was translation-routed or sent to an Unified CCE agent. RouterCallKey NULL DBINT 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. 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.) Note This field contains a value only if the call was translation-routed, post-routed to/from an ACD, or sent to a Unified CCE Enterprise agent. RouterCallKeyDay NULL DBINT A sequence number used for ordering rows for cradle-to-grave call tracking. 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 field also exists in the Route_Call_Detail table, where it defines the order in which the route requests were created.) There are a few scenarios where the RouterCallKeySequenceNumber may not be unique for a given RouterCallKey (specifically when translation routing to a Service Controlled IVR). For example, a call plays a prompt based on the script. This call is directly routed to a release node and produces a duplicate RouterCallKeySequenceNumber. RouterCallKeySequenceNumber Database Schema Handbook for Cisco Unified Contact Center Enterprise, Release 15.0(1) 581 All Tables Termination_Call_Detail