Cisco Cisco Computer Telephony Integration OS 8.5 Referências técnicas

Página de 274
   
39
CTI Server Message Reference Guide (Protocol Version 17) for Cisco Unified Contact Center Enterprise
Release 10.0(1)
Client Events Service
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:
Table 5-25
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 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
RTPType
The type of the event. One of the following 
values:
     0: Audio; 
     1: Video;     
     2: Data.
USHORT
2
BitRate
The media bit rate, used for g.723 payload only. UINT
4
EchoCancellation
on/off
USHORT
2
PacketSize
In milliseconds.
UINT
4
PayloadType
The audio codec type.
USHORT
2
ConnectionDevice IDType
Indicates the type of the connection identifier 
supplied in the ConnectionDeviceID floating 
field. 
USHORT
2
ConnectionCallID
The Call ID value assigned to this call by the 
peripheral or Unified CCE.
UINT
4
Floating Part
Field Name
Value
Data Type
Max. 
Size