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.
Contents
Call-control (also called "client-control") messages are from client applications requesting, establishing, answering, controlling, or terminating calls on behalf of a specified agent phone and manipulating the telephony features associated with the agent’s phone.
These messages invoke a message response from the server. Consequently the messages are paired request/response messages. A request message for the desired control action is sent, and the outcome of the request is indicated by the type of response message that is received.
Depending on the specifics of the request, as much as 10 or 15 seconds might elapse before the response message is returned. A successfully executed request is indicated by the corresponding control-action confirmation message, while an unsuccessful request is indicated by a CONTROL_FAILURE_CONF message.
You can use call-control messages to do the following:
Initiate a new call.
Answer a call.
Drop a call.
Put a call on hold.
Take back a call from the hold state.
Put one call on hold and answer another call.
Drop the connection to a consult agent and reconnect to the original call.
Initiate a call transfer operation.
Initiate a conference operation.
Transmit Dual Tone Multi-Frequency (DTMF) tones, as for example, to enter a phone number or an account number.
There is no specified order to the flow of call-control messages.
Unsolicited call or agent event messages that are caused by a client request may be received before or after the request confirmation message. Figure 1 illustrates the general call-control message flow. In this example, the messages control the agent state.
Figure 1 lists the call-control messages in the Unified CCX CTI protocol. See Message Type Definitions for each message definition.