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.
The purpose of the TAPI specification is to provide control of telephony resources to applications. This 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.
The Microsoft telephony application programming interfaces support the development of communications applications for Microsoft Windows or Windows NT. The telephony interfaces are listed in the following table.
The purpose of the TAPI specification is to provide control of telephony resources to applications. This 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.
The Microsoft telephony application programming interfaces support the development of communications applications for Microsoft Windows or Windows NT. The telephony interfaces are listed in the following table.
| Interface | Description |
|---|---|
| TAPI 2.x | A C-programming language based API that enables you to implement communications applications ranging from basic modem control to call centers with multiple agents and switches. |
| TAPI 3.x | A COM-based API that merges classic and IP telephony. |
| TSPI | A telephony service provider (TSP) is a dynamic-link library (DLL) that supports communications device control through a set of exported service functions. A TAPI application uses standardized commands, TAPI passes information to the telephony service provider, and the TSP handles the specific commands that must be exchanged with the device. |
| MSPI | A media service provider (MSP) allows an application considerable control over the media for a particular transport mechanism. An MSP is always paired with a telephony service provider (TSP). |
1:04 AM
0 Responses to "Telephony Application Programming Interface ( TAPI )"
Post a Comment