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
(→‎SW Upgrade / Migration)
 
(15 intermediate revisions by the same user not shown)
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
 +
* 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.<br>
 +
OpenScape Business TAPI 170 can be set up in different operating modes on single node systems or in the OpenScape Business network.
 +
 
 +
=== Connecting server-based TAPI Application 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. <br>
 +
For this connection, one CSTA link of OpenScape Business as well as one TAPI license for each configured TAPI station are required.
  
−
The supported TAPI features depend on the kind of connection:
+
[[Image:OSBiz_TAPI170_server_based.png|700px|TAPI 170 Server based TAPI Application]]
  
 +
Figure: TAPI 170 with server-based TAPI Application
  
−
{| {{DefaultTable}}
+
=== Connecting Client-based TAPI Applications to OpenScape Business using TAPI 170 ===
−
| align="center" style="background:#f0f0f0;"|'''Overview of OpenScape Business TAPI 120 Features'''
 
−
| align="center" style="background:#f0f0f0;"|'''TAPI 120 CSTA'''
 
−
| align="center" style="background:#f0f0f0;"|'''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
 
−
|-
 
−
|
 
−
|}
 
  
 +
In this scenario, the OpenScape Business TAPI 170 software is installed on a server on the network. On the client PCs with the TAPI applications, the so-called "Remote TAPI" function is enabled, via which the TAPI application on the client communicates with the TAPI 170 SW on the server. No TAPI 170 software needs to be installed on the client for this purpose. 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.
  
 +
[[Image:OSBiz_TAPI170_remote_TAPI.png|700px|TAPI 170 with remote TAPI]]
  
−
== Connectivity ==
+
Figure: TAPI 170 with remote TAPI
  
−
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
+
=== Connecting Terminal Server-based TAPI Applications to OpenScape Business using TAPI 170 ===
  
 +
In this scenario, the client-based TAPI applications are installed on one or more terminal servers. In this case, the TAPI 170 software is also installed on the terminal server. In the case of a cluster consisting of multiple terminal servers, the TAPI 170 software must be installed on each terminal server in the cluster. Each instance of the installed TAPI 170 software is connected to OpenScape Business over the LAN.
 +
For each instance of the TAPI 170 software installed on a terminal server, one CSTA link of OpenScape Business is required. In addition, a TAPI license is also required for each configured TAPI station.
 +
<br>
 +
'''Note'''
 +
The number of terminal servers that can be operated in the cluster is limited to the number of free CSTA links available within OpenScape Business for connecting the TAPI 170 software. This should be checked and taken into account before marketing.
  
−
=== TAPI 120 in WSI mode ===
+
[[Image:OSBiz_TAPI170_terminal_server_based.png|700px|TAPI 170 Terminal-Server based TAPI Application]]
−
 
−
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]]
+
Figure: TAPI 170 with Terminal Server-based TAPI application
  
−
Figure: TAPI 120 in the WSI mode with OpenScape Business X5R
+
=== Connecting TAPI 170 to Networked OpenScape Business Systems ===
  
−
=== TAPI 120 in CSTA Mode ===
+
For networked OpenScape Business systems, the TAPI 170 software is installed on one server, which is connected via the LAN to the CSTA interface of the master node.
−
All TAPI 120 client PCs are connected to the same CSTA link of OpenScape Business. OpenScape Business internally multiplexes all TAPI 120 connections.
+
This connection is independent of the previously mentioned operating modes of the TAPI 170 Service Provider (remote TAPI or server-based connection).
 +
To implement this connection, one CSTA link of the OpenScape Business master node as well as one TAPI license for each configured TAPI station are required.<br>
 +
'''Note'''
 +
Via the master node, the TAPI 170 receives network-wide access to all stations in the network.
 +
If the TAPI 170 is connected to a slave node instead of the master node, TAPI 170 can access only the stations of the slave node.
 +
When using multiple TAPI 170 in a terminal server cluster, one CSTA link to the master node is required for each TAPI 170.
  
−
[[Image:OSBiz_TAPI120_CSTA.png|700px|TAPI 120 connected via CSTA]]
+
[[Image:OSBiz_TAPI170_networked.png|700px|TAPI 170 in a network]]
  
−
Figure: TAPI 120 in CSTA mode with OpenScape Business X5R and UC Booster Card
+
Figure: TAPI 170 with networked OpenScape Business Systems
  
 
== Capacities ==
 
== Capacities ==
Line 118: Line 86:
 
=== Supported Systems ===
 
=== Supported Systems ===
  
−
{| {{DefaultTable}}
+
* OpenScape Business X3
−
| align="center" style="background:#f0f0f0;"|'''TAPI 120 CSTA'''
+
* OpenScape Business X5
−
| align="center" style="background:#f0f0f0;"|'''TAPI 120 WSI'''
+
* OpenScape Business X8
−
|-
+
* Open Scape Business S
−
| 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 ===
 
=== 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 ==
  
−
For operation of OpenScape Business TAPI 120 some HW / SW prereqisites have to be fulfilled
+
For operation of OpenScape Business TAPI 170 some HW / SW prereqisites have to be fulfilled
  
 
=== HW/SW prerequisites ===
 
=== HW/SW prerequisites ===
  
 
==== 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, provided that no further software applications other than TAPI 170 are being operated. In addition, an Ethernet LAN interface is required.
  
 
==== Computer SW ====
 
==== Computer SW ====
Line 178: Line 109:
 
'''Operating systems'''
 
'''Operating systems'''
  
−
* Microsoft Windows 7 (32/64 Bit) Service Pack: SP1
+
* Microsoft Windows Server
−
* Microsoft Windows 8 32/64 bit except Windows RT
+
** Microsoft Server 2008 R2, 64 bit
 +
** Microsoft Server 2012, 64 bit
 +
** Microsoft Small Business Server 2011
 +
** Microsoft Small Business Server 2012 (essential)
 +
 
 +
 
 +
* Terminal Server
 +
** Citrix XenApp 6.0, 6.5
 +
** Microsoft Server 2008 R2, 64 bit
 +
** Microsoft Server 2012, 64 bit
 +
 
 +
 
 +
* Virtualization
 +
** VMware vSphere 5
 +
 
 +
 
 +
* Remote Client PC for Remote TAPI
 +
** Microsoft Windows 7 (Ultimate, Professional)
 +
** Microsoft Windows 8 (Pro, Enterprise) not Windows RT
 +
** Microsoft Server 2008 R2
 +
** Microsoft Server 2012
 +
 
 +
 
 +
'''Note'''<br>
 +
In addition to the license for the server operating system, the Microsoft licensing model requires Microsoft device or User CALs corresponding to the number required for the planned expansion. These CALs are not included in the delivery of OpenScape Business TAPI 170 and must be purchased separately. <br>
 +
Under certain conditions specified by Microsoft, a "Windows Server for embedded systems" with the so-called "embedded Telco license" can be used for OpenScape Business TAPI 170.
  
 
==== OpenScape Business ====
 
==== OpenScape Business ====
  
−
'''TAPI 120 CSTA:''' <br>
+
In order to connect to OpenScape Business TAPI 170, one CSTA link of OpenScape Office is required, regardless of how many TAPI 170 clients are connected. This also applies to networked OpenScape Business systems.
−
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
+
Connection to a CSTA link requires either UC Booster Card or UC Booster Server
−
<br>
 
−
 
 
−
'''TAPI 120 WSI:''' <br>
 
−
Requires the Web Services Interface. A UC Booster (card / server) must not be present in / on the system
 
 
<br>
 
<br>
  
Line 204: Line 156:
  
 
== Software Delivery / Deployment ==
 
== 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.
+
The OpenScape Business TAPI 170 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 ==
 
== Licensing ==
−
The use of OpenScape Business TAPI 120 is licensed on a subscriber basis. <br>
+
The use of OpenScape Business TAPI 170 is licensed on a subscriber basis. The licenses are managed within the OpenScape Business system.
−
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.
+
When using the "MULAP" feature, a TAPI license is required for each station within the MULAP.
−
<br>
 
−
'''Note:'''
 
−
TAPI 120 in the WSI Mode requires only a TAPI user licenses. A UC user licenses is not necessary.
 
  
 
== SW Upgrade / Migration ==
 
== 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.
+
Before migrating from HiPath 3000 with HiPath TAPI 170 V2 to OpenScape Business V1 with TAPI 170 ensure that a OpenScape Business TAPI License is available within OpenScape Business for every TAPI 170 user. Existing HiPath TAPI 170 user licenses cannot be used further on within OpenScape Business. <br>
−
<br>
+
HiPath TAPI 170 SW has to be uninstalled and to be replaced by OpenScape Business TAPI 170 SW on the server PC.
−
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. <br>
+
 
−
HiPath TAPI 120 SW has to be uninstalled and to be replaced by OpenScape Business TAPI 120 SW on the client PC.
+
== Constraints ==
 +
Only Microsoft Windows operating systems can be used in conjunction with TAPI 170.<br>
 +
The TAPI server and clients must be managed by the same network domain controller, if remote TAPI function is used. <br>
 +
 
  
−
== Constaints ==
+
The following applies to the terminal server environment:<br>
−
Only Microsoft Windows operating systems can be used in conjunction with TAPI 120.<br>
+
* OpenScape Business TAPI 170 must be installed on the same server hardware as the terminal server.
−
For installations on terminal servers, OpenScape Business TAPI 170 must be used instead of TAPI 120.
+
* When using a terminal server cluster architecture, the TAPI 170 software must be installed on each terminal server in the cluster.
 +
* The maximum possible number of OpenScape Business TAPI 170 servers in conjunction with OpenScape Business must not be exceeded. The maximum number of possible connections is reduced if the CSTA links of OpenScape Business are used by other CSTA applications.
  
 
== Useful Tools ==
 
== Useful Tools ==

Latest revision as of 12:34, 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.

Connecting server-based TAPI Application 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

Connecting Client-based TAPI Applications to OpenScape Business using TAPI 170

In this scenario, the OpenScape Business TAPI 170 software is installed on a server on the network. On the client PCs with the TAPI applications, the so-called "Remote TAPI" function is enabled, via which the TAPI application on the client communicates with the TAPI 170 SW on the server. No TAPI 170 software needs to be installed on the client for this purpose. 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 with remote TAPI

Figure: TAPI 170 with remote TAPI

Connecting Terminal Server-based TAPI Applications to OpenScape Business using TAPI 170

In this scenario, the client-based TAPI applications are installed on one or more terminal servers. In this case, the TAPI 170 software is also installed on the terminal server. In the case of a cluster consisting of multiple terminal servers, the TAPI 170 software must be installed on each terminal server in the cluster. Each instance of the installed TAPI 170 software is connected to OpenScape Business over the LAN. For each instance of the TAPI 170 software installed on a terminal server, one CSTA link of OpenScape Business is required. In addition, a TAPI license is also required for each configured TAPI station.
Note The number of terminal servers that can be operated in the cluster is limited to the number of free CSTA links available within OpenScape Business for connecting the TAPI 170 software. This should be checked and taken into account before marketing.

TAPI 170 Terminal-Server based TAPI Application

Figure: TAPI 170 with Terminal Server-based TAPI application

Connecting TAPI 170 to Networked OpenScape Business Systems

For networked OpenScape Business systems, the TAPI 170 software is installed on one server, which is connected via the LAN to the CSTA interface of the master node. This connection is independent of the previously mentioned operating modes of the TAPI 170 Service Provider (remote TAPI or server-based connection). To implement this connection, one CSTA link of the OpenScape Business master node as well as one TAPI license for each configured TAPI station are required.
Note Via the master node, the TAPI 170 receives network-wide access to all stations in the network. If the TAPI 170 is connected to a slave node instead of the master node, TAPI 170 can access only the stations of the slave node. When using multiple TAPI 170 in a terminal server cluster, one CSTA link to the master node is required for each TAPI 170.

TAPI 170 in a network

Figure: TAPI 170 with networked OpenScape Business Systems

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

  • OpenScape Business X3
  • OpenScape Business X5
  • OpenScape Business X8
  • Open Scape Business S


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 170 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, provided that no further software applications other than TAPI 170 are being operated. In addition, an Ethernet LAN interface is required.

Computer SW

Operating systems

  • Microsoft Windows Server
    • Microsoft Server 2008 R2, 64 bit
    • Microsoft Server 2012, 64 bit
    • Microsoft Small Business Server 2011
    • Microsoft Small Business Server 2012 (essential)


  • Terminal Server
    • Citrix XenApp 6.0, 6.5
    • Microsoft Server 2008 R2, 64 bit
    • Microsoft Server 2012, 64 bit


  • Virtualization
    • VMware vSphere 5


  • Remote Client PC for Remote TAPI
    • Microsoft Windows 7 (Ultimate, Professional)
    • Microsoft Windows 8 (Pro, Enterprise) not Windows RT
    • Microsoft Server 2008 R2
    • Microsoft Server 2012


Note
In addition to the license for the server operating system, the Microsoft licensing model requires Microsoft device or User CALs corresponding to the number required for the planned expansion. These CALs are not included in the delivery of OpenScape Business TAPI 170 and must be purchased separately.
Under certain conditions specified by Microsoft, a "Windows Server for embedded systems" with the so-called "embedded Telco license" can be used for OpenScape Business TAPI 170.

OpenScape Business

In order to connect to OpenScape Business TAPI 170, one CSTA link of OpenScape Office is required, regardless of how many TAPI 170 clients are connected. This also applies to networked OpenScape Business systems. Connection to a CSTA link requires either UC Booster Card or UC Booster Server

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 170 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 170 is licensed on a subscriber basis. The licenses are managed within the OpenScape Business system. When using the "MULAP" feature, a TAPI license is required for each station within the MULAP.

SW Upgrade / Migration

Before migrating from HiPath 3000 with HiPath TAPI 170 V2 to OpenScape Business V1 with TAPI 170 ensure that a OpenScape Business TAPI License is available within OpenScape Business for every TAPI 170 user. Existing HiPath TAPI 170 user licenses cannot be used further on within OpenScape Business.
HiPath TAPI 170 SW has to be uninstalled and to be replaced by OpenScape Business TAPI 170 SW on the server PC.

Constraints

Only Microsoft Windows operating systems can be used in conjunction with TAPI 170.
The TAPI server and clients must be managed by the same network domain controller, if remote TAPI function is used.


The following applies to the terminal server environment:

  • OpenScape Business TAPI 170 must be installed on the same server hardware as the terminal server.
  • When using a terminal server cluster architecture, the TAPI 170 software must be installed on each terminal server in the cluster.
  • The maximum possible number of OpenScape Business TAPI 170 servers in conjunction with OpenScape Business must not be exceeded. The maximum number of possible connections is reduced if the CSTA links of OpenScape Business are used by other CSTA applications.

Useful Tools

Further technical Information

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