The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This reference chapter includes the following miscellaneous message constant values.
Table 1 lists the definitions of all the types of data that can appear in a Unified CCX CTI message.
Encoded using UTF-8 and can be a multi-byte or single byte (ASCII) string of length n.
|
||||
Unspecified data occupying n consecutive bytes (used only in the floating part of a message). |
||||
A date/time, expressed as the number of seconds since midnight January 1, 1970 Coordinated Universal Time (UTC). |
||||
Message header (see Table 1). |
||||
A named call context variable (see NAMEDVARIABLE Data Format). |
||||
A named call context array element (see NAMEDARRAY Data Format). |
The Unified CCX CTI message header is in what is called the Message HeaDeR (MHDR) data format. This is a common format used for message headers that precede all messages exchanged between a client and a server. The following table defines the MHDR format.
The length of the message in bytes, excluding the size of the message header (the first 8 bytes). |
|||
This identifies the type of message and has a unique numeric value used to determine the format of the remainder of the message. Table 1 defines the all the messages in the message set with a unique MessageTypeID number that identifies each message. To enter a message type into a message header, enter the MessageTypeID number specified for that message in Table 1. |
NAMEDVARIABLE data and NamedArray data are specially formatted floating data fields. There can be an arbitrary number of NamedVariable and NamedArray fields in a message, subject to a combined total limit of 2000 bytes.
The NAMEDVARIABLE data type is a call context variable that has been defined in the Unified CCX Script Editor. This variable length data type can appear in the floating part of a message and has the format defined in the following table.
For information on call context variables, see Cisco Unified Contact Center Express Scripting and Development Series: Volume 1, Getting Started with Scripts and Volume 2, Editor Step Reference at http://www.cisco.com/en/US/products/sw/custcosw/ps1846/tsd_products_support_series_home.html
There may be an arbitrary number of NamedVariable and NamedArray fields in a message, subject to a combined total limit of 2000 bytes.
The NAMEDARRAY data type is a call context variable that has been defined in the Unified CCX Script Editor. This variable length data type may appear in the floating part of a message and has the format defined in the following table.
For information on call context variables, see Cisco Unified Contact Center Express Scripting and Development Series: Volume 1, Getting Started with Scripts and Volume 2, Editor Step Reference at http://www.cisco.com/en/US/products/sw/custcosw/ps1846/tsd_products_support_series_home.html
The following table lists all the FieldDataID numeric values that identify data fields in the floating part of a Unified CCX CTI message.
Table 1 lists the DeviceTypes that can be used in a Unified CCX CTI message with their descriptions and code numeric values. Message types that contain field names ending with ...ConnectionDeviceType or ...DeviceType use the DeviceType values listed in Table 1.
The provided device ID is the ID belonging to Agent's non-ACD extension. |
The LocalConnectionState is the local end state of a connection.
Table 1 lists the local connection states that can be included in a Unified CCX CTI message with their descriptions and numeric code values.
Table 1 lists the causes of events that can be included in Unified CCX CTI messages with their numeric code values. The EventCause data field is described in CallType Fields. An example message type containing this field is the CALL_CLEARED_EVENT message.
Extended Call Cleared Event Causes |
|
Table 1 lists the system event IDs that can be included in the Unified CCX CTI SYSTEM_EVENT message, with their descriptions and numeric code values.
An Agent or Unified CCX device target has been removed from service. |
||
An EnterpriseAgent or IPCC device target has been returned to service. |
Table 1 lists the types of connecting devices that can be included in a Unified CCX CTI message with their descriptions and numeric code values.
The ConnectionDevice type value is stable over time between calls. |
||
The ConnectionDevice type value is dynamic and may change between calls. |
Table 1 lists the call types that can be included within a message with their descriptions and values.
For further information on CallType fields, see CallType Fields.
CALLTYPE_SUPERVISOR_ MONITOR |
Supervisor silently monitoring call. |
21 |
Table 1 lists the Control Failure code values that can appear in the CONTROL_FAILURE_CONF message.
Table 1 shows the numeric code values used to define sizes and limits, indicate special IDs, and unspecified data elements in Unified CCX CTI messages.
The maximum number of call devices that can be in a message list. |
||
Table 1 lists the numeric codes with their descriptions for the status of the Unified CCX. The SYSTEM_EVENT message contains the Unified CCX Status field.
Table 1 lists all the numeric call-party disposition numeric code values with their meanings that can occur in Unified CCX CTI messages.
Table 1 lists the status codes with their numeric code values that may be included in the FAILURE_CONF and FAILURE_EVENT Unified CCX CTI messages.
Table 1 lists the reason codes for agent state change, description, and their numeric code values for change in agent’s state that may be included in the AGENT_STATE_EVENT Unified CCX CTI messages.
AGT_RESERVED_OUTBOUND_DIRECT |
The Agent is reserved for a preview outbound call. |
32746 |
AGT_RESERVED_OUTBOUND |
The Agent is reserved for a progressive or predictive outbound call. |
32747 |
EMAIL_CONTACT_NOT_ACCEPTED |
Auto accept of email failed. |
32743 |
ACCX_MASTERSHIP_CHANGE |
32744 |