Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Telephony Application Programming Interface
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==TAPI compliant hardware== On [[Windows]], TAPI support was almost universal in [[telephony]] hardware such as [[voice modem]]s (both internal and external) and computer expansion boards such as [[Dialogic telephony cards]]. The only notable exception who never natively supported TAPI was the Avaya Communication Manager, which relied solely on the [[TSAPI]] interface for connectivity.<ref>{{cite web| url = https://downloads.avaya.com/css/P8/documents/100141354| title = Programmer's Reference}}</ref> Many [[Private branch exchange|PBX]] systems provide TAPI-compliant modem interfaces. TAPI compatible PBX solutions include [[Aastra]] (400/800), [[Aastra]] (MX-ONE), [[Alcatel]] (OXO/OXE), [[Avaya]] (BCM, IP Office), [[Cisco]] (Call Manager), [[Ericsson-LG]] (eMG80, iPECS, ipLDK), NEC-Philips (iS3000, IPC100/500), [[NEC]] (SL1000, SV8100/9100), Nitsuko (DXE600/328), [[Panasonic]] (KX-TDA/TDE/NCP, KX-NS1000), [[Samsung]] (OfficeServ), [[Unify GmbH & Co. KG|Unify]] (3000/4000, Openscape Office), [[ShoreTel]], and [[ZyXEL]] (X6004/X2002). Third party drivers are often available for the telephone systems that don't have drivers made by the manufacturers.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)