HiPath 3000 open interfaces

HiPath 3000 | HiPath 3000 open interfaces

HiPath 3000 offers different types of open interfaces for integration of its features into applications and IT landscapes.

Physical interfaces

 * Ethernet LAN
 * S0
 * a/b

CSTA protocol
CSTA protocol implementation is based on following ECMA recommendations:


 * ECMA 269 Services for Computer Supported Telecommunications Applications (CSTA) Phase III
 * ECMA 285 Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III

The CSTA interface of HiPath 3000 is not licensed separately. It is physically available on Ethernet LAN 10/100 base T interface with TCP/IP. Before use, LAN access of HP 3000 has to be enabled by system administration via system telephone or Manager E SW Tool. No default IP addresses are used within HiPath 3000 systems. IP addresses have to be configured explicitly. The default IP address of HG 1500 (10.144.233.63) is reserved for startup and cannot be used as a permanent IP address in the network. In addition the CSTA protocol and the required events has also to be enabled within system configuration.

Default port number for CSTA access is 7001.

HiPath 3000 supports CSTA ASN.1 coding HiPath 3000 specific implemtation is described within:

HiPath 3000 V8 MULAP Monitoring
From Version 8 on, HiPath 3000 CSTA interface supports monitoring of MULAP and MULAP devices.



A system flag, which can be set within the HP 3000 CSTA configuration, determines if MULAP devices can be monitored or not. Per default the MULAP monitoring is switched off.

Once the flag has been set the CSTA call flow follows the new mechanisms every time a MULAP device or a MULAP number is involved within a call. This may cause problems within applications, which are not prepared for the new event flow. Check application compatibility before switching on the new CSTA event flow !

Important remark

If OpenScape Office HX application is connected to HiPath 3000 MULAP monitoring has to be enabled.

Feedback about implementation

As no implementation standard is defined by ECMA a feedback about our implementation approach is welcome. Please address your feedback by e-mail directly to the author of this article.

Proprietary protocol for CDR transmission
HiPath 3000 transmits the call data records (CDR) via RS 232 or Ethernet LAN interface either for printer output or for further processing by an external computers. Call data records are call related and are transmitted when the calls are terminated. In case the connection to printer or external computer is broken HiPath 3000 stores call data records in an internal buffer. If the number of CDR exeeds the limit new records are dropped. The dropped records are counted internally.

After link is reestablished the number of dropped records is reported and the buffered CDR are tansmitted mixed with actual data. HiPath 3000 does not support a file storage of CDR like HiPath openOffice ME or EE does.

An english description of CDR can be found in the current HiPath 3000 Feature Description chapter 12.8.

Microsoft TAPI
HiPath OpenOffice EE provides three TAPI service providers (TSP) for implementation in Microsoft TAPI based applications:


 * HiPath TAPI 120 TSP (1st party)
 * HiPath TAPI 170 TSP (3rd party)
 * CallBridge Collection (1st party)

Hipath TAPI 120 and 170 are connected to HiPath OpenOffice EE via LAN interface. Callbride Collection is conected directly to optipoint 400 and openstage phones using USB or LAN interface.

Manufacturer specific implementations are described within these documents.