Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide
C H A P T E R
4-1
CTI Server Message Reference Guide (Protocol Version 15) for Cisco Unified Contact Center Enterprise
Release 8.5(1)
4
Session Management
This chapter describes how CTI Server initiates and maintains TCP connections and CTI Server
sessions. It discusses the following topics:
sessions. It discusses the following topics:
•
Configuring TCP/IP transport services
•
Establishing and maintaining a TCP connection
•
Initializing, maintaining, and terminating a CTI Server session, and the CTI Server messages related
to these tasks
to these tasks
Configuring TCP/IP Transport Services
TCP/IP transport services are used in CTI client/server communications. From the Windows Socket
interface, enable the TCP “linger” option and set it to zero to close TCP connections immediately upon
request without waiting for previously transmitted data to be acknowledged. This ensures that
communications can be re-established quickly after a failure.
interface, enable the TCP “linger” option and set it to zero to close TCP connections immediately upon
request without waiting for previously transmitted data to be acknowledged. This ensures that
communications can be re-established quickly after a failure.
If possible, disable the Nagle transmit delay algorithm of TCP to ensure timely delivery of all data.
(Disabling the Nagle algorithm is sometimes referred to as the TCP_NODELAY option.) Disabling this
algorithm ensures that messages are always transmitted immediately upon request.
(Disabling the Nagle algorithm is sometimes referred to as the TCP_NODELAY option.) Disabling this
algorithm ensures that messages are always transmitted immediately upon request.
Connection Management
You should configure the CTI clients with two sets of hostname/port number pairs; one for the IP address
and TCP port number of the CTI Server on side “A” and the other for the corresponding CTI Server on
side “B”. The CTI clients should alternately attempt to connect to each side until a connection is
established. Once a connection between the CTI client and the CTI Server has been established, the
connection remains in place until a failure occurs or the client closes the connection. Connection failures
may be detected by the TCP layer or by the heartbeat message mechanism described later in this chapter.
If a failure occurs, the CTI client should again alternately attempt to establish a connection to either side
until a new connection is established.
and TCP port number of the CTI Server on side “A” and the other for the corresponding CTI Server on
side “B”. The CTI clients should alternately attempt to connect to each side until a connection is
established. Once a connection between the CTI client and the CTI Server has been established, the
connection remains in place until a failure occurs or the client closes the connection. Connection failures
may be detected by the TCP layer or by the heartbeat message mechanism described later in this chapter.
If a failure occurs, the CTI client should again alternately attempt to establish a connection to either side
until a new connection is established.