Technical References

Keys and Null
Option:
Data Type:Description:Field Name:
NULLvarchar(64)
Reserved for future use
FutureUseVarchar2
NULLvarchar(64)
Reserved for future use
FutureUseVarchar3
NOT NULLDBINT
The number of seconds to wait after hanging-up a port on a dialer
card before attempting to use the port again. (This option is
HangupTime
designed to give the telephone system enough time to sense a
hang-up and release the line.)
NOT NULLDBCHAR
Reserved for future use.
IPBridgingEnabled
Default = 'N'.
NULLvarchar(100)
The local area code for this dialer. (This value is compared to
numbers being dialed to determine whether '1' and the area code
should be prexed to the dialed number.)
LocalAreaCode
NULLvarchar(32)
Long distance prex - previously set in the Dialer registry.
LongDistancePrex
FK NOT NULLDBSMALLINT
The peripheral ID for the ACD.
PeripheralID
NULLvarchar(32)
Dial a prex string before the regular phone number. (This would
be used, for example, to dial a '9' to reach an external line.)
PrexDigits
NOT NULLDBCHAR
Valid options are:
TenDigitDialEnabled
Y = Aways dial the area code instead of stripping it out for local
numbers.
N = Strip out the area code for local numbers.
Dialer_Detail Table
This table is in the Blended Agent category (page 439). To see database rules for these tables,
click here (page 503).
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.
Note: If Outbound Option was not selected during setup, this table will contain no data.
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
163
Chapter 2: All Tables
Dialer_Detail Table