TAPI comprises a set of classes that expose the functionality of the Cisco Unified Communications Solutions. TAPI enables developers to create customized IP telephony applications for Cisco Unified Communications Manager without specific knowledge of the communication protocols between the Cisco Unified Communications Manager and the service provider.For example, a developer could create a TAPI application that communicates with an external voice-messaging system.
Basic TAPI Implementation consists of:
- TAPI Line Functions
- TAPI Line Messages
- TAPI Line Device Structures
- TAPI Phone Functions
- TAPI Phone Messages
- TAPI Phone Structures
- Wave Functions
TAPI Line Functions
The number of TAPI devices that are configured in the Cisco Unified Communications Manager determines the number of available lines. Cisco Media Driver is used to terminate a media stream in the first-party call control models.
TAPI Line Messages
This section describes the line messages that the Cisco Unified TSP supports. These messages notify the application of asynchronous eventssuch as a new call arriving in the Cisco Unified Communications Manager. The messages get sent to the application by the method that the application specifies in lineInitializeEx
TAPI Line Device Structures
The following table lists the TAPI line device structures that the Cisco Unified TSP supports. This section lists the possible values for the structure members as set by the TSP, and provides a cross reference to the functions that use them. If the value of a structure member is device, line, or call specific, the system notes the value for each condition.
TAPI Phone Functions
TAPI phone functions enable an application to control physical aspects of a phone
TAPI Phone Messages
Messages notify the application of asynchronous events. All messages get sent to the application through the message notification mechanism that the application specified in lineInitializeEx. The message always contains a handle to the relevant object (phone, line, or call), of which the application can determine the type from the message type. The following table describes TAPI Phone messages.
The AVAudio32.dll implements the wave interfaces to the Cisco wave drivers. The system supports all APIs for input and output waveform devices.Cisco TSP8.0 includes Cisco Media Driver, a new and innovative way for TAPI-based applications, to provide media interaction. Cisco TSP 8.0(1) includes support for Cisco Media Driver and Cisco Wave Driver. Only one driver is active at any given time.
For detailed information on Basic Cisco TAPI Implementation, follow document: