Outbound SIP Call ID
This data export field displays the SIP session identifier on an outbound leg to the called party.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
UC |
|
Channels |
|
|
Size (bytes) |
258 |
|
Filter |
None |
|
Dimension |
None |
Example
This data export report shows an incoming call that was answered by an agent (first two rows) and then transferred twice (last two rows).
|
Outbound SIP Call ID |
||||
|
2018-07-19 16:43:22 |
I |
01614960654 |
|
|
|
2018-07-19 16:43:28 |
O |
iPath_129_cmilliband |
Craig Milliband |
PJjr543dSd58KiGjE4mM4MDoJue34A. |
|
2018-07-19 16:48:42 |
O |
00156527D65C |
Baz Parsons |
MjFjNDY2MDk5MGjE4mM4MDM1MTQ. |
|
2018-07-19 16:58:17 |
O |
00156531972e |
Stephen Dodd |
NTAyNTk3ZjZIyODU1NzZkMjExZTQ. |
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) |
||
|
|