INS supports several phone systems through their
own TSP (Telephony Service Provider) implementations. INS works with any PABX
TSP that provides "wave/in" and "wave/out" devices.
Please click here for an overview how to send SMS through INS.
Please click here for more information on using INS with a voice board.
Please click here for more information on using INS with VoIP.
As a sample here is how to directly accessing the Cisco TSP (Telephony Service Provider)
The Cisco (www.cisco.com) TSP solution uses the Cisco CallManager software to allow you to access the installed extensions as TAPI devices. With this you can use our INS IVR Software with any extension configured on your Cisco System.
=> More Information about the Cisco TSP.
The TSP (Telephony Service Provider) is shipped with the CallManager.
The formats supported by the TAPI Wave Driver are 16-bit PCM at 8000Hz, 8-bit ulaw at 8000Hz, and 8-bit alaw at 8000Hz.
You can only play/record wave files on Cisco CallManager "CTI Ports". Route points and station lines do not support "wave/in" and "wave/out". You can run the Cisco soft phone application to test that your audio is working correctly. Make sure to create CTI ports in Cisco's administration software, assign them a unique extension and create the associate to the user who who has the TSP installed.
NOTE: You must have the proper version of your TSP client software to match your version of CallManager. If you upgraded to version 3.1, then you must upgrade your TAPI TSP. In addition, if you get a newer version of the TSP, it will not work with older versions of CallManager.
Further PABX manufacturers (among others) that provide TAPI compliant TSP are:
The software requires a 3Com NBX solution
with R3.0 or later system software.
The 3Com® NBX® WAV Application Licenses supports TAPI as well as WAV.
|Aastra||Search for TAPI on their website.|
Alcatel-Lucent OmniDesktop TAPI Premium Server
|Altigen||AltiGen supports TAPI 2.1 and MAPI 1.0. Since AltiWare™ provides a TAPI service provider, third-party applications written to this Microsoft specification can be integrated into the AltiServ™ environment and run in the same Telecom Server.|
|Avaya (Network Alchemy)||
Avaya IP Office / Network Alchemy
|Comdial||Search for TAPI on their website.|
Business Phone 250 series. TAPI is available as 3rd party only via
BusinessLink for Windows.
Please search for Business link on their website.
|GoldStar ( LG Electronics)||GoldStar key systems support a 1st Party TAPI TSP. Support is provided by your local LG/GoldStar dealer.|
|Inter-Tel (Mitel)||Search for TAPI on their website.|
|Iwatsu (ADIX)||Search for TAPI on their website.|
|NEC||Search for TAPI on their website.|
|Nortel (Meridian, Norstar)||
In practice, a "CTA 100" is connected to a user's local telephone extension line and then to the local computer via a serial cable. You must install the TSP software that comes with the CTA 100 so that it can communicate with TAPI and INS.
In 3rd party mode, the CTA 100 connects to one of the
extensions on the PBX and the CTA 100 is connected to a telephony server
(any Windows NT Server) with it's serial cable. Then, with a license
obtained from Nortel, you install the 3rd party TSP on the server. You
may also need to purchase a user license to enable the ability for
multiple machines on the network to access this server and control lines
on the PBX. You then install the "TAPI
Remote Service Provider" that comes with windows
on each workstation that you want to connect to the server. Click on
the link form more information.
A Powerpoint presentation that tries to make the remote TSP installation easier is here: ftp://ftp.microsoft.com/developr/TAPI/remotesp.zip
In third party TSP mode, the Remote TSP software is now your driver on the local machine, which talks to the TSP running the CTA 100 on your server, which then links to your PBX through TAPI to INS. Note that many manufacturers make this much simpler by writing their own TSP's that work in first and third party modes.
In third party configuration, you would install Tapi Service Provider Direct Connect on a WinNT/Win2K server. The server connects to a Meridian 1 an Ethernet network connection and the TCP/IP protocol. You can then use Windows "TAPI Remote Service Provider" to connect to the TSP running on the server and allow call control through TAPI and INS.
Yet another option is to use a TAPI Symposium
Server. The Symposium TAPI 2.3.1 Service Provider (SP) for Meridian 1
is a multifunctional Microsoft TAPI 3.0-compliant service provider that
marries the Microsoft TAPI 3.0 Application Programming Interfaces (APIs)
to the Meridian 1. Together these products allow the telephony
capabilities of the Meridian 1 to be easily and very cost effectively
integrated with Windows-based business applications.
For more information please also visit www.nortel.com or contact your Nortel provider
|Vertical Networks (InstantOffice)||
Vertical Networks' Instant Office™ system brings voice, data, and
applications together. Their great support for the Window Telephony API
(TAPI) makes it an outstanding platform for a wide variety of CTI
Their TAPI implementation is fully integrated as both a 3rd party and 1stparty TSP. It is delivered in the Instant Office suite. Please refer to Vertical Networks TAPI information for more information.
Panasonic TAPI page
|Philips||Search for TAPI on their website.|
OfficeServ Open TSP
OfficeServ OpenTSP Driver interfaces with the Samsung key telephone system through the TCP/IP system, based on TAPI 2.x/TAPI 3.x, and enables call control and call processing of the Telephony Application Programming Interface(TAPI) service through the TSP.
|Siemens (HiCom, HiPath)||
CallBridge TU supports TAPI Versions 2.0 on Windows
NT 4.x or higher, TAPI Version 2.1 on Windows NT, Windows 95 and Windows
98 and TAPI Version 3.0 on Windows 2000. This
1st party TAPI TSP
works in conjunction with a USB cable that connects your handset to the
|Tevitel||Tevitel provides very robust support for TAPI|
|Toshiba||Search for TAPI on their website.|
Please note that some of those manufacturers may only provide a subset of the TAPI functionality (EG not support voice files all together), so you may need to check with your local support on how far their TSP supports TAPI and WAV.
Please fee free to contact us if you need any further assistance.