1  

Introduction 
 

1.1  

General 
 

OpenScape Business TAPI 170  
OpenScape Business TAPI 170 is a "3rd party" telephony service provider based on Windows TAPI 2.2 functionality. OpenScape Business TAPI 170 enables CTI-based server applications to control and to monitor multiple phones / devices connected to OpenScape Business.

Application of OpenScape Business TAPI 170  
OpenScape Business TAPI 170 can be used in different operation and connection modes. You find further information in the section Operation and connection mode alternatives.

Documentation  
 •   Various abbreviations are used in this document to improve readability. An overview of all abbreviations can be found in the List of abbreviations.
 •   To improve readability, "telecommunications system(s)" has been abbreviated to "system(s)" or "communication system(s)"in this document.
 •   The product name OpenScape Business TAPI 170 has also been abbreviated to TAPI 170 for the same reason.
 •   All described operation sequences and dialogs correspond to the referred Windows versions. With using other Windows versions you have to activate the functions accordingly.

Maximum number of TAPI 170 users  
The maximum numbers of TAPI 170 users / maximum number of parallel TAPI 170 connections depend on the OpenScape Business system model. You find more information about this limitations in the corresponding sales information.

Licensing of TAPI 170  
The TAPI 170 licensing is handled in the OpenScape Business. Further information is available in the OpenScape Business documentation.
Each TAPI 170 user connected to OpenScape Business requires a separate user licence (starting with the first user).  
The use of older HiPath TAPI 170 licences is not possible.  

Supported features  
OpenScape Business TAPI 170 software provides in general the following features of the TAPI interface:

Feature  
Centrally connected 3rd party TAPI service provider (TAPI 170 telephony server)  
Compatible to Microsoft TAPI 2.1 standard  
Telephony features are available on every connected TAPI 170 client via TAPI 2.2 client/server architecture for Microsoft remote TSP  
No additional TAPI client software required  
Call signalling of incoming and outgoing calls with identification of call number  
Additional information with redirected calls  
Answer incoming and outgoing calls  
Make call to external or internal parties  
Dialing /DTMF signaling  
Release existing calls (drop call)  
Initiate callback call to internal or external parties  
Toggling between calls  
Consultative call transfer  
Consultative call transfer with dialing the extension of the destination party (one step transfer)  
Unattendet call transfer (Blind Transfer)  
Set /delete call forwarding  
Set /delete DND  
Start conference  
Add participants to conference  
Redirect incoming call  
Call Pickup  
Group call signalling with group pickup  
Park existing calls  
Unpark parked calls  
Hold existing calls  
Unhold calls which are on hold  
Set automatic callback  
Support of code-dependent functions  
Call data exchange between TAPI applications  
ACD interface supplied  
Key access to optiPoint / OpenStage keypad  
Control volume of Microphone  
Control/select use of Handset/Speaker/Headset  
Control volume of Handset/Speaker/Headset  
Display / LED access to optiPoint / OpenStage displays (with limitation to 50 active displays per system)  

Supported phones / devices  
Supported phones / devices and the supported features per device depend on the CSTA capabilities of OpenScape Business. Details are described within the sales information.

Support of MULAP (multi line appearance)  
TAPI 170 directly supports basic MULAP groups, i.e. an OpenScape Business MULAP group can be used as a TAPI 170 user.
Each OpenScape Business member of a MULAP group requires a separate TAPI 120/170 user licence.