Views

Difference between revisions of "OpenScape Business TAPI 170"

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.

Jump to: navigation, search
Line 3: Line 3:
 
== Overview ==
 
== Overview ==
  
−
OpenScape Business TAPI 120 TSP is a "first party" telephony service provider that supports the Microsoft TAPI V2.1 functionality. TAPI 120 enables Microsoft Windows-based CTI applications to monitor and control a phone or device connected to OpenScape Business.
+
OpenScape Business TAPI 170 TSP is a "third party" telephony service provider that supports the Microsoft TAPI V2.1 functionality. TAPI 170 enables Microsoft Windows-based CTI applications to concurrently monitor and control phones or devices connected to OpenScape Business.
−
<br>
 
−
OpenScape Business TAPI 120 can alternatively be connected via LAN using the WSI (WebServices Interface) to the Motherboard of OpenScape Business or via LAN to the UC Booster HW using CSTA (Computer Supported Telephony Application) protocol). A mixed operation of the interface modes to one system is not possible.
 
−
If the OpenScape Business system contains a UC Booster Card or if it is connected to a UC Booster server, TAPI 120 can only be operated with the CSTA protocol.
 
  
 
== Features ==
 
== Features ==
  
−
=== TAPI features ===
+
* Centrally connected third-party TAPI Service Provider.
−
 
+
* Compatible with the Microsoft TAPI 2.1 Standard
−
The supported TAPI features depend on the kind of connection:
+
* Telephony functions are available on each connected PC client via the TAPI 2.1 client/server architecture.
−
 
+
* No additional TSP client software is required
−
 
