 |
|
Hybrex TAPI Protocol CTI Interface
TAPI Protocol
TAPI (Telephony Applications Programming Interface) is a protocol developed by Microsoft for use with its Windows operating system
to enable integration between Windows applications and telephony devices. In this case we are talking about PBX equipment.
The protocol defines a list of commands that an application can issue to control the functions of the telephony device.
Commands for making a call, holding a call, transfering a call, and ending a call, are basic. The protocol is of course
much more extensive than that with some quite sophisticated functional control available to applications should it be required.
The TAPI protocol is standard and published so there are many Windows applications (software) that have been written for
various purposes that use it. To use TAPI requires, at minimum, the installation of a TSP (Telephony Service Provider) driver
on the PC, workstation, or server, running the TAPI enabled application, or server/client software set. The TSP is supplied by
the telephony device manufacturer and is effectively a software driver that forms the interface between the manufacturers
equipment protocols and the Microsoft Windows TAPI application programming interface (API).
Hybrex TAPI Interface
Hybrex G series systems are TAPI enabled by virtue of the Hybrex supplied software components “G2-TSP” and “T-Server”.
With Hybrex G2-TSP and T-Server software installed on the relevant network computers, network connections to the subject
Hybrex system, and some configuration and program settings made, the TAPI functionality is provided. NB: G1/E systems
may require optional serial card if not fitted.
There are two classes of this CTI integration known as First Party and Third Party. The difference is primarily in
implementation and relates to the number of users. They both produce the same end user result such as the ability
to “click to dial” from Outlook for example; or much more extensive functionality such as
screen pops for incoming calls, and more, when used in conjunction with specific third party TAPI CTI applications.
-
First Party has a user's PC connected directly to the telephony device - for example to a Hybrex GDS system via a LAN
link; or to a Hybrex G1 or G2 system via a serial connection. In this case there will be only one (concurrent) CTI user.
For this in concept only the Hyrex TSP is required. However the use of T-Server is recommended in addition, in fact T-Server
is mandatory for G1 or G2 due to the serial link required. T-Server can be run on the same PC as G2-TSP in this case.
-
Third Party has multiple users connected to a server which in turn is connected to the PBX - in the Hybrex case the server will
generally be T-Server running on a suitable PC which is then connected to the Keysystem via a serial link or LAN cable dependent
on which system is in use. The user PC's will usually also have the TSP installed.
-
There is some blurring of the above concepts however - dependant on the nature of the TAPI enabled CTI software application in use -
there are application suites that employ their own server within the suite, and therefore service many users concurrently but still
only use a First Party link between their server and the PBX. A more extensive explanation of the
definition of First and Third Party is provided at the foot of this page.
|
|
|
|
Using Hybrex TAPI - An Example :
“Click to Dial” From Microsoft Outlook
If you use a PC running Microsoft Windows 2000 or Windows XP operating system and use Microsoft Outlook you can
“Click to Dial” your contacts direct from your Outlook Contact List right now on any Hybrex G-Series system.
Whether you are a single user, or your business has multiple concurrent users, all you need is the Hybrex TSP installed
on the user PC/s, Hybrex T-Server installed on either your PC or other existing network PC, dependent on former or latter,
some cabling links, and pertinent configuration settings made. If your system is a Hybrex GDS its IP (LAN) connectivity means
the T-Server PC can be anywhere on the network, with the advantage of greater speed for connections. For G1 or G2 system the
T-Server PC needs to be close to the main equipment (less than 25ft) as the mentioned serial link is required.
Call your Hybrex dealer to enquire about supply, install and configuration, and costs involved.
NB: In all cases Hybrex DK series handsets are required to enable dial-out.
G1/E systems will require optional serial card if not fitted.
Examples of this setup are:
|
|
|
|
|
|
|
Multiple User Setup:
|
|
 |
|
What does it cost :
The installation and configuration necessary to enable TAPI functionality can be performed by your dealer at the time of system
installation. Your dealer will inform you of any additional costs involved. This installation and configuration procedure
can also be performed at any time after that, however the costs may be greater.
For those comfortable with software installation and setup : the dealers responsibility, and therefore costs, may be reduced.
For recommendations of other TAPI applications you can use - ask your Hybrex dealer, or contact us here at Hybrex Australia. |
|
|
|
|
What is the difference between First and Third Party TAPI :
First Party TAPI - This is generally a direct connection (such as a serial or LAN cable) between the workstation computer and the telephony device.
A driver (known as a TSP) must be installed and configured on the workstation. The connection (cable) carries information
about the status of the handset and call related information such as CallerID (CLI / ANI) and DDI (MSN / DNIS) from the telephony
equipment to the computer workstation and commands such as dial and hang up from the workstation to the deskset.
When a serial cable is not used there may also be a PC expansion card, USB or IP connection or even a virtual phone.
First party Tapi has the advantage of a smaller number of users with independent cost associated.
Third Party TAPI - This is generally a network connection between the workstation computer, the telephony equipment, and the server.
The advantage here is the connection can carry information about all the telephony devices connected to the telephony system.
Each workstation is assigned to the appropriate telephony device via the network configuration. A TSP driver (just like above)
is installed and configured on the workstation or server. CallerID, ANI, CLI, DDI, and DNIS is passed from the telephony system
via the network to the workstation and commands such as dial and hang up are passed from the workstation via the network to the
phone system.
For basic functionality there is no difference between Third Party and First Party TAPI (except for possibly the number of concurrent
users and aspects related to that).
The differences lie in costs involved and required hardware.
|
|
|
|
