Cisco Cisco Computer Telephony Integration Option 8.5 개발자 가이드
5-37
CTI Server Message Reference Guide (Protocol Version 15) for Cisco Unified Contact Center Enterprise
Release 8.5(1)
Chapter 5 Application Level Interfaces
Client Events Service
AGENT_PRE_CALL_ABORT_EVENT
An AGENT_PRE_CALL_ABORT_EVENT message is generated when a call that was previously
announced via an AGENT_PRE_CALL_EVENT cannot be routed as intended (due to a busy or other
error condition detected during call routing) to Enterprise Agent. This message is defined in
announced via an AGENT_PRE_CALL_EVENT cannot be routed as intended (due to a busy or other
error condition detected during call routing) to Enterprise Agent. This message is defined in
RTP_STARTED_EVENT
The RTP_STARTED_EVENT message indicates that an RTP media stream has been started. There are
two media streams for audio media so there will be two RTP Started events, one indicating the input has
started (i.e. the phone is listening) and the other that the output has started (i.e. the outgoing media from
the agent phone has begun).
two media streams for audio media so there will be two RTP Started events, one indicating the input has
started (i.e. the phone is listening) and the other that the output has started (i.e. the outgoing media from
the agent phone has begun).
The RTP_STARTED_EVENT message will generally come up at the same time as the established event.
It also occurs when a call is retrieved from being on hold, and when the transfer or conference operations
are completed.
It also occurs when a call is retrieved from being on hold, and when the transfer or conference operations
are completed.
There is no guarantee of order of the RTP started events in relationship to the established and retrieved
events. The RTP started events may occur before or after the established event.
events. The RTP started events may occur before or after the established event.
defines the format of the RTP_STARTED_EVENT message:
Table 5-24
AGENT_PRE_CALL_ABORT_EVENT Message Format
Fixed Part
Field Name
Value
Data Type
Max.
Size
Size
MessageHeader
Standard message header. MessageType = 106.
MHDR
8
MonitorID
The Monitor ID of the device monitor that caused this
message to be sent to the client, or zero if there is no
monitor associated with the event (All Events Service).
message to be sent to the client, or zero if there is no
monitor associated with the event (All Events Service).
UINT
4
MRDID
Media Routing Domain ID as configured in Unified CCE
and the ARM client.
and the ARM client.
INT
4
Floating Part
Field Name
Value
Data Type
Max.
Size
Size
AgentInstrument
The agent instrument that the call was to have been routed
to.
to.
STRING
64
RouterCallKeyDay
Together with the RouterCall KeyCallID field forms the
unique 64-bit key for locating this call’s records in the
Unified CCE.
unique 64-bit key for locating this call’s records in the
Unified CCE.
UINT
4
RouterCallKey
CallID
CallID
The call key created by Unified CCE. Unified CCE resets
this counter at midnight.
this counter at midnight.
UINT
4
RouterCallKey
SequenceNumber
SequenceNumber
Together with RouterCallKeyDay and
RouterCallKeyCallID fields forms the TaskID
RouterCallKeyCallID fields forms the TaskID
UINT
4
Maximum message size (including header):
100