Technical References

The ICM software generates a Termination_Call_Detail record for each call that arrives at the
peripheral.
This table can become very large. Running custom reporting queries against it while it is on the
HDS can degrade performance. To optimize performance, extract the data from the HDS into
your own custom database on a separate server (one that is not used for other ICM/IPCC
components). Use only DBDateTime (date and time of the record that was written to the HDS
database) to perform the extraction. The table on the custom database can be indexed according
to the custom reporting needs.
Related Tables
Agent (page 15) (AgentSkillTargetID maps to Agent.SkillTargetID. SourceAgentSkillTargetID
maps to Agent.SkillTargetID)
Call Type Table (page 74) (via CallTypeID)
Media Routing Domain (page 234) (via MRDomainID)
Network Target (page 238) (via NetworkTargetID)
Peripheral (page 250) (via PeripheralID)
Route (page 277) (via RouteID)
Route Call Detail (page 278) (via Day + RouterCallKey)
Service (page 325) (ServiceSkillTargetID maps to Service.SkillTargetID)
Skill Group (page 364) (SkillGroupSkillTargetID maps to Skill_Group.SkillTargetID)
Termination_Call_Variable (page 417) (RecoveryKey maps to
Termination_Call_Variable.TCDRecoveryKey)
Table 201: Indexes for Termination_Call_Detail Table
index_keysindex_descriptionindex_name
DateTime, PeripheralID, ICRCallKeyclustered, unique, unique key
located on PRIMARY
XAK2Termination_Call_Detail
DateTimenonclustered located on PRIMARYXIE1Termination_Call_Detail
DbDateTimenonclustered located on PRIMARYXIE2Termination_Call_Detail
RecoveryKeynonclustered, unique, primary key
located on PRIMARY
XPKTermination_Call_Detail
Fields in Termination_Call_Detail Table:
Keys and
Null
Option:
Data Type:Description:Field Name:
NULLvarchar(32)
The peripheral number of the agent that the call.
AgentPeripheralNumber
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
408
Chapter 2: All Tables
Termination_Call_Detail Table