HiPath OpenOffice EE open interfaces

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

Physical interfaces

 * Ethernet LAN
 * USB
 * S0
 * a/b

HTTP / HTTP(S)
The realisation of the HTTP(S) protocol is done with G-Server support. Therefore the G-Server is installed together wtih the CSP on a computer within the LAN. G-Server establishes the link to CSP ising the XML protocol. The CSP components establishes the link to HiPath OpenOffice EE using the CSTA-ASN1 protocol. The client ars connecte to the G-Server via HTTP(S). More informations about this HTTP(S) interface and G-Server are available here.

A sample application based on this interface is myPortal entry.

HiPath OpenOffice EE - HTTP(S) link

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 Open Office EE is not separately licenensed. It is physically available on Ethernet LAN 10/100 base T interface with TCP/IP. Default IP address is 192.168.1.2 (IP address of HiPath OpenOffice EE). Default port number is 7001.

HiPath OpenOffice EE supports only ASN.1 coding. HiPath OpenOffice EE specific implemtation is described within:

Proprietary protocol for CDR transmission
HiPath OpenOffice EE collects all call specift data, as defined within its administration, in an internal file. This file can be transmitted via Ethernet LAN to external computers. To avoid inconsistencies by multiple transmission of the same file, the file should be deleted after transmission. More information about the handling, link established and the call data record content is given within the following document. An asynchonous transfer of single data records, as HiPath 3000 does, is not supported by HiPath OpenOffice EE.

SIP (Session Initiation Protokoll)
SIP is physically available at the Ethernet LAN-Interface. Implementations is done according to the following RFC:


 * RFC 2198	RTP Payload for Redundant Audio Data	Used in conjunction with RFC 2833
 * RFC 2327	SDP: Session Description Protocol (obsoleted by RFC4566)
 * RFC 2617	HTTP Authentication: Basic and Digest Access Authentication
 * RFC 2782	DNS RR for specifying the location of services (DNS SRV)
 * RFC 2833	RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
 * RFC 2976	The SIP INFO Method - Used for SIPQ trunking
 * RFC 3204	MIME media types for ISUP and QSIG Objects
 * RFC 3261	SIP: Session Initiation Protocol - SIP Core RFC
 * RFC 3262	provisional Response Acknowledgement (PRACK) Early Media
 * RFC 3263	SIP Locating Servers
 * RFC 3264	An Offer/Answer Model with SDP
 * RFC 3310	HTTP Digest Authentication
 * RFC 3311	Session Initiation Protocol (SIP) UPDATE Method -Currently UPDATE only supported in receiving direction
 * RFC 3323	A Privacy Mechanism for the Session Initiation Protocol (SIP)
 * RFC 3325	Private Extensions to the Session Initiation Protocol (SIP)for Asserted Identity within Trusted Networks
 * RFC 3326	The Reason Header Field for the Session Initiation Protocol (SIP)
 * RFC 3489	STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
 * RFC 3515	The Session Initiation Protocol (SIP) Refer Method
 * RFC 3550	RTP: Transport Protocol for Real-Time Applications
 * RFC 3551	RTP Profile for Audio and Video Conferences with Minimal Control
 * RFC 3891	The Session Initiation Protocol (SIP) Replaces Header	passive usage only
 * RFC 3581	An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
 * RFC 3711	The Secure Real-time Transport Protocol (SRTP)

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.

Sample Applications
myPortal entry

WebCall Firefox Plugin