Telephony Server Application Programming Interface - Revision history

Strugglehouse: #suggestededit-add 1.0

2022-08-09T12:16:01Z

#suggestededit-add 1.0

← Previous revision		Revision as of 12:16, 9 August 2022
Line 1:		Line 1:
			{{Short description\|Computer telephony integration standard developed and promoted by Novell and AT&T}}
	'''Telephony Server Application Programming Interface''' was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface]] from [[Microsoft]] and [[Intel]], it was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, which sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.		'''Telephony Server Application Programming Interface''' was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface]] from [[Microsoft]] and [[Intel]], it was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, which sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.

Αρκάς: clean up

2019-02-10T15:38:54Z

clean up

← Previous revision		Revision as of 15:38, 10 February 2019
Line 2:		Line 2:

	==Description==		==Description==
	Telephony Server Application Programming Interface consisted of two primary parts, the [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to [[~~Business_telephone_system~~#~~Private_branch_exchange~~\|private branch exchange]] driver was known as "NetWare Telephony Services", at least when using Novell software.		Telephony Server Application Programming Interface consisted of two primary parts, the [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to [[Business telephone system#Private branch exchange\|private branch exchange]] driver was known as "NetWare Telephony Services", at least when using Novell software.

	Message formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side application programming interface was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]], [[UnixWare]] and [[Linux]]<ref>https://downloads.avaya.com/css/P8/documents/101014061 Installation Guide</ref>.		Message formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side application programming interface was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]], [[UnixWare]] and [[Linux]].<ref>https://downloads.avaya.com/css/P8/documents/101014061 Installation Guide</ref>

	The interface was a control protocol only, and did not send a voice data across the network for use with software-based phones. It included commands for dialing, hanging up, and other instructions. It required a channel, called a ''stream'', to be set up for all communications.		The interface was a control protocol only, and did not send a voice data across the network for use with software-based phones. It included commands for dialing, hanging up, and other instructions. It required a channel, called a ''stream'', to be set up for all communications.
Line 14:		Line 14:

	==References==		==References==
			{{Reflist}}
	* Paul Cronin, [https://ieeexplore.ieee.org/document/489712 "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996		* Paul Cronin, [https://ieeexplore.ieee.org/document/489712 "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996
	* [https://web.archive.org/web/20110727010709/http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx		* [https://web.archive.org/web/20110727010709/http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx

86.111.159.216: /* References */ fixed link

2019-02-05T18:57:37Z

References: fixed link

← Previous revision		Revision as of 18:57, 5 February 2019
Line 14:		Line 14:

	==References==		==References==
	* Paul Cronin, [~~http~~://~~www~~.~~comsoc~~.org/ci/~~private/1996/apr/cronin.html~~ "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996 ~~xx Link is dead xx~~		* Paul Cronin, [https://ieeexplore.ieee.org/document/489712 "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996
	* [https://web.archive.org/web/20110727010709/http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx		* [https://web.archive.org/web/20110727010709/http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx

86.111.159.216: /* Description */ Installation Guide

2019-02-05T10:57:33Z

Description: Installation Guide

← Previous revision		Revision as of 10:57, 5 February 2019
Line 4:		Line 4:
	Telephony Server Application Programming Interface consisted of two primary parts, the [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to [[Business_telephone_system#Private_branch_exchange\|private branch exchange]] driver was known as "NetWare Telephony Services", at least when using Novell software.		Telephony Server Application Programming Interface consisted of two primary parts, the [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to [[Business_telephone_system#Private_branch_exchange\|private branch exchange]] driver was known as "NetWare Telephony Services", at least when using Novell software.

	Message formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side application programming interface was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]] and [[~~UnixWare~~]].		Message formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side application programming interface was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]], [[UnixWare]] and [[Linux]]<ref>https://downloads.avaya.com/css/P8/documents/101014061 Installation Guide</ref>.

	The interface was a control protocol only, and did not send a voice data across the network for use with software-based phones. It included commands for dialing, hanging up, and other instructions. It required a channel, called a ''stream'', to be set up for all communications.		The interface was a control protocol only, and did not send a voice data across the network for use with software-based phones. It included commands for dialing, hanging up, and other instructions. It required a channel, called a ''stream'', to be set up for all communications.

211.24.117.118 at 08:49, 16 January 2019

2019-01-16T08:49:53Z

← Previous revision		Revision as of 08:49, 16 January 2019
Line 1:		Line 1:
	'''Telephony Server Application Programming Interface''' was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface]] from [[Microsoft]] and [[Intel]], it was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, ~~whicho~~ sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.		'''Telephony Server Application Programming Interface''' was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface]] from [[Microsoft]] and [[Intel]], it was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, which sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.

	==Description==		==Description==

