HiPath TAPI 120 TSP

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.

Jump to: navigation, search

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 HiPath platform. To enable this, HiPath TAPI 120 communicates with the Communication Platform directly via LAN and CSTA III protocols.


  • First-party TAPI service provider
  • Full compatibility with the latest Microsoft TAPI 2.2/3.1 standard
  • Support for CSTA Phase III protocol
  • Connection to the Communication Platform via Ethernet LAN
  • Continuous interface monitoring to guarantee higher availability
  • Automatic release of permanently occupied resources after timeout

-> Feature description in detail

Software versions

Latest Version (effective July 2011) is:

HiPath TAPI 120 V2 R1.66.0 (released 2011-07-08)

This version supports 32-bit and 64-bit Microsoft Windows operation systems.

TAPI 120 general configuration

HiPath TAPI 120 is not server based and represents solution for use in small network topologies and which supports workgroup solutions. It can be set up in the customer LAN without interfering with the domain structure.

TAPI 120 is capable to monitor and control one single device via CSTA interface of the HiPath platform.

The CTI Link between the HiPath TAPI 120 Server PC and the HiPath platform is logically done by the CSTA III protocol. No physical connection is required between computer and phone. Communication Platform and the HiPath TAPI 120 PC are connected to an Ethernet based LAN with TCP/IP protocol.

HiPath TAPI 120 can be operated either directly connected to to the Communication Platform or via the CMD component.

TAPI 120 TAPI 120 with CMD

TAPI 120

TAPI 120 with CMD

In a direct connection, the CTI client PC communicates directly with HiPath TAPI 120 TSP via the HiPath platform 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 and available CSTA licenses available on the Communication Platform.

In a connection via CMD, the CTI client PC with TAPI 120 TSP communicates via the PC where the CMD is installed, using Ethernet LAN and CSTA protocols. The CMD multiplexes the CSTA CTI links on individual TAPI 120 TSP systems using a separate CSTA CTI link to the Communication Platform. The PC where the CMD is installed must always be reachable in the LAN for the CTI client PC.


HiPath TAPI 120 is installed on the the Client PC and is connected to the HiPath platform via Ethernet LAN. The LAN connection of the Communication Platform depends on the platform itself:

  • OpenScape Office MX via system internal LAN switch
  • OpenScape Office LX via PC Ethernet LAN interface

Operation in mixed 32 and 64-bit environment

Within a customer network different Windows operating systems can be used. The released constellations of 32 and 64-bit Windows operating systems, related to HiPath TAPI 120 V2 are shown in the tables below.

TAPI 120 TSP without CMD

Scenario PC –operating system TAPI 120 variant TAPI client application Released
1 32-bit 32-bit 32-bit yes
2 64-bit 64-bit 32-bit yes
3 64-bit 64-bit 64-bit yes

Explanations: A TAPI client PC with 64-bit operating system can operate either 32-bit or 64-bit TAPI applications (e.g. scenario 2 and 3)

TAPI 120 TSP with CMD

Scenario CMD PC operating system CMD variant TAPI 120 PC operating system TAPI 120 variant TAPI Client application Released
1 32-bit 32-bit 32-bit 32-bit 32-bit yes
2 32-bit 32-bit 64-bit 64-bit 32-bit yes
3 32-bit 32-bit 64-bit 64-bit 64-bit yes
4 64-bit 64-bit 32-bit 32-bit 32-bit yes
5 64-bit 64-bit 64-bit 64-bit 32-bit yes
6 64-bit 64-bit 64-bit 64-bit 64-bit yes

Explanations: A TAPI client PC with 64-bit operating system can operate either 32-bit or 64-bit TAPI applications (e.g. scenario 5 and 6)

Prerequisites / Requirements

Platform/Phone Requirements

Supported systems

Supported phones

Not Supported phones

  • Standard H.323 phones
  • SIP Phones

PC Requirements

PC Hardware

In general the PC hardware equipment must meet the requirements of the Windows operating system.

TAPI 120 SW is not released for operation on virtual machines, even if one of the operating systems mentioned below are operated within the virtual machine.

In addition for TAPI 120 an Ethernet LAN interface is required

PC Software

PC operating systems:

  • Microsoft Windows Vista SP2 (32 & 64-bit) except Home / Home Premium Edition
  • Microsoft Windows 7 (32 & 64-bit) except Starter / Home Premium Edition
  • Microsoft Windows 2008 Server (32 & 64-bit)
  • Microsoft Windows 2008 R2 Server (64-bit)

