Difference between revisions of "OpenScape Business TAPI 120"
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.
(→Prerequisites) |
(→Prerequisites) |
||
Line 178: | Line 178: | ||
==== Computer HW ==== | ==== 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. | 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 ==== | ==== Computer SW ==== | ||
Line 186: | Line 185: | ||
* Microsoft Windows 7 (32/64 Bit) Service Pack: SP1 | * Microsoft Windows 7 (32/64 Bit) Service Pack: SP1 | ||
* Microsoft Windows 8 32/64 bit except Windows RT | * Microsoft Windows 8 32/64 bit except Windows RT | ||
+ | |||
+ | ==== OpenScape Business ==== | ||
+ | |||
+ | '''TAPI 120 CSTA:''' <br> | ||
+ | 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 | ||
+ | <br> | ||
+ | |||
+ | '''TAPI 120 WSI:''' <br> | ||
+ | Requires the Web Services Interface. A UC Booster (card / server) must not be present in / on the system | ||
+ | <br> | ||
== Documentation == | == Documentation == |
Revision as of 09:07, 22 July 2014
Contents
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 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
TAPI features
The supported TAPI features depend on the kind of connection:
Overview of OpenScape Business TAPI 120 Features | TAPI 120 CSTA | TAPI 120 WSI |
· TAPI supported functionality | ||
– Signaling of incoming and outgoing calls with CLI and the origin of the call | Yes | Yes |
– Additional information in the call signaling with diverted calls | Yes | Yes |
– Call answer of internal and external calls | Yes | Yes |
– Controlled call set up to internal and external targets | Yes | Yes |
– Manual dialing / DTMF dialing | Yes | Yes |
– 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
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
TAPI 120 in WSI mode
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.
Figure: TAPI 120 in the WSI mode with OpenScape Business X5R
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.
Figure: TAPI 120 with OpenScape Business X5R and UC Booster Card
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 120 CSTA | TAPI 120 WSI |
Supported are: | Supported are: |
The same terminals which are supported by the OpenScape Business CSTA Interface. | - Analogue telephone |
- OpenScape Desk Phone devices (HFA) | |
- OpenStage (HFA) terminals | |
- OptiPoint 4xx (HFA) / optiPoint 500 devices | |
(if it is enabled) | |
- OpenScape Cordless devices (CMI) | |
Incoming calls to analogue devices and, OpenScape Cordless terminals must be manually answered | |
Not supported are: | |
- SIP - phones | |
- ISDN - phones | |
- Mobility- / Deskshare Users | |
- Team/Top groups | |
- UCD groups | |
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 CallBridge Collection. As there are:
- Datasheets
- Installation manuals
- Technical release note
The documents can be obtained from the following source:
- Partner Portal of Unify
Documentation | Version / Date | File | Disclaimer |
---|---|---|---|
CallBridge Collection
CorNet TS TAPI Service Provider Supplement to the Microsoft Windows Telephony Application Programmer's Guide Version 2.0 |
V2.0 / November 2004 |
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 |
Software Delivery / Deployment
The CallBridge Collection software package can be downloaded free of charge from the Software Download Server (SWS) within the Partner Portal of Unify. The package contains, in addition to the TAPI service provider setup, all necessary USB drivers, the installation manual and a README.TXT with up-to-date information on the product.
Licensing
Callbridge Collection SW is not licensed
SW Upgrade / Migration
Useful Tools
Further technical Information
How To
Suitable task descriptions with links to corresponding procedures in the How To article(s)
Whitepapers
Suitable white paper document titles with links to the corresponding White Paper article(s)