BEGIN_CALL_EVENT
The first association between a call and a client (a route point, a CTI port, or an agent phone to which the agent has logged in) generates a BEGIN_CALL_EVENT message to the client, providing the call ID and the initial call context data. This message is optional.
The CallID identifies the call, and the ConnectionDeviceType and ConnectionDeviceID uniquely identify the client’s local call connection, if any, or another valid call connection.
This message always precedes any other event messages for that call. Subsequent changes to the call context data (if any) result in CALL_DATA_UPDATE_EVENT messages containing the changed call data being sent to the client.
Note | There can be multiple calls with the same CallID value. |
The following tables define the format of the BEGIN_CALL_EVENT message.
Fixed part Field name |
Value |
Data type |
Byte size |
---|---|---|---|
reserved |
Set this value to 0. |
UINT |
4 |
reserved |
Set this value to 1. |
UINT |
4 |
reserved |
Set this value to 21. |
USHORT |
2 |
NumCTIClients |
The number of clients previously associated with this call. This value also indicates the number of client signatures and timestamps that are present in the floating part of the message. |
USHORT |
2 |
NumNamedVariables |
The number of NamedVariable floating fields present in the floating part of the message. |
USHORT |
2 |
NumNamedArrays |
The number of NamedArray floating fields present in the floating part of the message. |
USHORT |
2 |
CallType |
The general classification of the call type. See CallType Values. |
USHORT |
2 |
ConnectionDeviceType |
The type of device ID supplied in the ConnectionDeviceID floating field. See Table 1 |
USHORT |
2 |
CallID |
The Call ID value assigned to this call by Unified CCX. |
UINT |
4 |
CalledPartyDisposition |
Indicates the disposition of the called party. See Disposition Values. |
USHORT |
2 |
Floating part Field name |
Value |
Data type |
MaxSize | ||
---|---|---|---|---|---|
ConnectionDeviceID[25] (required) |
The ID of the connection between the call and the device. In CTI Protocol Version 14, the general rules for the Primary.Actual Field Format will apply to this field. |
STRING |
64 | ||
ANI[8] (optional) |
ANI (Automatic Number Identification). The telephone number of the person making the call. In CTI Protocol Version 14, the general rules for the Primary.Actual Field Format will apply to this field. |
STRING |
40 | ||
DNIS[10] (optional) |
The DNIS (Dialed Number Identification Service) provided with the call; that is, the number associated with a call on a switch. This can be different, though often it is not, from the number the caller dialed. This is different if the call is transferred. In CTI Protocol Version 14, the general rules for the Primary.Actual Field Format will apply to this field. |
STRING |
32 | ||
DialedNumber[11] (optional) |
The telephone number dialed. In CTI Protocol Version 14, the general rules for the Primary.Actual Field Format will apply to this field. |
STRING |
40 | ||
CallerEnteredDigits[12] (optional) |
The digits entered by the caller in response to IVR prompting. |
STRING |
40 | ||
CallVariable1[13] (optional) |
Call-related variable data. |
STRING |
40 | ||
CallVariable2[14] (optional) through CallVariable9[21] (optional) |
… |
… |
… | ||
CallVariable10[22] (optional) |
Call-related variable data. |
STRING |
40 | ||
CallWrapupData[46] (optional) |
Call-related wrapup data.
|
STRING |
40 | ||
NamedVariable[82] (optional) |
Call-related variable data that has a variable name defined in the Unified CCX Editor. See NAMEDVARIABLE Data Format, for the format of this field. |
NAMEDVAR |
251 | ||
NamedArray[83] (optional) |
Call-related variable data that has an array variable name defined in the Unified CCX Editor. See NAMEDARRAY Data Format, for the format of this field.
|
NAMEDARRAY |
252 |