Cisco Unified Intelligent Contact Management Enterprise

What Does the CallDispositionFlag Field in the Termination_Call_Detail Table Represent in the Logger Database?

Cisco - What Does the CallDispositionFlag Field in the Termination_Call_Detail Table Represent in the Logger Database?

Document ID: 43621

Updated: Aug 11, 2005



Termination_Call_Detail table only resides on the central database on the Logger. Each record contains information about how a call is handled at a peripheral. The Peripheral Gateway generates termination call detail data for each call that receives private network routing or is sent to a translation route. The CallRouter process creates a Termination Call Detail row every time it receives termination call detail data from a Peripheral Gateway. CallDisposition and CallDispositionFlag are two fields in the Termination Call Detail record.

Q. What does the CallDispositionFlag field in the Termination_Call_Detail table represent in the Logger database?

A. The CallDisposition field represents the final disposition of the call or how the call is terminated. It is provided by peripherals in the call disconnect or abandon event. Possible values are 1 through 34. For details, refer to Termination_Call_Detail table in Cisco Intelligent Contact Management (ICM) Software Database Schema. The CallDispositionFlag field is supposed to provide additional information to supplement the CallDisposition field. It is set by Open Peripheral Controller (OPC). Since no component uses this code, it is always set to 0. The CallDispositionFlag field is set to 0, as shown in the bold text in the following OPC log which represents the peripheral's delivery of a Termination_Call_Detail record to the Peripheral Gateway (PG).

16:28:01 pg2B-opc Trace: Peripheral::SendTerminationCallDetail 
  - DateTime=04/26 15:28:00 
16:28:01 pg2B-opc Trace:     Periph=5004 Day=146577 RtrCallKey=29204 
  RtrCallKeySeq#=2 PeriphCallKey=6901 PeriphCallType=2 DBCD_PREROUTE_ACD_IN 
16:28:01 pg2B-opc Trace:     ICRCallKey=2985678, ICRCallKeyParent=-1 
16:28:01 pg2B-opc Trace:     CallDisp=13,DBCD_DROP_HANDLED_PRIMARY_ROUTE 
  NetworkTime=1 Duration=451 RingTime=3 DelayTime=3 
16:28:01 pg2B-opc Trace:     TimeToAband=0 HoldTime=0 TalkTime=365 WorkTime=8 
16:28:01 pg2B-opc Trace:     BillRate=-1 SegmentTime=-1 NewTransaction=78 
16:28:01 pg2B-opc Trace:     AgentPeriphNum=4285(-5000470) 
  SkillGroupSkillTargetID=5014  (0x21) ServiceSkillTargetID=5039(244) 
16:28:01 pg2B-opc Trace:     SRCAgentPeriphNum=-1(-1) CallDispositionFlag=0 
16:28:01 pg2B-opc Trace:     DigitsDialed=35031 Var1=72405460965301327629 
16:28:01 pg2B-opc Trace:     Var3=35107 Var4= Var5=724 5460 9653 0132 7629 
  Var6=MR JOHN DOE                 
16:28:01 pg2B-opc Trace:     Var7=MBS001 Var8=AODWYER Var9= Var10= 
16:28:01 pg2B-opc Trace:     NetworkTargetID=5044 TrunkGroupID=5000 (1) 
  InstrumentPortNumber=295 DNIS=35107 UserToUser= 
16:28:01 pg2B-opc Trace:     AnsweredWithinServiceLevel=N ConferenceTime=0 
  Priority=-1 Trunk=21 
16:28:01 pg2B-opc Trace:     ANI=01756748633 WrapupData= 

Note: The above value covers multiple lines due to space limitations.

Possible values of the CallDisposition field are 1 through 52. They are listed in Table 1.

Table 1: Call Disposition

Value Explanation
1 Abandoned in network
2 Abandoned in local queue
3 Abandoned ring
4 Abandoned delay
5 Abandoned interflow
6 Abandoned agent terminal
7 Short
8 Busy
9 Forced busy
10 Disconnect/drop no answer
11 Disconnect/drop busy
12 Disconnect/drop reorder
13 Disconnect/drop handled primary route
14 Disconnect/drop handled other
15 Redirected
16 Cut through
17 Intraflow
18 Interflow
19 Ring no answer
20 Intercept reorder
21 Intercept denial
22 Timed out
23 Voice energy
24 Non-classified energy detected
25 No cut through
26 U-Abort
27 Failed aoftware
28 Blind transfer
29 Announced transfer
30 Conferenced
31 Duplicate transfer
32 Unmonitored device
33 Answering machine
34 Network blind transfer
35 Task abandoned in Router
36 Task abandoned before offered
37 Task abandoned whle offered
38 Normal end task
39 Cannot obtain task ID
40 Agent logged out during task
41 Maximum task lifetime exceeded
42 Application path went down
43 ICM routing complete
44 ICM routing disabled
45 Application invalid MRD ID
46 Application invalid dialogue ID
47 Application duplicate dialogue ID
48 Application invalid invoke ID
49 Application invalid script selector
50 Application terminate dialogue
51 Task ended during application init
52 Called party disconnected

Related Information

Updated: Aug 11, 2005
Document ID: 43621