Malicious Call?
This data export field indicates whether an incoming call was potentially malicious. This information originates from the ‘malicious call’ parameter of the SS7 message received by the storm application.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
UC |
|
Channels |
|
|
Size (bytes) |
1 |
|
Filter |
None |
|
Dimension |
None |
Possible Values
One of the following values is written to a record (communication leg):
|
Value |
Description |
|
1 |
The call was potentially malicious. |
|
0 |
A call was not potentially malicious. |
Example
This data export report shows an incoming call that was potentially malicious.
|
Malicious Call? |
|||||
|
2018-08-07 10:50:13 |
I |
07700900432 |
01614960654 |
bas |
1 |
|
2018-08-07 10:50:15 |
O |
07700900432 |
01614960654 |
|
1 |
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 |
Always 0 |
|
|
|
EXTERNAL INCOMING CALL (2 legs) |
|
|
|
OUTGOING CALL dialled directly from deskphone or storm DTA Web iPath (1st leg) |
Always 0 |
|
|
or OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
Always 0 |
||
|
Initial called party leg (2nd leg) |
|||
|
Always 0 |
|
|
TRANSFER of an INCOMING or OUTGOING CALL Transfer leg (3rd and subsequent legs) |
||||
|
|
|||||
|
Always 0 |
|
||||
Note: values of 0 are written to all communication legs of non-voice interactions.