+
* Supported telephony features
−
{| {{DefaultTable}}
+
* Selection or dialing of incoming/outgoing calls from the PC
−
| align="center" style="background:#f0f0f0;"|'''Overview of OpenScape Business TAPI 120 Features'''
+
* Transmission of incoming call number, if signaled
−
| align="center" style="background:#f0f0f0;"|'''TAPI 120 CSTA'''
+
* Consultation and transfer
−
| align="center" style="background:#f0f0f0;"|'''TAPI 120 WSI'''
+
* Toggle/Connect
−
|-
+
* Conferencing
−
| ·      TAPI supported functionality ||||
+
* Call forwarding
−
|-
+
* Forwarding callers
−
| –    Signaling of incoming and outgoing calls with CLI and the origin of the call||Yes||Yes
+
* Answering a call through the application
−
|-
+
* Initiating a call through the application
−
| –    Additional information in the call signaling with diverted calls||Yes||Yes
+
* Blind/Supervised transfer (also called "transfer before answer / consultation transfer")
−
|-
+
* Transmission of feature codes
−
| –    Call answer of internal and external calls||Yes||Yes
+
* Monitoring of the phone (call states, failure, etc.)
−
|-
+
* Provision of an ACD interface
−
| –    Controlled call set up to internal and external targets||Yes||Yes
+
* Monitoring / access to keypad for system telephones (HFA)
−
|-
+
* Control of display/LED for system telephones (HFA)
−
| –    Manual dialing / DTMF dialing||Yes||Yes
+
* Connection to standalone and networked OpenScape Business systems
−
|-
+
* Support for MULAP members / station numbers
−
| –    Clear down of existing calls||Yes||Yes
 
−
|-
 
−
| –    Recall to internal and external parties||Yes||Yes
 
−
|-
 
−
| –    Toggle||Yes||Yes
 
−
|-
 
−
| –    Supervised Call Transfer||Yes||Yes
 
−
|-
 
−
| –    Supervised Call Transfer with subsequent dialing of the query target (one-step transfer)||Yes||Yes
 
−
|-
 
−
| –    Unsupervised Call Transfer (Blind Transfer)||Yes||No
 
−
|-
 
−
| –    Activation and deactivation of call forwarding||Yes||Yes
 
−
|-
 
−
| –    Activation and deactivation of DND||Yes||Yes
 
−
|-
 
−
| –    Set up a conference||Yes||No
 
−
|-
 
−
| –    Expanding the conference||Yes||No
 
−
|-
 
−
| –    Forward incoming call||Yes||No
 
−
|-
 
−
| –    Directed pickup (Call Pickup)||Yes||No
 
−
|-
 
−
| –    Group call signaling and acquisition group call (Group pickup||Yes||No
 
−
|-
 
−
| –    Call park||Yes||No
 
−
|-
 
−
| –    Call park retrieval||Yes||No
 
−
|-
 
−
| –    Call hold||Yes||No
 
−
|-
 
−
| –    Call hold retrieval||Yes||No
 
−
|-
 
−
| –    Set callback||Yes||No
 
−
|-
 
−
| –    Support for code-controlled functions||Yes||No
 
−
|-
 
−
| –    exchange of call relevant data between TAPI applications||Yes||No
 
−
|-
 
−
| –    Activation of programmable keys at system terminals (HFA)||Yes||No
 
−
|-
 
−
| –    Control the microphone gain in system terminals (HFA)||Yes||No
 
−
|-
 
−
| –    Control / selection of the use of Handset / loud speaker / headset with system terminals (HFA)||Yes||No
 
−
|-
 
−
| –    volume control of handset / speaker / headset keyboard with system terminals (HFA)||Yes||No
 
−
|-
 
−
| –    Access to optiPoint / OpenStage display and the LEDs (with limitation to 50 active displays per system)||Yes||No
 
−
|-
 
−
| ·      connection to OpenScape Business Single systems||Yes||Yes
 
−
|-
 
−
| ·      Support for OpenScape Business CTI Firewall||Yes||No
 
−
|-
 
−
|
 
−
|}
 
−
 
 
−
 
 
  
 
== Connectivity ==
 
== Connectivity ==
  
−
The TAPI 120 software is installed on a Microsoft Windows client PC. The connection to the OpenScape Business System occurs via a LAN. A physical connection between the Windows PC and the phone is not required
+
The OpenScape Business TAPI 170 software is installed on a Microsoft Windows server on the network. The connection to OpenScape Business occurs via a CSTA link. A physical connection between the Windows PC and the phone is not required.<br>
 +
OpenScape Business TAPI 170 can be set up in different operating modes on single node systems or in the OpenScape Business network.
  
 +
=== Server-based TAPI Applications to OpenScape Business using TAPI 170 ===
  
−
=== TAPI 120 in WSI mode ===
+
The server applications and the TAPI 170 software are installed on the so-called "Telephony Server" in the network. The server applications provide their associated clients in the network with telephony features for stations that are configured within OpenScape Business TAPI 170. The TAPI 170 software is connected to the CSTA interface of OpenScape Business over the LAN. <br>
−
+
For this connection, one CSTA link of OpenScape Business as well as one TAPI license for each configured TAPI station are required.
−
All TAPI 120 client PCs are connected via LAN, via the web server interface to the motherboard of the OpenScape business. OpenScape business internally multiplexes all TAPI 120 connections.
 
  
−
[[Image:OSBiz_TAPI120_WSI.png|700px|TAPI 120 connected via WSI]]
+
[[Image:OSBiz_TAPI170_server_based.png|700px|TAPI 170 Server based TAPI Application]]
  
−
Figure: TAPI 120 in the WSI mode with OpenScape Business X5R
+
Figure: TAPI 170 with server-based TAPI application
  
 
=== TAPI 120 in CSTA Mode ===
 
=== TAPI 120 in CSTA Mode ===
 +
 
All TAPI 120 client PCs are connected to the same CSTA link of OpenScape Business.  OpenScape Business internally multiplexes all TAPI 120 connections.
 
All TAPI 120 client PCs are connected to the same CSTA link of OpenScape Business.  OpenScape Business internally multiplexes all TAPI 120 connections.
  
Line 134: Line 75:
  
 
=== Supported Devices ===
 
=== Supported Devices ===
−
{| {{DefaultTable}}
+
TAPI 170 supports the same devices as the OpenScape Business CSTA interface.<br>
−
| align="center" style="background:#f0f0f0;"|'''TAPI 120 CSTA'''
+
These are described in section 1.6.11, "CSTA Interface".
−
| align="center" style="background:#f0f0f0;"|'''TAPI 120 WSI'''
 
−
|-
 
−
| Supported are:||Supported are:
 
−
|-
 
−
| The same devices which are supported by the OpenScape Business CSTA Interface.||-          Analogue  telephones
 
−
|-
 
−
| ||-          OpenScape Desk Phone devices (HFA)
 
−
|-
 
−
| ||-          OpenStage devices (HFA)
 
−
|-
 
−
| ||-          OptiPoint 4xx (HFA) / optiPoint 500 devices
 
−
|-
 
−
| ||-          OpenScape Cordless devices (CMI)
 
−
|-
 
−
| ||'''Not supported are:'''
 
−
|-
 
−
| ||-          SIP - phones
 
−
|-
 
−
| ||-          ISDN - phones
 
−
|-
 
−
| ||-          Mobility- / Deskshare Users
 
−
|-
 
−
| ||-          Team/Top groups
 
−
|-
 
−
| ||-          UCD groups
 
−
|-
 
−
|
 
−
|}
 
  
 
== Prerequisites ==
 
== Prerequisites ==

Revision as of 10:41, 22 July 2014

You are here:  

Icon linkarrow.gif Home  Icon linkarrow.gif OpenScape Business  Icon linkarrow.gif OpenScape Business TAPI 170

Overview

OpenScape Business TAPI 170 TSP is a "third party" telephony service provider that supports the Microsoft TAPI V2.1 functionality. TAPI 170 enables Microsoft Windows-based CTI applications to concurrently monitor and control phones or devices connected to OpenScape Business.

Features

  • Centrally connected third-party TAPI Service Provider.
  • Compatible with the Microsoft TAPI 2.1 Standard
  • Telephony functions are available on each connected PC client via the TAPI 2.1 client/server architecture.
  • No additional TSP client software is required
  • Supported telephony features
  • Selection or dialing of incoming/outgoing calls from the PC
  • Transmission of incoming call number, if signaled
  • Consultation and transfer
  • Toggle/Connect
  • Conferencing
  • Call forwarding
  • Forwarding callers
  • Answering a call through the application
  • Initiating a call through the application
  • Blind/Supervised transfer (also called "transfer before answer / consultation transfer")
  • Transmission of feature codes
  • Monitoring of the phone (call states, failure, etc.)
  • Provision of an ACD interface
  • Monitoring / access to keypad for system telephones (HFA)
  • Control of display/LED for system telephones (HFA)
  • Connection to standalone and networked OpenScape Business systems
  • Support for MULAP members / station numbers

Connectivity

The OpenScape Business TAPI 170 software is installed on a Microsoft Windows server on the network. The connection to OpenScape Business occurs via a CSTA link. A physical connection between the Windows PC and the phone is not required.
OpenScape Business TAPI 170 can be set up in different operating modes on single node systems or in the OpenScape Business network.

Server-based TAPI Applications to OpenScape Business using TAPI 170

The server applications and the TAPI 170 software are installed on the so-called "Telephony Server" in the network. The server applications provide their associated clients in the network with telephony features for stations that are configured within OpenScape Business TAPI 170. The TAPI 170 software is connected to the CSTA interface of OpenScape Business over the LAN.
For this connection, one CSTA link of OpenScape Business as well as one TAPI license for each configured TAPI station are required.

TAPI 170 Server based TAPI Application

Figure: TAPI 170 with server-based TAPI application

TAPI 120 in CSTA Mode

All TAPI 120 client PCs are connected to the same CSTA link of OpenScape Business. OpenScape Business internally multiplexes all TAPI 120 connections.

TAPI 120 connected via CSTA

Figure: TAPI 120 in CSTA mode with OpenScape Business X5R and UC Booster Card

Capacities

The maximum number of TAPI 120 client PCs that can be connected to OpenScape Business depends on the model. More information on this can be found within the OpenScape Business Sales Information.

Compatibility

Supported Systems

TAPI 120 CSTA TAPI 120 WSI
OpenScape Business X3 OpenScape Business X1
OpenScape Business X5 OpenScape Business X3
OpenScape Business X8 OpenScape Business X5
Open Scape Business S OpenScape Business X8

Supported Devices

TAPI 170 supports the same devices as the OpenScape Business CSTA interface.
These are described in section 1.6.11, "CSTA Interface".

Prerequisites

For operation of OpenScape Business TAPI 120 some HW / SW prereqisites have to be fulfilled

HW/SW prerequisites

Computer HW

The PC hardware must comply with at least the system requirements specified by Microsoft for the operating system used as well as the requirements of the TAPI application. In addition, an Ethernet LAN interface is required.

Computer SW

Operating systems

  • Microsoft Windows 7 (32/64 Bit) Service Pack: SP1
  • Microsoft Windows 8 32/64 bit except Windows RT

OpenScape Business

TAPI 120 CSTA:
Regardless of the number of TAPI 120 clients a CSTA link of the OpenScape Business is required. For this purpose, a UC Booster (card or server) is a prerequisite

TAPI 120 WSI:
Requires the Web Services Interface. A UC Booster (card / server) must not be present in / on the system

Documentation

Some documents in various languages are available for OpenScape Business TAPI 120. As there are:

  • Installation manuals
  • Technical release note

The documents can be obtained from the following source:

Software Delivery / Deployment

The OpenScape Business TAPI 120 software is supplied on a separate data medium. It is not part of the OpenScape Business System software. The software package can also be downloaded free of charge from the Software Download Server (SWS) within the Partner Portal of Unify.

Licensing

The use of OpenScape Business TAPI 120 is licensed on a subscriber basis.
The TAPI licenses are managed within the OpenScape Business system and can be used for both TAPI 120 modes. When using the "MULAP" feature, a TAPI license is required for each station within the MULAP.
Note: TAPI 120 in the WSI Mode requires only a TAPI user licenses. A UC user licenses is not necessary.

SW Upgrade / Migration

Before migrating from HiPath 3000 with HiPath TAPI 120 V2 to OpenScape Business V1 with TAPI 120 in the WSI mode the functionality of the TAPI services should be verified in order to ensure that they are sufficient. If they are not sufficient either TAPI 120 in the TAPI 120 CSTA mode or Call Bridge Collection should be used.
Ensure that a OpenScape Business TAPI License is available within OpenScape Business for every TAPI 120 user. Existing HiPath TAPI 120 user licenses cannot be used further on within OpenScape Business.
HiPath TAPI 120 SW has to be uninstalled and to be replaced by OpenScape Business TAPI 120 SW on the client PC.

Constaints

Only Microsoft Windows operating systems can be used in conjunction with TAPI 120.
For installations on terminal servers, OpenScape Business TAPI 170 must be used instead of TAPI 120.

Useful Tools

Further technical Information

Retrieved from "http://wiki.unify.com/index.php?title=OpenScape_Business_TAPI_170&oldid=42424"