HiPath TAPI 120 TSP

HiPath TAPI 120/170

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.

Features

 * 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.

Connection
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:


 * HiPath 500 via LIM only
 * HiPath OpenOffice EE via system internal LAN switch
 * HiPath 33x0 via LIM (max 400 BHCA) or HG1500
 * HiPath 35x0 via LIM (max 400 BHCA) or HG1500
 * HiPath 38x0 via LIM (max 400 BHCA) or STMI
 * HiPath OpenOffice ME via system internal LAN switch
 * 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
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
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)

Supported systems

 * HiPath 500 V7, V8
 * HiPath 2000 V2
 * HiPath OpenOffice EE V1
 * HiPath 3300/3350 V7, V8
 * HiPath 3500/3550 V7, V8
 * HiPath 3800 V7, V8
 * HiPath 5000 RSM V7
 * HiPath OpenOffice ME V1R3
 * OpenScape Office MX V2
 * OpenScape Office LX/MX V3

Supported phones

 * Analog phones
 * optiPoint 500 family based on CorNet-TS or CorNet-IP
 * optiPoint 410/420 family based on Cornet TS or IP
 * OpenStage HFA family (HFA)

Not Supported phones

 * Standard H.323 phones
 * SIP Phones

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 2000 Professional SP4 (32-bit)
 * Microsoft Windows XP Professional SP3 (32-bit)
 * 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 2000 Server (32-bit)
 * Microsoft Windows 2003 Server (32-bit)
 * 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

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

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 (SEBA, 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.

Licensing
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.

(* applies if connected via CMD

Calculation of additional user licenses
Once the number of free TAPI 120 licenses per Communication Platform is exceeded one user license should be marketed for each PC (TAPI line) that should be operated with TAPI 120 TSP. For this reason, user licenses are offered as “single step” licenses. To determine the number of licenses necessary, the number of CSTA links already occupied by other applications on the platform must be examined. This number should then be subtracted from the number of free TAPI 120 licenses per Communication Platform. All TAPI 120 users above this value should be marketed and licensed.

Example of TAPI 120 user license marketing for HiPath 3000: Initial situation: HiPath 3350 with two connected TAPI 120 clients already in place. An additional eight TAPI 120 clients (ten in total) should be operated.

1st step: License free TAPI 120 Clients for HiPath 3350 = 6 (from table)

2nd step:	Already used CSTA Links by TAPI 120 Clients = 2 3rd step:	Still free CSTA Links for TAPI 120 clients = 4 (6 - 2) 4th step	TAPI 120 user licenses which need to be marketed = 4 (8 - 4)

In this case the CMD is needed from the 6th TAPI 120 Client on. CMD is connected to the 7th CSTA link of the HiPath platform. It merges the CSTA links of the remaining 4 TAPI 120 clients and manages their licenses. Only 4 TAPI 120 user licenses need to be marketed, 6 TAPI 120 Client remain license free.

Example of TAPI 120 user license marketing for OpenScape Office MX V2

The example given before for HiPath 3000 does not apply for OpenScape Office MX V2. For this Communication Platform the connection of TAPI 120 Clients should be done via CMD component basically, to reduce the number of CSTA licences to 1. For this scenario every TAPI 120 Client requires one TAPI 120 User License. The same applies for HiPath OpenOffice ME.

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 In this case the existing license data can be reused 1:1. In this case the existing license data can be reused 1:1. 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.
 * Installation on the same computer HW with the same MAC address.
 * Installation on other computer HW with the same MAC address. (in case of reuse of the network interface card)
 * Installation on other computer HW with different MAC address.

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