OpenScape Business TAPI 170 - Revision history

Wmenn: /* SW Upgrade / Migration */

2014-07-22T12:34:27Z

‎SW Upgrade / Migration

2014-07-22T12:32:14Z

‎Software Delivery / Deployment

2014-07-22T12:31:22Z

‎Constaints

2014-07-22T12:29:05Z

‎HW/SW prerequisites

2014-07-22T12:26:48Z

‎Licensing

2014-07-22T11:06:22Z

‎Computer SW

2014-07-22T11:05:32Z

‎Prerequisites

2014-07-22T11:01:18Z

‎Compatibility

2014-07-22T10:53:13Z

‎Connecting TAPI 170 to Networked OpenScape Business Systems

2014-07-22T10:53:02Z

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

@@ Line 164: / Line 164: @@
 == 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.
 == Constraints ==

@@ Line 156: / Line 156: @@
 == 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 ==

@@ Line 169: / Line 169: @@
 HiPath TAPI 120 SW has to be uninstalled and to be replaced by OpenScape Business TAPI 120 SW on the client PC.
-== Constaints ==
+== Constraints ==
-Only Microsoft Windows operating systems can be used in conjunction with TAPI 120.<br>
+Only Microsoft Windows operating systems can be used in conjunction with TAPI 170.<br>
-For installations on terminal servers, OpenScape Business TAPI 170 must be used instead of TAPI 120.
+The TAPI server and clients must be managed by the same network domain controller, if remote TAPI function is used. <br>
 == Useful Tools ==

@@ Line 139: / Line 139: @@
 ==== 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>

@@ Line 163: / Line 163: @@
 == 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.
 == SW Upgrade / Migration ==

@@ Line 114: / Line 114: @@
 ** 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)
@@ Line 127: / Line 133: @@
-'''Note'''
+'''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 ====

@@ Line 98: / Line 98: @@
 == 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 ===
 ==== 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 ====
@@ Line 109: / Line 109: @@
 '''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
 ==== OpenScape Business ====

@@ Line 86: / Line 86: @@
 === 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
 === Supported Devices ===

@@ Line 74: / Line 74: @@
 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_TAPI170_networked.png|700px|TAPI 170 in a network]]

@@ Line 60: / Line 60: @@
 '''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.
 [[Image:OSBiz_TAPI170_terminal_server_based.png|700px|TAPI 170 Terminal-Server based TAPI Application]]