The Telephony Application Programming Interface (TAPI) is a Microsoft Windows API, which provides computer telephony integration and enables PCs running Microsoft Windows to use telephone services. Different versions of TAPI are available on different versions of Windows. TAPI allows applications to control telephony functions between a computer and telephone network for data, fax, and voice calls. It includes basic functions, such as dialing, answering, and hanging up a call. It also supports supplementary functions, such as hold, transfer, conference, and call park found in PBX, ISDN, and other telephone systems.
TAPI is used primarily to control either modems or, more recently, to control business telephone system (PBX) handsets. When controlling a PBX handset, the driver is provided by the manufacturer of the telephone system. Some manufacturers provide drivers that allow the control of multiple handsets. This is traditionally called "third-party control". Other manufacturers provide drivers that allow the control of a single handset. This is called "first-party control". Third-party drivers are designed to allow applications to see and/or control multiple extensions at the same time. Some telephone systems only permit one third-party connection at a time. First-party drivers are designed to allow applications to monitor and/or control one extension at a time. Telephone systems naturally permit many of these connections simultaneously. Modem connections are by nature first-party.
TAPI can also be used to control voice-enabled telephony devices, including voice modems and dedicated hardware such as Dialogic cards.
TAPI was introduced in 1993 as the result of joint development by Microsoft and Intel. The first publicly available version of TAPI was version 1.3, which was released as a patch on top of Microsoft Windows 3.1. Version 1.3 drivers were 16-bit only. Version 1.3 is no longer supported, although some MSDN development library CDs still contain the files and patches.
With Microsoft Windows 95, TAPI was integrated into the operating system. The first version on Windows 95 was TAPI 1.4. TAPI 1.4 had support for 32-bit applications.
The TAPI standard supports both connections from individual computers and LAN connections serving any number of computers.
In 1997, Microsoft released TAPI version 2.1. This version of TAPI was available as a downloadable update and was the first version to be supported on both the Microsoft Windows 95 and Windows NT/2000 platforms.
TAPI 3.0 was released in 1999 together with Windows 2000. This version enables IP telephony (VoIP) by providing simple and generic methods for making connections between two (using H.323) or more (using IP Multicast) computers and now also offers the ability to access any media streams involved in the connection.
Windows XP included both TAPI 3.1 and TAPI 2.2. TAPI 3.1 supports the Microsoft Component Object Model and provides a set of COM objects to application programmers. This version uses File Terminals which allow applications to record streaming data to a file and play this recorded data back to a stream. A USB Phone TSP (Telephony Service Provider) was also included which allows an application to control a USB phone and use it as a streaming endpoint. TAPI 3.0 or TAPI 3.1 are not available on operating systems earlier than Windows 2000 and Windows XP respectively.
The Telephony Server Application Programming Interface (TSAPI) is a similar standard developed by Novell for NetWare servers.
It is a common misconception that TAPI 3.0 (or TAPI 3.1) replaces TAPI 2.x.
TAPI 2.x and earlier versions were written in C; the API uses pointers to structures. Consequently, TAPI 2.x is easy to access from C or C++ applications, but it can be awkward to use from many other programming languages.
TAPI 3.x was designed with a Component Object Model (COM) interface. This was done with the intent of making it accessible to higher level applications such as developed in VB or other environments that provide easy access to COM but don't deal with C-style pointers.
TAPI 3.x has a slightly different set of functionality than TAPI 2.x. The addition of integrated media control was the most significant addition. But TAPI 3.x doesn't include all functionality that TAPI 2.x does, like support for the Phone class.
One very notable issue with TAPI 3.x is the lack of support for managed code (.NET environment). As documented in Microsoft KB Article 841712, Microsoft currently has no plans to support TAPI 3.x directly from .Net programming languages. However, Mark Smith has provided a Managed C++ library called ITAPI3 and other developers such as Mondago provide .Net libraries to work indirectly with TAPI enabled PBXs.
One often overlooked reason an application developer might choose between TAPI 2.x and TAPI 3.x should be the hardware vendors recommendation. Even though TAPI provides an abstract model of phone lines, telephony applications are still heavily impacted by the specific behavior of the underlying hardware. Troubleshooting behavior issues usually requires both software and hardware vendors to collaborate. Because there is almost a 1:1 relationship between the TAPI Service Provider (TSP) interface and the TAPI 2.x interface, collaboration is often easier if the application is designed using TAPI 2.x. Experience with TAPI 3.x varies significantly between hardware vendors.
The following telephone systems provide Tapi drivers. Often these are only available for 32 bit operating systems. Many of these drivers are licensed and thus incur a charge to use. In other cases, alternative drivers are available for separate purchase from iQ NetSolutions, Estos and Mondago:
|Manufacturer||Model||Manufacturer Support (32 bit)||Manufacturer Support (64 bit)||Alternative suppliers||Notes|
|3Com||NBX||Yes||-||-||Support for platform is unclear since purchased by HP|
|Aastra||800||-||-||Mondago||Based on a PBX from Detewe|
|Aastra||MX-ONE||Yes||-||New version of Ericsson MD110|
|Allworx||6x, 6x12, 10x, 24x, and 48x||Yes||Yes||-|
|Avaya||BCM||Yes||-||Mondago||Formerly Nortel BCM|
|Avaya||CS1000||-||-||Mondago||Formerly Nortel CS|
|Avaya||Index||Yes||-||-||Platform has been discontinued. Formerly SDX Index|
|Cisco||320||-||-||TAPI drivers may be possible for the handsets rather than the PBX|
|Cisco||500 / Call Manager Express||-||-||Mondago|
|LG||LDK||Yes||-||Driver uses UDP for communication. Can be sensitive to poor network conditions.|
|LG-Ericsson||iPECS||Yes||-||Driver uses UDP for communication. Can be sensitive to poor network conditions.|
|LG-Ericsson||ipLDK||Yes||-||Driver uses UDP for communication. Can be sensitive to poor network conditions.|
|Mitel||3000||-||-||Mondago||Sold as BT Versatility in the UK|
|Mitel||3250||-||-||Mondago||Sold as BT Quantum in the UK|
|Mitel||3300 ICP||-||-||Mondago, iQ NetSolutions||Mitel did have a TAPI driver until it was discontinued in 2007|
|NEC-Philips||Aspire (aka IPC500)||Yes||-|
|NEC-Philips||XN120 (aka IPC100)||Yes||-|
|Nortel||Meridian||Yes||-||Platform has been discontinued. See Avaya CS1000|
|Sipleo||Sipleo||Yes||Yes||Sipleo TAPI drivers work with all handset models. Sipleo TAPI drivers are compatible with Terminal Services.|
|Tekelec||M6||Yes||-||See Broadsoft M6|
|Way2Call||Hi-Phone Desktop Lite||Yes||Yes||Supports Windows XP, 2000, Server 2003, VISTA 32 bit and 64 bit, WIN7 32 bit and 64 bit, WIN Server 2008 R2|
|Way2Call||Hi-Phone Desktop Pro||Yes||Yes||Supports Windows XP, 2000, Server 2003, VISTA 32 bit and 64 bit, WIN7 32 bit and 64 bit, WIN Server 2008 R2|
|Way2Call||Way2Call Maestro||Yes||Yes||Supports Windows XP, 2000, Server 2003, VISTA 32 bit and 64 bit, WIN7 32 bit and 64 bit, WIN Server 2008 R2|
|Wildix||All Wildix WMS UC Series > rel. 2.0||Yes||Yes||Supports Windows XP, 2000, Server 2003, VISTA 32 bit and 64 bit, WIN7 32 bit and 64 bit, WIN8 32/64, WIN Server 2008 R2|
Here you can share your comments or contribute with more information, content, resources or links about this topic.