Neil Hallis: Dead webpage link

2018-12-18T20:46:05Z

Dead webpage link

← Previous revision		Revision as of 20:46, 18 December 2018
Line 14:		Line 14:

	==References==		==References==
	* Paul Cronin, [http://www.comsoc.org/ci/private/1996/apr/cronin.html "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996		* Paul Cronin, [http://www.comsoc.org/ci/private/1996/apr/cronin.html "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996 xx Link is dead xx
	* [https://web.archive.org/web/20110727010709/http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx		* [https://web.archive.org/web/20110727010709/http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx

GreenC bot: Rescued 1 archive link; reformat 1 link. Wayback Medic 2.1

2018-08-02T17:32:20Z

Rescued 1 archive link; reformat 1 link. Wayback Medic 2.1

← Previous revision		Revision as of 17:32, 2 August 2018
Line 15:		Line 15:
	==References==		==References==
	* Paul Cronin, [http://www.comsoc.org/ci/private/1996/apr/cronin.html "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996		* Paul Cronin, [http://www.comsoc.org/ci/private/1996/apr/cronin.html "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996
	* [http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"]~~{{Dead link\|date=June 2018 \|bot=InternetArchiveBot \|fix-attempted=no }}~~, NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx		* [https://web.archive.org/web/20110727010709/http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx

	[[Category:Application programming interfaces]]		[[Category:Application programming interfaces]]

InternetArchiveBot: Rescuing 0 sources and tagging 1 as dead. #IABot (v2.0beta)

2018-06-15T17:13:46Z

Rescuing 0 sources and tagging 1 as dead. #IABot (v2.0beta)

← Previous revision		Revision as of 17:13, 15 June 2018
Line 15:		Line 15:
	==References==		==References==
	* Paul Cronin, [http://www.comsoc.org/ci/private/1996/apr/cronin.html "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996		* Paul Cronin, [http://www.comsoc.org/ci/private/1996/apr/cronin.html "An Introduction to TSAPI and Network Telephony"], ''IEEE Communications'', April 1996
	* [http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"], NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx		* [http://ftp.iasi.roedu.net/mirrors/rubyforge.org/files/tsapi/tsapi.pdf "Telephony Services Application Programming Interface (TSAPI)"]{{Dead link\|date=June 2018 \|bot=InternetArchiveBot \|fix-attempted=no }}, NetWare Software Developer Kit, Release 5 (or later) xx Link is dead xx

	[[Category:Application programming interfaces]]		[[Category:Application programming interfaces]]

Ira Leviton: Replaced another jargon abbreviation. WIkipedia is for general audiences, not experts in computer software.

2017-12-10T14:57:30Z

Replaced another jargon abbreviation. WIkipedia is for general audiences, not experts in computer software.

← Previous revision		Revision as of 14:57, 10 December 2017
Line 1:		Line 1:
	''Telephony Server Application Programming Interface'' was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface]] from [[Microsoft]] and [[Intel]], it was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, whicho sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.		'''Telephony Server Application Programming Interface''' was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface]] from [[Microsoft]] and [[Intel]], it was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, whicho sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.

	==Description==		==Description==
	Telephony Server Application Programming Interface consisted of two primary parts, the [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to ~~PBX~~ driver was known as "NetWare Telephony Services", at least when using Novell software.		Telephony Server Application Programming Interface consisted of two primary parts, the [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to [[Business_telephone_system#Private_branch_exchange\|private branch exchange]] driver was known as "NetWare Telephony Services", at least when using Novell software.

	Message formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side application programming interface was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]] and [[UnixWare]].		Message formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side application programming interface was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]] and [[UnixWare]].

Ira Leviton: Deleted or replaced jargon.

2017-12-10T14:54:45Z

Deleted or replaced jargon.

← Previous revision		Revision as of 14:54, 10 December 2017
Line 1:		Line 1:
	~~'''TSAPI''', short for~~ ''Telephony Server Application Programming Interface'', was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface~~\|TAPI~~]] from [[Microsoft]]/[[Intel]], ~~TSAPI~~ was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, ~~who~~ sold large telephone switches that ~~TSAPI~~ was intended to work with.		''Telephony Server Application Programming Interface'' was a [[computer telephony integration]] standard developed and promoted by [[Novell]] and [[AT&T]]. It consisted of a number of call control commands for switching calls, [[voice mail]] and call logging using [[NetWare]] servers. Unlike the competing [[Telephony Application Programming Interface]] from [[Microsoft]] and [[Intel]], it was a [[Server (computing)\|server]]-based system that did not expect client-side equipment to handle call switching. This was important to AT&T, whicho sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.

	==Description==		==Description==
	~~TSAPI~~ consisted of two primary parts, the ~~TSAPI~~ [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to ~~TSAPI~~ clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to PBX driver was known as "NetWare Telephony Services" ~~(NTS)~~, at least when using Novell software ~~from top to bottom~~.		Telephony Server Application Programming Interface consisted of two primary parts, the [[application programming interface]] itself, and a "telephony service provider" that ran on a server and talked to clients. Novell produced one such provider, "TServer" that ran, unsurprisingly, on NetWare servers. TServer, in turn, talked to a driver specific to the brand of telephony switch being used. NetWare acted primarily as the [[operating system]] for TServer to run within, although TServer did make use of [[NetWare Directory Services]] for security and provisioning. The whole system from client-side drivers to server to PBX driver was known as "NetWare Telephony Services", at least when using Novell software.

	~~The TSAPI message~~ formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the ~~TSAPI~~ server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side ~~TSAPI~~ ~~API~~ was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]] and [[UnixWare]].		Message formats were based on a standard promoted by the [[European Computer Manufacturers Association]], which was directly supported by a number of European-built switches. When used with one of these switches, the driver between the server and the switch was "thin". "Thicker" drivers were needed for switches that did not directly support these standards. The client-side application programming interface was available for [[Windows 3.1]], [[Windows 95]], [[Windows NT]], [[OS/2]], [[Mac OS]] and [[UnixWare]].

	~~TSAPI~~ is a control protocol only, it ~~does~~ not send ~~actual~~ voice data across the network for use with software-based phones. It ~~includes~~ commands for dialing, hanging up and so ~~forth~~. ~~TSAPI is a stateful protocol that~~ required a channel, ~~referred to as~~ a ''stream'', to be set up for all communications.		The interface was a control protocol only, and did not send a voice data across the network for use with software-based phones. It included commands for dialing, hanging up, and other instructions. It required a channel, called a ''stream'', to be set up for all communications.

	==~~TSAPI~~ and Versit==		==Telephony Server Application Programming Interface and Versit==
	~~TSAPI~~ ~~was~~ ~~being~~ created in an era when major telephony vendors were promoting a vision of wide-area networking based on dedicated circuit-switched links. Unlike modern networking systems where each piece of data is separately routed to its destination, these networking systems were essentially a version of the existing phone system carrying data instead of voice, setting up dedicated channels between endpoints. Looking for applications that might make use of such a network, vendors promoted numerous new standards for videotelephony, high-speed fax, etc.		Telephony Server Application Programming Interface was created in an era when major telephony vendors were promoting a vision of wide-area networking based on dedicated circuit-switched links. Unlike modern networking systems where each piece of data is separately routed to its destination, these networking systems were essentially a version of the existing phone system carrying data instead of voice, setting up dedicated channels between endpoints. Looking for applications that might make use of such a network, vendors promoted numerous new standards for videotelephony, high-speed fax, etc.

	~~TSAPI standardized only~~ the control system; getting data into and out of a computer remained an issue. There were a number of efforts by various vendors to support this functionality. [[Apple Computer]] was promoting [[GeoPort]] as the computer-end of such a system, and selected ~~TSAPI~~ as the messaging protocol. The various vendors formed the [[Versit Consortium]] and published "The Versit CTI Encyclopedia." The Encyclopedia expanded the basic ~~TSAPI~~ system to include a data-type identifier to allow it to switch any sort of "call". Additionally, Versit allowed that data to be switched to the computer using GeoPort or a number of other connection options.		Only the control system was standardized; getting data into and out of a computer remained an issue. There were a number of efforts by various vendors to support this functionality. [[Apple Computer]] was promoting [[GeoPort]] as the computer-end of such a system, and selected Telephony Server Application Programming Interface as the messaging protocol. The various vendors formed the [[Versit Consortium]] and published "The Versit CTI Encyclopedia." The Encyclopedia expanded the basic system to include a data-type identifier to allow it to switch any sort of "call". Additionally, Versit allowed that data to be switched to the computer using GeoPort or a number of other connection options.

	==References==		==References==