Clever Geek Handbook
📜 ⬆️ ⬇️

Microsoft Telephony API

TAPI ( Telephony Application Programming Interface - allows you to connect PCs running Windows to voice systems - office telephone exchanges, analog telephone channels. Thanks to this, users are able to combine voice conversations with the exchange of computer data.

TAPI Architecture

TAPI includes:

  • TAPI Dynamic Link Library - Defines the level of abstraction that separates applications from service providers. The library is loaded into the address space of the application and establishes communication via the RPC protocol with the TAPI server. Starting with version 3.0, the library also creates an object of a media service provider (MSP) and communicates with it via the MSPI interface.
  • TAPI server - monitors the communication resources available on the local machine, communicates with telephony service providers (TSP) through the TSPI interface.
  • Telephony service provider - dynamically connected libraries for managing communication devices. Run by a separate thread in the context of the TAPI server.
  • Media service provider - a set of COM objects for managing media. Virtual communication through the library and the TAPI server is used for communication between the MSP and the TSP.

History

TAPI Versions
VersionYear of issueSupported OS
1.31991Windows 3.1
1.41995Windows 95
2.01996Windows NT
2.11997Windows 2000, Windows NT, Windows 95
3.01999Windows 2000
3.12001Windows XP, Windows 2000

Links

  • Telephony API
  • What is TAPI and what is it used for?
Source - https://ru.wikipedia.org/w/index.php?title=Microsoft_Telephony_API&oldid=87115232


More articles:

  • Mitino (electrodepo)
  • Black Sea Air
  • Orekhovsky World
  • Lonely sail whitens
  • First (lake, Chelyabinsk region)
  • Plassenburg
  • Louis Barragan
  • Bulla, Victor Karlovich
  • Kustodieva Street (St. Petersburg)
  • Herzog and de Meuron

All articles

Clever Geek | 2019