Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide

Page of 278
5-43
CTI Server Message Reference Guide (Protocol Version 9) Release 7.0(0)
Chapter 5      Application Level Interfaces
Client Events Service
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).
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. 
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.
 defines the format of the RTP_STARTED_EVENT message:
RouterCallKey 
SequenceNumber
Together with RouterCallKeyDay 
and RouterCallKeyCallID fields 
forms the TaskID
UINT
4
Maximum message size (including header):
100
Table 5-22
AGENT_PRE_CALL_ABORT_EVENT Message Format 
Table 5-23
RTP_STARTED_EVENT Message Format 
Fixed Part
Field Name
Value
Data Type
Byte 
Size
MessageHeader
Standard message header. 
MessageType = 116.
MHDR
8
MonitorID
The Monitor ID of the device or 
call 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).
UINT
4
PeripheralID
The ICM PeripheralID of the ACD 
where the device is located.
UINT
4
ClientPort
The TCP/IP port number of the 
CTI Client connection
UINT
4
Direction
The direction of the event. One of 
the following values:
     0: Input; 
     1: Output;     
     2: Bi-directional.
USHORT
2