HiPath OpenOffice ME open interfaces

From Wiki

HiPath OpenOffice ME offers different types of interfaces which can be used for integration of HiPath OpenOffice ME features into applications and IT landscapes.

Contents 1 Physical interfaces 2 Protocols 2.1 HTTP / HTTPS 2.2 CSTA protocol 2.3 Proprietary protocol for CDR-Übertragung 2.4 SIP (Session Initiation Protokoll) 3 Application Interfaces 3.1 Microsoft TAPI

Physical interfaces

• LAN Ethernet 10/100 base T
• USB
• S0 / S2m
• a/b

Protocols

HTTP / HTTPS

The realisation of the HTTP(S) protocol is done with G-Server support. Therefore the G-Server is installed on a computer within the LAN. G-Server establishes the link to HiPath OpenOffice ME using the CSTA-XML protocol and to the Client using the HTTP(S) protocol. More informations about this HTTP(S) interface and G-Server are available here .

HiPath OpenOffice ME - 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
• ECMA-323 XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III 4th edition (December 2006)

The CSTA interface of HiPath Open Office ME is licenensed per CSTA link.

Physically it is 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 ME). Default port number is 8801.

HiPath OpenOffice ME detects automatically ASN.1 or XML coding. HiPath OpenOffice ME specific implemtation is described within:

Documentation	Version / Date	File	Disclaimer
HiPath OpenOffice ME V1 CSTA Interface Manual	V1.0 / 31.01.2008	HooMECSTA readme	You may download and use this file only if you agree to the DISCLAIMER. If You disagree, your are not allowed to download the file. Any support regarding the CSTA implemtation is only be given to registered partners within the HiPath Technologie Partner Program

Proprietary protocol for CDR-Übertragung

HiPath OpenOffice ME sammelt alle anrufspezifische Daten in einer internen Datei, wie vom Administrator eingerichtet.

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 establishing 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 ME.

Documentation	Version / Date	File	Remark
HiPath OpenOffice ME V1 Ecosystem Open Interfaces	A31003P1010-T101-1-18 05/2008	HooMEINT readme	This document is currently only available in German language

SIP (Session Initiation Protokoll)

SIP is physically available at the Ethernet LAN-Interface. Implementations is done according to the following RFC:

• VoIP über SIP
  • RFC 2198 RTP Payload for Redundant Audio Data
  • RFC 2327 SDP Session Description Protocol
  • 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 3261 SIP Session Initiation Protocol
  • RFC 3262 Provisional Response Acknowledgement (PRACK) Early Media
  • RFC 3263 SIP Locating Servers
  • RFC 3264 An Offer/Answer Model with the Session Description Protocol
  • RFC 3310 HTTP Digest Authentication
  • RFC 3311 Session Initiation Protocol (SIP)UPDATE Method
  • 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 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
  • RFC 3891 The Session Initiation Protocol (SIP) Replaces Header

Application Interfaces

Microsoft TAPI

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

• HiPath TAPI 170 TSP (3rd party)
• CallBridge Collection (1st party not yet released for HiPath OpenOffice ME, coming soon)

TAPI 170 is connected to HiPath OpenOffice ME via LAN interface . Callbridge Collection is connected directly to optiPoint 400 and OpenStage phones using USB or LAN interface.

Manufacturer specific implementations are described within these documents.

Documentation	Version / Date	File	Disclaimer
TAPI Application Developer´s Guide HiPath TAPI 170 V2.0	V1.3 / 28.11.2007	TAPI170 Developers Guide readme	You may download and use this file only if you agree to the DISCLAIMER. If You disagree, your are not allowed to download the file. Any support regarding the TAPI implentation is only be given to registered partners within the HiPath Technologie Partner Program
CallBridge Collection CorNet TS TAPI Service Provider Supplement to the Microsoft Windows Telephony Application Programmer's Guide Version 2.0	V2.0 / November 2004	CBV2_PG readme	You may download and use this file only if you agree to the DISCLAIMER. If You disagree, your are not allowed to download the file. Any support regarding the TAPI implentation is only be given to registered partners within the HiPath Technologie Partner Program