1 | Introduction

1.1 | General

The product HiPath TAPI 120 V2.0 consists of the following software components:

• | HiPath TAPI 120 TAPI Service Provider (TSP) HiPath TAPI 120 TSP is a first party telephony provider software based on MS Windows TAPI functionality and is always deployed on client PCs. HiPath TAPI 120 TSP enables TAPI-based applications to have the control and status / presence display of telephones connected to a communication system. To enable this, HiPath TAPI 120 communicates with the communication system directly via LAN and CSTA III protocols.

• | CSTA Message Dispatcher CMD Per client, HiPath TAPI 120 occupies one CSTA link on the communication system. If there are insufficient CSTA links on a communication system to connect all clients, you can use CSTA Message Dispatcher (CMD) component. The CMD SW-component merges the CSTA links of multiple TAPI 120 TSP applications on one CSTA link on the communication system.

Documentation

• | To improve readability, "telecommunications system(s)" has been abbreviated to "communication system(s)" or "system(s)" in this document.

• | The product name HiPath TAPI 120 V2.0 has also been abbreviated to TAPI 120 for the same reason.

• | All described operation sequences and dialogs refer to older Windows versions. With using newer Windows versions you have to activate the functions accordingly.

Solutions

TAPI 120 can be used as standalone software with a system / server or can be purchased and used in conjunction with several systems / servers. Basic operation is identical:

• | HiPath 500

• | HiPath OpenOffice EE

• | HiPath 2000

• | HiPath 3000

• | OpenScape Office

Alternatively the system connection can be established using CMD

Configuration example: TAPI 120 direct connection

In a direct connection, the CTI client PC communicates directly with HiPath TAPI 120 TSP via the communication system using Ethernet LAN and CSTA protocols. The number of CTI client PCs that can be connected with TAPI 120 is equal to the number of free CSTA links available on the system.
In a direct connection, the CTI client PC communicates directly using HiPath TAPI 120 TSP with the communication system via Ethernet LAN and CSTA protocols. The number of CTI client PCs that can be connected with TAPI 120 is equal to the number of free CSTA links available on the communication system.
In a direct connection of TAPI 120 with the OpenScape Office system every CSTA link TAPI 120 is using requires a single licence.

Configuration example: TAPI 120 connection via CMD

In a connection via CMD, the TAPI 120 client PC communicates using TSP with the PC where the CMD is installed via Ethernet LAN and CSTA protocols. The CMD multiplexes the CSTA CTI links on individual TSP systems using a separate CSTA CTI link to the communication system (here: OpenScape Office).

License monitoring

If TAPI 120 is operating with CMD licenses are monitored for the access of TAPI 120 to the CSTA-interface of the CMD. License administration is located in the CMD.

Connecting TAPI 120 to the system OpenScape Office via CMD requires only one CSTA-licence.

Features

The following features are available:

• | outgoing connection setup

• | incoming call acceptance

• | dropping of calls

• | display of call state, display of caller id, display of caller name (internal calls)

• | logging of calls

• | call pickup (group)

• | consultation hold

• | toggling between calls

• | call transfer, speed extend, call park / hold

• | conference

• | call forwarding, do not disturb

• | additional information for redirected calls

• | data exchange between TAPI applications

TAPI application: Example

The easiest way to work with TAPI is to use the default Windows application Dialer. It is possible to start outgoing calls with this application.