Not supported operating systems / servers

  • Microsoft Home Server
  • Micosoft Small Business Server


The maximum number of TAPI clients connected to HiPath TAPI 120 depends on the HiPath platform and on the type of LAN connection.

Platform TAPI 120 clients direct TAPI 120 clients with CMD Remark

OpenScape Office LX/MX




The maximum value of TAPI clients per platform does not represent the max number of monitor points available within a HiPath platform.

Functional Boundary Conditions

  • Connection to the HiPath platforms is via Ethernet LAN with TCP/IP and CSTA protocols.
  • HiPath TAPI is exclusively installed on single systems.
  • Only MS Windows PCs can be operated as TAPI PCs.
  • The number of monitor points are not exclusively for HiPath TAPI 120 TSP, but are available for all connected applications. This could reduce the monitor points available for HiPath TAPI 120 considerably. The configuration level is therefore dependent on the overall installation and the expected load.
  • The load resulting from the number of messages caused by the TAPI applications can lead to delayed reaction times in a HiPath platform.
  • Use in connection with Terminal Server architecture has not been released.
  • Operation with standard H.323 or SIP phones is not released.
  • When installing CMD components on a separate PC, please note that this PC must be in operation for the duration of TAPI 120 use of all clients.


Software Delivery

HiPath TAPI 120 software is shipped on a CD labelled "HiPath TAPI 120/ 170 V2 Service Provider" which is included in serveral order positions.

For service purposes the software can also be downloaded from the Software Supply Server of the manufacturer. software patches for dedicated problem corrections can be retrieved from the Knowledge Base within the Partner Portal (Partner Portal, login required) of the manufacturer (login required). Access to the two methods mentioned above is only granted by the manufacturer to registered partners on a contractual base.


The use of HiPath TAPI 120 TSP is licensed. The TAPI 120 licenses are first checked when the CMD is deployed. The generated license keys can be used for 32 or 64-bit variant.

License free TAPI 120 Clients

Depending on the type of Communication Platform used, a certain number of TAPI 120 TSPs can be operated without a license, with the proviso that the CSTA interface on the platform is not occupied by other applications. A dedicated CSTA License is required for TAPI 120 if TAPI 120 is connected directly to OpenScape Office LX/MX or HiPath OpenOffice ME. For these Communications Platforms it is recommended to connect TAPI 120 Clients via CMD. Within this constellation only one CSTA license is required. Every TAPI 120 Client requires a TAPI 120 user license in addition.

Platform Max. No. of license-free TAPI 120 clients CSTA License required within the system

OpenScape Office LX/MX

0 (*


(* applies if connected via CMD

Reuse of existing licenses after change from 32 to 64-bit

Existing TAPI 120 user licenses can be reused after upgrade of the operating system from 32 to 64-bit. Three constellations have to be considered for the license handling

  • Installation on the same computer HW with the same MAC address.

In this case the existing license data can be reused 1:1.

  • Installation on other computer HW with the same MAC address. (in case of reuse of the network interface card)

In this case the existing license data can be reused 1:1.

  • Installation on other computer HW with different MAC address.

Within this scenario the existing license keys have to be shifted to the new MAC address and a new license string has to be generated by the Central License Server. To do so the “Rehost” function of the Central License Server has to be applied.


Migration from TAPI 120 TSP V2 32-bit to TAPI 120 TSP V2 64-bit

HiPath TAPI 120 TSP V2 64-bit is functionally backward compatible with HiPath TAPI 120 TSP V2 32-bit. In case of replacement of the 32-bit TAPI 120 TSP the deviations within the supported scenarios of TAPI 120 TSP 64-bit in combination with CMD have to be considered.

Feature description in detail

HiPath TAPI 120 software provides in general the following features of the TAPI interface:

  • Incoming / outgoing dialing from PC
  • Identification of incoming ISDN station number
  • Consultation call and Transfer
  • Alternate
  • Conference
  • Call divert
  • Call forward
  • Call accept by application
  • Call release by application
  • Unscreened transfer
  • Code-dependent functions are supported
  • Telephone monitoring (ringing states, failure, etc.)
  • Key access to the optiset/optiPoint keypad
  • Display/LED access to the optiset/optiPoint (limited to 50 active displays per system)

Deviations can occur if the underlying CSTA III Interface of the HiPath Platform does not support some features


External Links