Every call which is routed by Cisco ICM is put into the Route_Call_Detail
table (Call Detail Records CDR) of the database. The Cisco ICM software
generates a Route_Call_Detail record for every routing request it processes.
A look into this table could help you by troubleshooting routing problems of the
Cisco ICM system.
The Route_Call_Detail Table contains a lot of information of the routed calls
like: dialed number, destination label, failures, used script, caller entered
digits, ect.
See bellow a subset of fields in this table useful for troubleshooting.
(All fields can be found in the Cisco ICM database scheme handbook document at
cisco.com)
|
Fields of the Route_Call_Detail table:
ANI
automatic number identification (calling party).
CED
caller-entered digits.
DateTime
date and time call was routed.
DialedNumberString
The dialed number for the call.
|
|
|
FinalObjectID
Identifies the node ID of the last script node executed to route the call.
Label
Identifies the label that was passed to routing the call
(NULL when call is not routed).
ScriptID
foreign key from Script table.
Indicates the script which is used to route the call.
Bellow an example query to search for a specific dialed number at a specific
time and date in the Route_Call_Detail table of Cisco ICM:
SELECT
RCD.DialedNumberString as DNS,
RCD.DateTime,
RCD.ANI,
RCD.CED,
RCD.ScriptID,
RCD.FinalObjectID,
RCD.Label
FROM
hostname.dbo.Route_Call_Detail as RCD
WHERE
RCD.DialedNumberString like '%123456%' AND
(RCD.DateTime > '2008-08-19 07:00:00.000'
AND
RCD.DateTime < '2008-08-19 22:00:00.000')
ORDER BY
RCD.DateTime
When the Label field is NULL the call is not routed, this can be caused by a
problem of the mapping of the dialed number to the Label.
You can also see what the last object was in the script which have routed the
call. |
