CSTA Service Provider (CSP)

HiPath TAPI 120/170

Features
The CSTA service provider interacts with an application and maps CSTA links from multiple HiPath platforms in a network to one logical CSTA. This allows applications to control the phones of all connected HiPath platforms via the CSP.

The CSP CSTA scope essentially corresponds to the descriptions in the CSTA Interface Manual for HiPath 3000. I/O services are not supported.

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.

Supported networking scenarios
The following scenario takes effect when the CSTA interfaces of the systems in the network must be concentrated on a single CSTA link.



The CSTA application on the application server exclusively accesses the CSTA link of the CSP component. This component first arranges the CSTA events from all connected systems in the same sequence as in a standalone HiPath system and presents them to the CSTA application. Applications thus overlook whether the CSTA interface is operated on a standalone HiPath platform or networked platforms. CSTA multi-node connection always requires a HiPath 5000 RSM platform, as well as the CSP and CMD components. In a multi-node environment, the CSP first communicates with a CMD, which is then connected to each individual HiPath platform via Ethernet LAN and CSTA protocol. CSP components retrieve station data for the HiPath platforms connected in the network from the HiPath 5000 RSM database. If station data is changed in the network, the CSP components are automatically notified of the change. Application client PCs in the network access the application server via application-specific mechanisms.

Note: At the time this information was written, HiPath 5000 RSM and CSP / CMD were released only for 32-bit operating systems within this scenario

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 CSP are shown in the table below.

Explanations :

Scenario 2 can be earliest supported, when HiPath 5000 RSM works together with 64-bit operating systems.

Supported systems

 * HiPath 5000 V7, V8

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

Capacities
The CSP component is always configured for: Currently, a maximum of one CSTA application with up to 10 nodes and up to 150 released agents has been tested and released under 1400 BHCA load.
 * Max. 64 nodes
 * Max. 1000 monitoring points, system-wide
 * Theoretically unlimited number of CSTA interfaces to the applications.

PC Hardware
In general the PC hardware equipment must meet the requirements for HiPath 5000 RSM the CSP always runs on the same PC.

PC Software

 * 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

Functional Boundary Conditions

 * The CSP works only in connection with HiPath 5000 RSM.
 * It must be connected to HiPath platforms via LAN (TCP/IP).
 * Only the CSTA Phase III protocol is supported.
 * Operation in 64-bit operating system environments
 * Supported OS: Currently CSP is released for Windows 7 64-bit Windows 2008 64-bit and Windows 2008 R2. It is not intended to support older 64-bit Windows operating systems.

Documentation

 * CSTA Interface Manual for HiPath 3000
 * CSP Developers Guide

The CSP Developers Guide is part of the CSTA Interface Manual, which can be retrieved from the page

HiPath 3000 open interfaces

within this wiki.

Software Delivery
CSP SW 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. Access to the two methods mentioned above is only granted by the manufacturer to registered partners on a contractual base.

Licensing
The use of CSP software components is licensed.

The license defines the number of released CSTA III application links. This is independent of the number of connected nodes. Licenses are bound to the MAC address of the first HiPath node. The license key generated by the license server is imported directly via the CSP components configuration dialog.

Reuse of existing licenses after change from 32 to 64-bit
Existing CSP 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 CSP 32-bit to CSP 64-bit
CSP 64-bit is functionally backward compatible with CSP 32-bit. In case of replacement of the 32-bit CSP the deviations within the supported scenarios of CSP 64-bit in combination with HiPath 5000 RSM have to be considered.