Telephony Application Programming Interface - Revision history

Polluks: /* TAPI 2.x vs TAPI 3.x */ reference

2025-03-24T08:30:26Z

TAPI 2.x vs TAPI 3.x: reference

← Previous revision		Revision as of 08:30, 24 March 2025
Line 45:		Line 45:
	It is a common misconception that '''TAPI 3.0''' (or '''TAPI 3.1''') replaces '''TAPI 2.x'''.		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 (programming language)\|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 language]]s.		TAPI 2.x and earlier versions were written in [[C (programming language)\|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 language]]s.<ref>{{Citation \|last=Smith \|first=Mark \|title=markjulmar/atapi.net \|date=2025-03-24 \|url=https://github.com/markjulmar/atapi.net \|access-date=2025-03-24}}</ref>

	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 [[Visual Basic\|VB]] or other environments that provide easy access to COM but don't deal with C-style pointers.		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 [[Visual Basic\|VB]] or other environments that provide easy access to COM but don't deal with C-style pointers.

DanielRigal: Deprod. This is an API not software. It is plausibly notable.

2025-03-18T00:09:46Z

Deprod. This is an API not software. It is plausibly notable.

← Previous revision		Revision as of 00:09, 18 March 2025
Line 1:		Line 1:
	{{Proposed deletion/dated
	\|concern = Fails [[WP:NSOFT]]
	\|timestamp = 20250317192016
	\|nom = 90.167.202.192
	\|help =
	}}
	{{Short description\|Microsoft Windows API}}		{{Short description\|Microsoft Windows API}}
	The '''Telephony Application Programming Interface''' ('''TAPI''') is a [[Microsoft Windows]] [[Application programming interface\|API]], which provides [[computer telephony integration]] and enables [[personal computer\|PC]]s 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 [[Private branch exchange\|PBX]], [[ISDN]], and other telephone systems.		The '''Telephony Application Programming Interface''' ('''TAPI''') is a [[Microsoft Windows]] [[Application programming interface\|API]], which provides [[computer telephony integration]] and enables [[personal computer\|PC]]s 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 [[Private branch exchange\|PBX]], [[ISDN]], and other telephone systems.

90.167.202.192 at 19:20, 17 March 2025

2025-03-17T19:20:28Z

← Previous revision		Revision as of 19:20, 17 March 2025
Line 1:		Line 1:
			{{Proposed deletion/dated
			\|concern = Fails [[WP:NSOFT]]
			\|timestamp = 20250317192016
			\|nom = 90.167.202.192
			\|help =
			}}
	{{Short description\|Microsoft Windows API}}		{{Short description\|Microsoft Windows API}}
	The '''Telephony Application Programming Interface''' ('''TAPI''') is a [[Microsoft Windows]] [[Application programming interface\|API]], which provides [[computer telephony integration]] and enables [[personal computer\|PC]]s 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 [[Private branch exchange\|PBX]], [[ISDN]], and other telephone systems.		The '''Telephony Application Programming Interface''' ('''TAPI''') is a [[Microsoft Windows]] [[Application programming interface\|API]], which provides [[computer telephony integration]] and enables [[personal computer\|PC]]s 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 [[Private branch exchange\|PBX]], [[ISDN]], and other telephone systems.

Citation bot: Added date. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | Category:Microsoft application programming interfaces | #UCB_Category 44/133

2024-11-20T21:23:23Z

Added date. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | Category:Microsoft application programming interfaces | #UCB_Category 44/133

← Previous revision		Revision as of 21:23, 20 November 2024
Line 24:		Line 24:

	==Telephone address format==		==Telephone address format==
	TAPI uses Microsoft canonical address format for telephone numbers<ref name="MSDN_TAPI_Canonical_Address">{{cite web\| url = https://msdn.microsoft.com/en-us/library/ms726017.aspx#canonical_addresses\| title = MSDN: TAPI Applications - Device Control - Canonical Address}}</ref><ref name="TechNet_Canonical_Address">{{cite web\| url = https://technet.microsoft.com/ru-ru/library/cc772545(v=ws.10).aspx\| title = Microsoft Technet: Dialing Rules and Canonical Address Format}}</ref> to make phone calls. It is a derivative of [[E.123]] international notation.		TAPI uses Microsoft canonical address format for telephone numbers<ref name="MSDN_TAPI_Canonical_Address">{{cite web\| url = https://msdn.microsoft.com/en-us/library/ms726017.aspx#canonical_addresses\| title = MSDN: TAPI Applications - Device Control - Canonical Address\| date = 7 January 2021}}</ref><ref name="TechNet_Canonical_Address">{{cite web\| url = https://technet.microsoft.com/ru-ru/library/cc772545(v=ws.10).aspx\| title = Microsoft Technet: Dialing Rules and Canonical Address Format\| date = 2 July 2012}}</ref> to make phone calls. It is a derivative of [[E.123]] international notation.

	The canonical address is a text string with the following format: <code>+Country␣(AreaCode)␣ SubscriberNumber \| Subaddress ^ Name CRLF</code>. Area code, subaddress and name are optional; the latter can carry extension number for [[direct inward dialing]] and [[caller ID\|calling party name]], as used by [[ISDN]]/[[E-carrier\|E1]]/[[T-carrier\|T1]] telecommunication protocols.		The canonical address is a text string with the following format: <code>+Country␣(AreaCode)␣ SubscriberNumber \| Subaddress ^ Name CRLF</code>. Area code, subaddress and name are optional; the latter can carry extension number for [[direct inward dialing]] and [[caller ID\|calling party name]], as used by [[ISDN]]/[[E-carrier\|E1]]/[[T-carrier\|T1]] telecommunication protocols.

PhotographyEdits: /* TAPI compliant hardware */ fix link

2024-09-30T08:27:05Z

TAPI compliant hardware: fix link

← Previous revision		Revision as of 08:27, 30 September 2024
Line 58:		Line 58:
	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>		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-Lucent\|~~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).		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.		Third party drivers are often available for the telephone systems that don't have drivers made by the manufacturers.

Cardace: /* External links */ Fixed

2023-06-22T19:09:00Z

External links: Fixed

← Previous revision		Revision as of 19:09, 22 June 2023
Line 74:		Line 74:

	==External links==		==External links==
	* [[MSDN]] [~~http~~://~~msdn2~~.microsoft.com/en-us/~~library~~/ms950407.~~aspx~~ Library about TAPI]		* [[MSDN]] [https://learn.microsoft.com/en-us/previous-versions/ms950407(v=msdn.10)?redirectedfrom=MSDN Library about TAPI]
	* [~~http~~://www.i-b-a-m.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm Frequently Asked Questions]		* [https://www.i-b-a-m.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm Frequently Asked Questions]

	{{Microsoft APIs}}		{{Microsoft APIs}}

Kvng: thin

2022-09-14T15:10:53Z

thin

← Previous revision		Revision as of 15:10, 14 September 2022
Line 58:		Line 58:
	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>		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-Lucent\|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]]~~, Wildix~~, and [[ZyXEL]] (X6004/X2002).		Many [[Private branch exchange\|PBX]] systems provide TAPI-compliant modem interfaces. TAPI compatible PBX solutions include [[Aastra]] (400/800), [[Aastra]] (MX-ONE), [[Alcatel-Lucent\|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.		Third party drivers are often available for the telephone systems that don't have drivers made by the manufacturers.

Explicit: Removing link(s) undefined (XFDcloser)

2022-09-11T10:54:14Z

Removing link(s) undefined (XFDcloser)

← Previous revision		Revision as of 10:54, 11 September 2022
Line 58:		Line 58:
	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>		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-Lucent\|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]], [[Wildix]], and [[ZyXEL]] (X6004/X2002).		Many [[Private branch exchange\|PBX]] systems provide TAPI-compliant modem interfaces. TAPI compatible PBX solutions include [[Aastra]] (400/800), [[Aastra]] (MX-ONE), [[Alcatel-Lucent\|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]], Wildix, and [[ZyXEL]] (X6004/X2002).

	Third party drivers are often available for the telephone systems that don't have drivers made by the manufacturers.		Third party drivers are often available for the telephone systems that don't have drivers made by the manufacturers.

Kvng: caps

2022-05-21T14:17:06Z

caps

← Previous revision		Revision as of 14:17, 21 May 2022
Line 17:		Line 17:
	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.		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 [[streaming media\|media stream]] (MSP driver) involved in the connection.		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 [[streaming media\|media stream]] (MSP driver) 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.		[[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.

Citation bot: Alter: title. Add: date, website, title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 1967/2189

2022-02-19T09:01:42Z

Alter: title. Add: date, website, title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 1967/2189

← Previous revision		Revision as of 09:01, 19 February 2022
Line 51:		Line 51:
	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.		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 ([[Microsoft .NET\|.NET]] environment). As documented in Microsoft KB Article [http://support.microsoft.com/default.aspx?scid=kb;en-us;841712 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<ref>https://github.com/markjulmar/itapi3 </ref> and a 2.x wrapper for .NET.<ref>https://github.com/markjulmar/atapi.net</ref> Other developers provide libraries to work indirectly with TAPI enabled PBXs.<ref>https://sourceforge.net/projects/siptapi/</ref>		One very notable issue with TAPI 3.x is the lack of support for managed code ([[Microsoft .NET\|.NET]] environment). As documented in Microsoft KB Article [http://support.microsoft.com/default.aspx?scid=kb;en-us;841712 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<ref>{{Cite web\|url=https://github.com/markjulmar/itapi3\|title = ITAPI3 - Managed TAPI 3.0 .NET wrapper\|website = [[GitHub]]\|date = 15 March 2021}}</ref> and a 2.x wrapper for .NET.<ref>{{Cite web\|url=https://github.com/markjulmar/atapi.net\|title=ATAPI.NET - Managed library for TAPI development with .NET\|website=[[GitHub]]\|date=12 November 2021}}</ref> Other developers provide libraries to work indirectly with TAPI enabled PBXs.<ref>{{Cite web\|url=https://sourceforge.net/projects/siptapi/\|title = Siptapi}}</ref>

	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.		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.

	==TAPI compliant hardware==		==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>		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-Lucent\|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]], [[Wildix]], and [[ZyXEL]] (X6004/X2002).		Many [[Private branch exchange\|PBX]] systems provide TAPI-compliant modem interfaces. TAPI compatible PBX solutions include [[Aastra]] (400/800), [[Aastra]] (MX-ONE), [[Alcatel-Lucent\|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]], [[Wildix]], and [[ZyXEL]] (X6004/X2002).