1.2 | Operation and connection mode alternatives

1.2.1 | Operation mode alternatives

TAPI 170 operation mode alternatives

Independent from the connection mode to OpenScape Business there are different operation mode alternatives of TAPI 170 according to the TAPI applications requirements:

Telephony server based TAPI application connected to OpenScape Business via TAPI 170

| - | Installation of server application and TAPI 170 on the telephony server in the LAN.
| - | The server application provides telephony functions in the LAN for its client applications and associated users configured in TAPI 170.
| - | TAPI 170 and OpenScape Business are connected in the LAN via CSTA link of the OpenScape Business.

Client based TAPI applications connected to OpenScape Business via TAPI 170 with remote TSP functionality

| - | Installation of TAPI 170 on the telephony server in the LAN.
| - | On the client PCs containing the client applications the remote TSP functionality is activated. Client applications communicate via LAN with TAPI 170 / the telephony server.
| - | TAPI 170 and OpenScape Business are connected in the LAN via CSTA link of the OpenScape Business.
When using TAPI 170 with remote-TSP functionality several further settings on the telephony server and on the client PCs have to be considered. You find more information in the sections Additional Configurations on the telephony server (remote TSP) and Configuration on a Client PC (remote TSP).

Terminal Server based TAPI applications connected to OpenScape Business via TAPI 170

| - | With client based TAPI applications installed on one or more Terminal Server TAPI 170 is also installed on the Terminal Server. In case of a cluster build up of one ore more Terminal Server TAPI 170 is installed on every Terminal Server.
| - | Each installed TAPI 170 needs one CSTA link of OpenScape Business.
Depending on the OpenScape Business model and operating mode a maximum of three or four CSTA links are available.