Introduction

The purpose of the CTI Server C API is to provide a C language interface to the CTI Server. The steps involved in the communicating through this interface are:

• initializing
• setting the elements
• validating
• encoding
• decoding

It is important to understand that the C API is a thin wrapper by means of which a C-language CTI client application can communicate with the CTI Server. In order to create such a client application, you must understand the CTI Server and its request, confirmation, and event messages. These messages, and much else, are discussed in the CTI Server Message Reference Guide. The C-API should be considered no more than a supplement to the CTI Server Message Reference Guide.

CTI Server C-API Benefits

The C-API enables you to create CTI Applications such as

• Call Recording applications
• Wall Board Applications
• WFM realtime-adherence integrations
• CTI Bridge mode integrations

Depending on your application and the environment you are supporting, you may wish to consider using the CTIOS Server and the CTIOS Toolkit for creating integrations. Also, Cisco Advanced Services provides a realtime WFM adherence application for purchase which may save you or your customer from needing to create a new CTI Server application.

Technology/Solution Details

The CTI Server provides for integration of CTI Applications that can open a session, request a set of services, send requests and receive confirmations and asynchronous events. CTI Server is the component that delivers agent, call, and customer data in real time and enables third-party call control.

C-API Architecture

Below is a diagram that illustrates the architecture of C-API.