Service manual

OpenScape Business V1
Sales Information Page 39 04.06.2013
– 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
Supported Devices
TAPI 170 supports the same devices as the OpenScape Business CSTA interface.
These are described in the chapter on the CSTA Protocol.
TAPI 170 Connections
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 standalone
systems or in the OpenScape Business network.
Connecting Server-based TAPI Applications 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.
Telephony CTI Clients
„CTI Link“
CSTA at Port 8800
OpenScape
Business
TAPI 170
Server
Application
MS Windows
Domain Server
Client
Application
Client
Application
Telephony (CTI) Server
Client / Server
Links
Figure: Server-based TAPI application via TAPI 170 to OpenScape Business
Connecting Client-based TAPI Applications to OpenScape Business using TAPI 170 with
the "Remote TAPI" Function
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 software