Cisco Cisco Computer Telephony Integration OS 8.5 Reference Guide
5-157
CTI Server Message Reference Guide (Protocol Version 14) for Cisco Unified ICM/Contact Center Enterprise & Hosted
Release 8.0(1)
Chapter 5 Application Level Interfaces
Server Service
When the request has been processed, the CTI Server responds to the CTI Client with the
BAD_CALL_CONF message:
BAD_CALL_CONF message:
Server Service
A server application specifies the new service type CTI_SERVICE_SERVER to identify itself as server
application. The server application then registers each service that it wishes to provide by sending a new
message, REGISTER_SERVICE_REQ, to the CTI Server. When a CTI client application requests a
service that is provided by a server application, such as CallRecording, the CTIServer selects a registered
server application and forwards the client request to the server application. If no server is registered for
the desired service the client request is refused with an E_CTI_NO_SERVER_FOR_REQUEST error.
application. The server application then registers each service that it wishes to provide by sending a new
message, REGISTER_SERVICE_REQ, to the CTI Server. When a CTI client application requests a
service that is provided by a server application, such as CallRecording, the CTIServer selects a registered
server application and forwards the client request to the server application. If no server is registered for
the desired service the client request is refused with an E_CTI_NO_SERVER_FOR_REQUEST error.
The server service optionally allows multiple server applications to supply the same service. The
ServerMode registration parameter determines how a server is selected to handle a given request. All
server applications that wish to provide the same service must use the same ServerMode:
ServerMode registration parameter determines how a server is selected to handle a given request. All
server applications that wish to provide the same service must use the same ServerMode:
•
Exclusive. The first server application to register the service is the only one to serve requests. All
other requests to register a server application for that service are refused with an
E_CTI_NO_SERVER_FOR_REQUEST.
other requests to register a server application for that service are refused with an
E_CTI_NO_SERVER_FOR_REQUEST.
InvokeID
An ID for this request message that will be returned in the
corresponding confirm message.
corresponding confirm message.
UINT
4
PeripheralID
The Unified ICM PeripheralID of the ACD where the call
is located.
is located.
UINT
4
ConnectionDevice
IDType
IDType
Indicates the type of the connection identifier supplied in
the Connection DeviceID floating field (
the Connection DeviceID floating field (
).
USHORT
2
ConnectionCallID
The Call ID value of the call that the agent needs to mark to
bad line call.
bad line call.
UINT
4
Floating Part
Field Name
Value
Data Type
Max.
Size
Size
Connection
DeviceID
DeviceID
The identifier of the connection between the call and the
agent’s device.
agent’s device.
STRING
64
AgentID
The AgentID.
STRING
12
Maximum message size (including header)
102
Table 5-135
BAD_CALL_REQ Message Format (continued)
Table 5-136
BAD_CALL_CONF Message Format
Field Name
Value
Data Type
Byte
Size
Size
MessageHeader
Standard message header. MessageType = 140.
MHDR
8
InvokeID
Set to the same value as the InvokeID from the
corresponding request message.
corresponding request message.
UINT
4
Maximum message size (including header)
12