Telephony Server Application Programming Interface: Difference between revisions

Revision as of 14:57, 10 December 2017

Latest revision as of 12:16, 9 August 2022

(7 intermediate revisions by 6 users not shown)

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, whichowhich sold large telephone switches that Telephony Server Application Programming Interface was intended to work with.

==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_systemBusiness telephone system#Private_branch_exchangePrivate 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 [[UnixWareLinux]].<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.

Line 14 ⟶ 15:

==References==

{{Reflist}}

* Paul Cronin, [httphttps://wwwieeexplore.comsocieee.org/cidocument/private/1996/apr/cronin.html489712 "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

[[Category:Application programming interfaces]]