Disconnection Reason
This data export field indicates the reason a call leg ended.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
UC |
|
Channels |
|
|
Size (bytes) |
33 |
|
Filter |
Disconnection Reason |
|
Dimension |
None |
Possible Values
One of the following values is written to a record (communication leg):
|
Value |
The leg ended because |
|
normal |
Of normal causes |
|
transfer |
The call was transferred |
|
failed |
The call failed |
|
rejected |
The call was rejected |
|
busy |
The called party was busy |
|
no answer |
The called party did not answer |
Example
This data export report shows that the first outbound leg to user 'cmilliband' ended because the call was transferred to user 'bas'.
|
Disconnection Reason |
|||||
|
2018-07-30 17:15:18 |
I |
01344304344 |
01614960654 |
cmilliband |
normal |
|
2018-07-30 17:15:25 |
O |
01344304344 |
iPath_129_cmilliband |
cmilliband |
transfer |
|
2018-07-30 17:18:11 |
O |
01344304344 (2006) |
00156527D65C |
bas |
normal |
Detail
The data export field populates the inbound (I) and outbound (O) legs in interaction scenarios as illustrated below. See also, Communication Legs.
|
|
External |
storm |
storm user |
|
|
Deskphone LOG IN and LOG OUT |
|
|
|
|
EXTERNAL INCOMING CALL (2 legs) |
|
|
|
OUTGOING CALL dialled directly from deskphone or storm DTA Web iPath (1st leg) |
|
|
|
or OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
|
||
|
Initial called party leg (2nd leg) |
|||
|
|
|
|
TRANSFER of an INCOMING or OUTGOING CALL Transfer leg (3rd and subsequent legs) |
||
|
|
Filter
Include or exclude one or more of the values listed in the 'Possible Values' section above.