/mcpC H A P T E R 5 Basic TAPI Implementation This chapter outlines the TAPI 2.1 functions, events, and messages that the Cisco Unified TAPI Service Provider (TSP) supports. This chapter contains functions in the following sections: • Overview, on page 143 • TAPI Line Functions, on page 143 • TAPI Line Messages, on page 199 • TAPI Line Device Structures, on page 216 • TAPI Phone Functions, on page 274 • TAPI Phone Messages, on page 290 • TAPI Phone Structures, on page 298 • Wave Functions, on page 305 Overview 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 Unified Communications Manager without specific knowledge of the communication protocols between the Unified Communications Manager and the service provider. For example, a developer could create a TAPI application that communicates with an external voice-messaging system. TAPI Line Functions The number of TAPI devices that are configured in the 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. Table 14: TAPI Line Functions Supported TAPI line functions supported lineAccept, on page 146 lineAddProvider, on page 146 lineAddToConference, on page 147 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 143
