Cisco Cisco Administrative Workstation Références techniques

Page de 620
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
 (AgentSkillTargetID maps to Agent.SkillTargetID. SourceAgentSkillTargetID
maps to Agent.SkillTargetID)
 (via CallTypeID)
 (via NetworkTargetID)
 (via PeripheralID)
 (via Day + RouterCallKey)
 (ServiceSkillTargetID maps to Service.SkillTargetID)
 (SkillGroupSkillTargetID maps to Skill_Group.SkillTargetID)
 (RecoveryKey maps to
Termination_Call_Variable.TCDRecoveryKey)
Table 201: Indexes for Termination_Call_Detail Table
index_keys
index_description
index_name
DateTime, PeripheralID, ICRCallKey
clustered, unique, unique key
located on PRIMARY
XAK2Termination_Call_Detail
DateTime
nonclustered located on PRIMARY
XIE1Termination_Call_Detail
DbDateTime
nonclustered located on PRIMARY
XIE2Termination_Call_Detail
RecoveryKey
nonclustered, unique, primary key
located on PRIMARY
XPKTermination_Call_Detail
Fields in Termination_Call_Detail Table:
Keys and
Null
Option:
Data Type:
Description:
Field Name:
NULL
varchar(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