OpenScape Office MX open interfaces

	OpenScape Office MX
	New Features
	Contact Center
	Open Interfaces
	Released VoIP Provider
	Open Source Software
	Data Gathering Tool
	Application documents: Citrix Presentation Server 4.5 Citrix XenApp 5.0 Windows Terminal Server 2003 Windows Terminal Server 2008 Microsoft Exchange Server 2007
	www.openscapeoffice.com

OpenScape Office MX offers different types of open interfaces which can be used for integration of OpenScape Office MX features into applications and IT landscapes.

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.

G-server is integrated part of HiPath OpenScape Office MX V2 software. No SW download and no external PC are required for use of the G-Server. G-Server administration can be done via the Web Based Administration (WBM) of OpenScape Office MX V2

OpenScape Office MX - 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 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 OpenScape Office MX). Default port number is 8800.

OpenScape Office MX detects automatically ASN.1 or XML coding. OpenScape Office MX specific implemtation is described within:

Proprietary protocol for CDR-Transmission

OpenScape Office MX 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 OpenScape Office MX.

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

SIP protocol is available at subscriber lines and at trunk lines. For interoperability with VoIP Providers (SIP trunking) see Collaboration with VoIP Providers.

Application Interfaces

Microsoft TAPI

OpenScape Office MX 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 OpenScape Office MX, coming soon)

TAPI 170 is connected to OpenScape Office MX 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.