Documentation HiPath TAPI 170 V2.0 MultiNode Installation and

Transcription

Documentation
HiPath TAPI 170 V2.0 MultiNode
Installation and Configuration
Administrator Documentation
P31003-H3540-T170-5-7619, 11/2008
Communication for the open minded
Siemens Enterprise Communications
www.siemens.com/open
Copyright © Siemens Enterprise
Communications GmbH & Co. KG 2008
Hofmannstr. 51, 80200 München
Siemens Enterprise Communications GmbH & Co. KG
is a Trademark Licensee of Siemens AG
Reference No.: A31003-H3540-T170-5-7619
Communication for the open minded
Siemens Enterprise Communications
www.siemens.com/open
The information provided in this document contains
merely general descriptions or characteristics of
performance which in case of actual use do not
always apply as described or which may change as
a result of further development of the products. An
obligation to provide the respective characteristics
shall only exist if expressly agreed in the terms of
contract. Availability and technical specifications are
subject to change without notice.
OpenScape, OpenStage and HiPath are registered
trademarks of Siemens Enterprise
Communications GmbH & Co. KG.
All other company, brand, product and service
names are trademarks or registered trademarks of
their respective holders.
Tapi170_enTOC.fm
Nur für den internen Gebrauch
Contents
Contents
0
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Setup type (environment) and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.3 Licensing and copy protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.4 Data Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.5 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.6 System connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
1.7 Hard- and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1.8 Installation medium and installation sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
2 Installing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Starting installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Installing the CMD component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Installing the CSP component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Installing the TSP component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 Installing the CCMC component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7 Installing the dongle driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8 Ending installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
2-1
2-2
2-4
2-5
2-6
2-7
2-8
2-8
3 Configuring Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Configuring the CMD component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.1 Starting the configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.2 General CMD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2.3 Advanced CMD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.4 CMD assignment parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.2.4.1 Adding nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.2.4.2 deleting an entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.2.4.3 Exporting / importing parameters (nodes) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.2.5 CMD parameters for CTI Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.2.5.1 Editing / deleting an entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.2.5.2 Adding a CSTA client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.2.6 CMD license parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.2.7 CMD version information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
3.3 Configuring the TSP component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3.3.1 Starting the configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3.3.2 General TSP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
3.3.2.1 Importing / exporting general configuration parameters . . . . . . . . . . . . . . . . 3-17
3.3.3 Advanced TSP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
3.3.4 TSP ACD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
A31003-H3540-T170-5-7619, 11/2008
HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation
0-1
Tapi170_enTOC.fm
Contents
3.3.5 TSP assignment parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.6 TSP license parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.6.1 License-free applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.7 TSP linedevice parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.7.1 Adding lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.7.2 Editing / deleting lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.7.3 Licensing linedevices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.7.4 Marking linedevices for UCD (ACD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.8 TSP version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Configuring the CSP component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Starting the configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 General CSP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 CSP mode parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4 Advanced CSP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5 CSP assignment parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.6 CSP licensing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.7 CSP version information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Configuring CCMC components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2 Configuring database parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3 Configuring general CCMC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-22
3-24
3-25
3-26
3-27
3-27
3-27
3-28
3-29
3-30
3-30
3-31
3-32
3-34
3-36
3-38
3-39
3-40
3-40
3-41
3-42
4 Additional Configurations on the Server PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 Linedevice assignment to client PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Configuring the telephone service on the server PC. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
5 Microsoft TSP Configuration on a Client PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Configuring the TSP on a client PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Entering the server name on the client PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Configuring Network Neighborhood properties . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1
5-1
5-1
5-2
A Appendix A: TAPI 170 with Terminal Server / Citrix. . . . . . . . . . . . . . . . . . . . . . . . . .
A.1 Terminal Server / Citrix overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2 TAPI 170 (Single node) on Terminal Server / Citrix:
Release and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3 Conditions for Domain Controller and Terminal Server . . . . . . . . . . . . . . . . . . . . . . . .
A.4 Special needs for Terminal Server / Citrix with >1 cluster server. . . . . . . . . . . . . . . . .
A.5 Terminal-Server / Citrix and HiPath 5000 RSM (Multi node) . . . . . . . . . . . . . . . . . . . .
A-1
A-2
A-3
A-4
A-5
A-6
List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Y-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
0-2
A31003-H3540-T170-5-7619, 11/2008
tapi170_enEinl.fm
1
Introduction
1.1
General
Introduction
General
The product consists of the following software components:
●
HiPath TAPI 170 TAPI Service Provider (TSP)
HiPath TAPI 170 TSP is a third-party telephony service provider software based on MS
Windows Server that supports Microsoft's remote TAPI concept (TAPI 2.1).
HiPath TAPI 170 TSP enables TAPI-based applications to have the control and status/presence display of telephones connected to a HiPath system.
It can be set up either as a separate system (Single node) or in connection with HiPath
5000 RSM in a networked system environment (Multi node).
●
CSTA Service Provider (CSP)
The CSTA service provider interacts with an application and maps CSTA links from multiple
HiPath systems in a network to a logical CSTA.
This allows applications to control the phones of all connected HiPath systems via the CSP.
●
CSTA Message Dispatcher CMD
The CSTA links of multiple applications are merged on the CSTA interface on a HiPath system using the CSTA message dispatcher.
●
Central Configuration Manager Client (CCMC)
Synchronizes the data between the TAPI PC configuration database and the HiPath server
configuration database.
Communicating within the network
Once TAPI 170 has been installed and activated, TAPI functions are available on all TAPI clients
connected to this server. The TAPI-compliant software applications installed on the client PCs
can use the TAPI functions in the same way as when using TAPI 1st Party Service Provider.
Communication between server and client is completely transparent and is performed by Microsoft-defined interfaces.
Operational reliability
The TAPI 3rd Party Service Provider model with a central service provider requires a high level
of operability. This is achieved via CSTA interface monitoring using a so-called heartbeat function and a permanently activated consistency check for fast recognition and release of blocked
resources.
Documentation
●
Various abbreviations are used in this document to improve readability. An overview of all
abbreviations can be found in the List of abbreviations.
A31003-H3540-T170-5-7619, 11/2008
1-1
tapi170_enEinl.fm
Introduction
General
●
To improve readability, "telecommunications system(s)" has been abbreviated to "system(s)" in this document.
●
The product name has also been abbreviated to TAPI 170 for the same reason.
1-2 HiPath TAPI 170 V2.0 MultiNode Installation and
A31003-H3540-T170-5-7619, 11/2008
Configuration, Administrator Documenta-
tapi170_enEinl.fm
1.2
Introduction
Setup type (environment) and components
Setup types (environment)
As an individually marketed product, TAPI 170 can be used with one system / one server (Single node setup type or single node environment) or can be used in conjunction with several systems / servers (multi node setup type or multi node environment). Basic operation is identical.
However, the scope of the relevant TAPI 170 components varies depending on the node environment.
Configuration of TAPI 170 in Single node environment
For single node environment the TAPI 170 server PC, where TSP is installed, communicates
directly with a single HiPath system, using Ethernet LAN and CSTA protocol.
PC clients in a network with the TAPI applications are in the same domain as the TAPI 170 server with the TSP, and access the TAPI server PC via Microsoft's remote TAPI functionality.
A31003-H3540-T170-5-7619, 11/2008
1-3
tapi170_enEinl.fm
Introduction
Configuration of TAPI 170 in Multi node environment (HiPath 5000 RSM)
TSP in Multi node environment
●
TSP must be installed on the server PC with HiPath 5000 RSM for multi node environment.
●
TSP communicates via Ethernet LAN and CSTA protocol with each individual HiPath system in a multi node environment. Station data for the HiPath systems connected in the network is retrieved from the HiPath 5000 RSM database. If station data is changed in the network, TSP is automatically notified of the change.
●
PC clients with TAPI applications in the network must be located in the same domain as
the HiPath 5000 RSM server with TSP. They access this server PC via Microsoft's remote
TAPI functionality.
A31003-H3540-T170-5-7619, 11/2008
tapi170_enEinl.fm
Introduction
CSP in Multi node environment
●
This scenario takes effect when the CSTA interfaces of the systems in the network must
be concentrated on a single CSTA link.
●
The CSTA application on the application server exclusively accesses the CSTA link of the
CSP component. This component first arranges the CSTA events from all connected systems in the same sequence as in a standalone HiPath system and presents them to the
CSTA application. Applications thus overlook whether the CSTA interface is operated on a
standalone HiPath system or networked systems.
●
CSTA multi node connection always requires a HiPath 5000 RSM system, as well as the
CSP and CMD components.
●
In a multi node environment, the CSP first communicates with a CMD, which is then connected to each individual HiPath system via Ethernet LAN and CSTA protocol.
●
CSP components retrieve station data for the HiPath platforms connected in the network
from the HiPath 5000 RSM database. If station data is changed in the network, the CSP
components are automatically notified of the change.
●
Application client PCs in the network access the application server via application-specific
mechanisms.
TAPI 170 components
The following TAPI 170 components are installed irrespective of the solution:
A31003-H3540-T170-5-7619, 11/2008
1-5
tapi170_enEinl.fm
Introduction
●
TSP (TAPI Service Provider)
This component will be installed for single node and multi node environment by default.
●
CMD (CSTA Message Dispatcher)
This component will be installed for multi node environment by default.
●
CSP (CSTA Service Provider)
●
CCMC (Central Configuration Manager Client)
●
Dongle driver
Required for installing (updating) TAPI versions licensed via TAPI 170 V1.0 dongle licensing.
You can select this component for installation with the setup type Custom. The dongle driver is not installed if license codes are used for licensing.
See also:
Installation medium and installation sequence
A31003-H3540-T170-5-7619, 11/2008
tapi170_enEinl.fm
1.3
Introduction
Licensing and copy protection
Licensing and copy protection
General
Licenses are required for operating the TAPI 170 components installed. The license codes must
be entered during configuration.
License monitoring of TAPI 170 applications
●
TSP 170
– Licensing of TAPI linedevices through TSP170
– For compatibility reasons, licensing of TAPI 170 can be supported furtheron using the
dongle and license strings of the pre-version TAPI 170 V1.0 or Hicom CTI TAPI 3P
V2.0/V2.1.
●
TSP 120
– Licensing of TAPI linedevices within CMD
– Operating without CMD no license monitoring takes place. The maximum number of
TSP 120 clients then is determined with the connected system.
●
CMD
– Operation of CMD takes place without license monitoring.
●
CSP
– Licensing of CSTA application links within CSP
A31003-H3540-T170-5-7619, 11/2008
1-7
tapi170_enEinl.fm
Introduction
Data Synchronization
1.4
Data Synchronization
For a simplified TAPI 170 configuration in multi node environment data is synchronized via the
CCMC component.
●
Configuration data in HiPath 5000 RSM data base (feature provider database) and the local HiPath TAPI 170 data base (mdb) are synchronized.
A31003-H3540-T170-5-7619, 11/2008
tapi170_enEinl.fm
1.5
Introduction
Features
Features
The following features are available depending on the system installed and the support provided for the TAPI applications used.
Features of TSP components
●
●
●
●
●
●
●
●
●
●
●
●
Outgoing connection setup, incoming call acceptance, call cleardown
Call status/caller ID display
Call logging
Call pickup (group), consultation hold, toggling, call transfer, conference
Speed transfer, call redirect, call hold
Tone dialing (DTMF) during call
Call charge information
Write to display
Set/query hookswitch status
Volume setting for handset, speaker and headset
Lamp mode setting
Call center features:
– Query/set/cancel message waiting indicator
– Query/set/cancel call forwarding and do not disturb
– Additional information on forwarded/redirected/ transferred calls
– Playback of music on hold (MOH) and recorded announcements (RCA)
– Trunk monitoring
– UCD monitoring
– Call status timer
– Unique caller ID (domain-wide)
– Call data exchange between TAPI applications (domain wide)
TSP features (TAPI extended services)
●
●
Support for ACD proxy request handler
Heartbeat/loopback
>
●
●
Not every feature is available on every system.
You can only use features that are supported by the TAPI application.
A31003-H3540-T170-5-7619, 11/2008
1-9
tapi170_enEinl.fm
Introduction
System connection
1.6
System connection
TCP/IP is generally used for connecting TAPI 170 components to each other or to the system(s).
A31003-H3540-T170-5-7619, 11/2008
1-10HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documenta-
tapi170_enEinl.fm
1.7
Introduction
Hard- and software requirements
Hardware requirements for server and client PCs
The hardware requirements are specified by Microsoft for Windows 2000 Professional / Server
PCs, Windows XP Professional PCs and Windows 2003 Server PCs. For further information,
please consult the Windows documentation.
Software requirements for the server PC
●
Windows 2000 Server
●
or Windows 2003 Server
●
or Windows 2008 Server
>
For TAPI 170 on a server PC with Terminal Server / Citrix please consider information given in the section Appendix A: TAPI 170 with Terminal Server / Citrix.
Software requirements for client PCs
●
Windows 2000 Professional
●
or Windows XP Professional
●
or Windows Vista (excluding Home versions)
>
Furthermore, only 32-bit operation systems are supported for the server and the client PCs.
>
When using Microsoft Vista different confirmation prompts might appear during TAPI
170 configuration. Furthermore the TAPI 170 configuration dialogs are possibly displayed in the background after initiation. Then you can activate them using the task
bar.
Other requirements
●
Network protocol: TCP/IP must be installed and configured.
●
The server and client PCs must be members of the same Windows domain.
●
NETBIOS must be activated for reading the MAC ID.
●
The server PC must have a fixed IP address (also when using DHCP).
A31003-H3540-T170-5-7619, 11/2008
1-11
tapi170_enEinl.fm
Introduction
●
Installation of TAPI 170 must be executed by an user with administration and domain administration rights.
●
For operation the telephone service on the server PC a user account with administrator
and domain administration rights is required.
●
File and printer sharing must be activated.
Overview of used TAPI 170 ports (default)
Port number Description
7001
CSTA-link to the system
8001
CSTA-link to CMD
8800
CSTA-link to CSP
8503
IP port for data synchronisation of TSP
Limitations
Operating TAPI 170 and TAPI 120 on the same PC is not possible.
A31003-H3540-T170-5-7619, 11/2008
tapi170_enEinl.fm
Introduction
1.8
Installing TAPI 170
Either an installation CD is provided or the software can be downloaded from the software supply center.
Contents of the TAPI 170 installation CD
The TAPI 170 installation CD contains these folders:
File / folder
Description
\Diehl_NT_2.36
Contains the USB-compliant CAPI drivers for the DIVA
Pro 2.0 ISDN card for Windows NT.
\Diehl_w2k
Pro 2.0 ISDN card for Windows 2000.
\Diehl_w2k3
\Diehl_w2k_diva30
\doc
Contains documentation for customers and developers.
\MS
Contains the Microsoft documentation for TAPI configuration.
\Setup
Contains the TAPI 170 installation files.
\Tools
Contains files for different TAPI 170 tools.
Installation sequence
As the installation can include different components from various vendors, the following installation sequence must be observed.
1.
Installing Components
2.
Configuring Components
3.
Linedevice assignment to client PCs
4.
Configuring the telephone service on the server PC
5.
Configuring the TSP on a client PC
A31003-H3540-T170-5-7619, 11/2008
1-13
tapi170_enEinl.fm
Introduction
Following the installation of a component the configuration dialog of this component is displayed directly. Thus you can determine the necessary parameters during the setup. Alternatively you can configure the parameters after seutp completition.
You define the components to be installed by selecting a setup type or by selecting the components directly with custom installation. The setup determines the sequence of the components
installation.
>
During setup, the selected number and type of components are installed, i.e., unselected components are deinstalled, selected components are installed or updated.
See also:
Configuring the CMD component
Configuring the TSP component
Configuring the CSP component
Configuring CCMC components
A31003-H3540-T170-5-7619, 11/2008
tapi170_enInstallation.fm
2
2.1
General
General
Scope of installation
The components to be installed can be selected directly or indirectly when installing TAPI components. The following components andare available:
●
CMD
●
CSP
●
TSP
●
CCMC
●
Dongle driver
See also:
Installing the CMD component
Installing the CSP component
Installing the TSP component
Installing the CCMC component
Installing the dongle driver
Installation and configuration
If several components are selected for installation, the individual installation routines and dialogs for entering the configuration parameters may be automatically started one after the other.
In the present document, installation procedures are described in Installing Components and
configurable parameters are described in Configuring Components.
A31003-H3540-T170-5-7619, 11/2008
2-1
Starting installation
2.2
1.
Log on as an administrator and close all running applications.
2.
Insert the TAPI 170 installation CD.
3.
Select the setup.exe file on the installation drive under Start - Run and confirm with OK.
The Welcome dialog is displayed. Click Next to confirm. The installation setup type must
then be specified:
Display
The relevant installation components are automatically assigned once the Single node
and Multi node setup types have been selected.
Components
TSP
CMD
CSP
CCMC
Dongle
driver
Single node
✓
-
-
-
-
Multi node
✓
✓
✓
✓
-
(✓)
(✓)
(✓)
(✓)
(-)
Setup type
Custom
The components to be installed can be selected manually in the customized setup dialog
displayed once the Custom setup type has been selected. This is useful, for example, if
deviations from the standard scope of installation have to be taken into account for individual components.
2-2
A31003-H3540-T170-5-7619, 11/2008
4.
>
The dongle driver is only relevant for TAPI 170 installations that are licensed via
the dongle. Mac IDs and license codes are used for licensing initial installations
of TAPI 170 version 2.0 or later. A dongle driver is not generally required.
>
In an update installation, the installed components are detected automatically.
After the initial installation is completed, the dialog for a custom installation can
be opened at any time and independently of the update installation by clicking
Control Panel - Add/Remove Programs (select the HiPath TAPI 170 SP V2
entry). Please note, however, that a custom installation performed via the Control Panel will override the existing installation, i.e., all installed components that
are not explicitly selected in the custom installation dialog will be uninstalled.
Click Next to confirm your selection.
Installation of the selected components is started.
Standard scope of installation for TAPI 170
●
Setup type Single node:
– Installing the TSP component
●
Setup type Multi node:
– Installing the CMD component
– Installing the TSP component
– Installing the CSP component
– Installing the CCMC component
Activating the ACD service
A message prompting activation of ACD support is displayed at the start of the TAPI 170 installation routine (the exact time is dependent on the installation components selected). To activate
the ACD service, click Yes.
>
The corresponding service for ACD support can be activated or deactivated at a later
stage. Activate the Service Control Manager (Control Panel - Services) and select
the required service ACD 3Service setting for the service.
A31003-H3540-T170-5-7619, 11/2008
2-3
2.3
The CMD component is included in the standard scope of installation for Multi node environment or after customized selection.
1.
A welcome dialog is not displayed when installing the CMD component. Progress is displayed in a window.
2.
The CMD configuration dialog opens automatically following successful CMD installation.
The required parameters can be entered in this dialog or configured at a later stage.
Display
The individual configuration parameters are described under Configuring the CMD component.
CMD installation is complete once you have exited the configuration dialog. Further components may now be installed automatically depending on the setup type selected.
2-4
A31003-H3540-T170-5-7619, 11/2008
2.4
The CSP component is included in the standard scope of installation for Multi node environment or after customized selection.
1.
A welcome dialog is not displayed for installing the CSP component.
2.
The CSP configuration dialog opens automatically following successful CSP installation.
Display
The individual configuration parameters are described under Configuring the CSP component.
CSP installation is complete once you have exited the configuration dialog. Further components may now be installed automatically depending on the setup type selected.
A31003-H3540-T170-5-7619, 11/2008
2-5
2.5
The central TSP component is included in the standard scope of installation for the setup types
Single node and Multi node.
1.
Click Next to confirm the TSP welcome dialog.
TSP installation is then started and progress is displayed in a window.
2.
If your PC has multiple network cards (and thus multiple IP addresses), you will be prompted to select the IP address to be used.
3.
The TSP configuration dialog opens automatically following successful TSP installation.
Display
The individual configuration parameters are described in detail under Configuring the TSP
component.
TSP installation is complete once you have exited the configuration dialog. Further components
may now be installed automatically depending on the setup type selected.
2-6
A31003-H3540-T170-5-7619, 11/2008
2.6
The CSP component is included in the standard scope of installation for Multi node environment or after customized selection.
1.
A Welcome dialog is not displayed for installing the CCMC component.
2.
The CCMC options configuration dialog opens automatically following successful installation. The required parameters can be entered in this dialog or configured at a later stage.
Display
The individual configuration parameters are described under Configuring CCMC components.
CCMC installation is complete. Further components may now be installed automatically depending on the setup type selected.
A31003-H3540-T170-5-7619, 11/2008
2-7
2.7
>
Installation of the dongle driver is only necessary for reasons of compatibility if the
TSP was licensed via dongle in a previous version (TAPI 170 V1.0 or
HICOM CTI TAPI 3P V2.0/V2.1).
The dongle driver is automatically installed in a command prompt window without any further
user commands. This window closes automatically following installation.
Further components may now be installed automatically depending on the setup type selected.
2.8
Ending installation
A completion dialog is displayed following installation of all selected components. Click Finish
to end installation.
2-8
A31003-H3540-T170-5-7619, 11/2008
tapi170_enKonfiguration.fm
3
3.1
General
General
Manual activation of configuration dialogs
The individual component parameters can be configured during installation or at a later stage.
How to start the configuration dialog after installation is described in these sections:
●
●
●
●
Effectiveness of modified configuration parameters
Modified configuration of user parameters are immediately effective once the data has been
saved in the configuration dialog (Apply or OK buttons).
It is necessary to restart the TSP (net stop tapisrv), for instance after modifying the connection
type (CSTA link).
A31003-H3540-T170-5-7619, 11/2008
3-1
3.2
3.2.1
Starting the configuration dialog
Activating the configuration dialog
To edit the CMD configuration parameters after installation, start the configuration dialog as follows:
1.
Open the Windows Control Panel via Start - Settings - Control Panel.
2.
Activate the CSTA Message Dispatcher by double-clicking the associated icon.
The CMD configuration dialog is then displayed.
>
When using Microsoft Vista different confirmation prompts might appear during
CMD configuration. Furthermore, the configuration dialogs are possibly displayed in
the background after initiation. Then you can activate them using the task bar.
Configuration parameters
You can configure this parameters:
–
General CMD parameters
–
Advanced CMD parameters
–
CMD assignment parameters
–
CMD parameters for CTI Firewall
–
CMD license parameters
Up-to-date CMD version information can be found in the configuration dialog.
3-2
A31003-H3540-T170-5-7619, 11/2008
3.2.2
General CMD parameters
The type of system connected, the type of connection between the CMD and the system and
the relevant connection parameters must be determined when configuring the general CMD
parameters.
>
Activate the General tab in the CMD configuration dialog.
Display
These parameters and information is displayed:
Parameter
Description
System
For selecting the connected system. The following systems can be selected:
●
HiPath OpenOffice EE
●
HiPath 2000
●
HiPath 3000
●
HiPath 5000 RSM (default)
CSTA link
Connection type between CMD and the system. By default this is
TCP/IP and cannot be changed.
Call number
Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant.
CAPI-DLL
A31003-H3540-T170-5-7619, 11/2008
3-3
Parameter
Description
CAPI controller
Baud rate
CMD IP port
Connected to HiPath 5000 RSM (Multi node) this field is inactive. parameter is nor relevant. You onfigure this parameter in the Assignment tab.
>
If the system is changed, a message may appear indicating that the licensing information may have been changed. If this occurs, the licensing information for the new
system must be checked.
Saving parameters
●
To save entries, click Apply (to configure parameters in other tabs for example) or OK (to
exit the configuration dialog and save changes).
●
A confirmation message appears in both cases before the parameter values are saved in
the database. Click Yes to confirm this message.
3-4
A31003-H3540-T170-5-7619, 11/2008
3.2.3
Advanced CMD parameters
The advanced CMD parameters are determining settings relevant for to the connection between the connected system and the CMD. System-dependent parameters are defined on the
system and should be specified here accordingly.
>
Activate the Advanced tab in the CMD configuration dialog.
Enter the following parameters:
Parameter
Description
CSTA3 user
CSTA3 user name of the system.
Entering a name opens an input dialog in which you can
determine and confirm the new name, then return to the
configuration dialog.
CSTA3 password
CSTA3 system password.
Entering a password opens an input dialog in which you
can determine and confirm the new password, then return
to the configuration dialog.
>
CSTA-Login on the system is not possible if the CSTA3 password entered here
does not correspond to the system password.
Parameter
Description
Heartbeat period (s)
Time interval (seconds) for checking CSTA interface activity. The value 0 disables the check.
The default value is 15 seconds and should not be
changed.
Heartbeat timeout (s)
Additional time in seconds until automatic re-estalishment
in the case of CSTA interface failure.
The default value is 10 seconds and should not be
changed.
Consistency check period
(s)
Time interval in seconds for cyclical plausibility checks.
The value 0 disables the check.
The default value 60 seconds should not be changed.
CSTA reestablish period (s) CMD waiting time in seconds until a connection is re-established following connection failure.
The default value is 120 seconds.
CSTA invoke timeout (s)
CMD timeout in seconds.
A31003-H3540-T170-5-7619, 11/2008
3-5
Parameter
Description
Transmission interval (ms)
Waiting time between two CMD messages.
The default value is 50 ms.
Trace
With TCP/IP connection of the CMD this parameter is not
relevant. You must define the trace option for each of the
connected systems when configuring the assignment parameters.
See also CMD assignment parameters.
Saving parameters
>
>
3-6
A31003-H3540-T170-5-7619, 11/2008
3.2.4
CMD assignment parameters
When configuring the assignment parameters, you assign the systems connected to the CMD
via the CMD Listener Ports on the Assignment tab.
>
Activate the Assignment tab in the CMD configuration dialog.
Display
A list of assigned CMDs/systems is displayed with this information:
Column/field
Description
Name
System description, entered during installation/configuration (KDS) - usually the customer name and / or location.
V-Node ID
Node ID of the system connected to the CMD. The node
ID is entered during system installation/configuration and
is unique in the network.
Node IP address
Node IP address of the system connected to the CMD.
Node port
IP port number of the system, always set to 7001.
CMD IP port
CMD Listener Port port number to be configured for the
system, e.g. 8001, 8002, etc.
Trace
Option for activating trace messages (CSTA messages) for
the assigned system that can be interpreted using a separate standard tool.
A31003-H3540-T170-5-7619, 11/2008
3-7
Sorting the list displayed
The list can be sorted in ascending/descending order according to column content by clicking
the relevant column heading, e.g. Name.
Saving parameters
>
>
the registration database. Click Yes to confirm this message.
3.2.4.1
Adding nodes
>
Click Add in the Assignment tab.
>
A list of all assigned nodes including the entries from the central database is displayed
containing the following information:
Column/field
Description
Node ID
Node ID of the system connected to the CMD. The node
ID is entered during system installation and configuration
and is unique in the network.
Node Name
System description, entered during installation / configuration (KDS) - usually the customer name and / or location.
Node IP
Node IP address of the system connected to the CMD.
Node Port
IP port number of the system, always set to 7001.
CMD Port
CMD Listener Port port number to be configured for the
system, e.g. 8001, 8002, etc.
Individually select the nodes you want to make available for the CMD, multiple selection is
possible using the keyboard or mouse. Click Mark All to highlight all list entries.
3.
Click Add to accept the selected entries followed by Close to exit the list window. The CMD
configuration dialog re-appears.
4.
Click Apply to save entries. You can then enter additional parameters for other systems.
Click OK to save changes and exit the entry dialog. The CMD configuration dialog re-appears.
A maximum of 64 systems/nodes can be configured.
3-8
A31003-H3540-T170-5-7619, 11/2008
3.2.4.2
deleting an entry
Deleting an entry
>
Highlight the entry to be deleted using the mouse and click Delete or press the * key.
The entry is then deleted from the list.
3.2.4.3
Exporting / importing parameters (nodes)
Exporting
1.
The configured node information can be exported to a file, e.g. to save a specific level. Click
Nodes Export to start exporting.
2.
Enter the name of the export file in the dialog displayed and confirm.
The entries are exported. The CMD configuration dialog re-appears.
Importing
1.
Node parameters can also be imported from a file, e.g. containing exported parameter information. Click Nodes Import to start importing.
2.
Select the file to be imported.
The entries are imported and the CMD configuration dialog re-appears.
A31003-H3540-T170-5-7619, 11/2008
3-9
3.2.5
CMD parameters for CTI Firewall
Every CSTA client (e.g. TAPI 120) that is connected to the CMD and permitted to seize a linedevice, must be entered in the CTI Firewall tab to enable this access.
>
Activate the CTI Firewall tab in the CMD configuration dialog.
You will see a list of the CSTA clients (IP addresses) already configured for access:
Display
Entries are displayed with the following information:
Column
Description
Name
Freely chosen name for the CSTA client (e.g. TAPI 120), enabling a single entry in the firewall to be identified.
Call number
Enter the call number of the CSTA client.
TAPI 120 IP addresses
Enter the IP address of the CSTA client.
The list can be sorted in ascending/descending order according to column content by clicking
the relevant column heading, e.g. Name.
Saving parameters
>
3-10
A31003-H3540-T170-5-7619, 11/2008
>
3.2.5.1
Editing / deleting an entry
Editing an entry
>
To edit the parameters of an entered CSTA client, double-click the corresponding value.
The value can then be changed in the entry field displayed.
Deleting an entry
>
3.2.5.2
Adding a CSTA client
Add a CSTA client
1.
Click Add in the CTI Firewall tab.
2.
Enter the data of the CSTA client in the input dialog and confirm with OK. You return to the
CTI Firewall tab.
An unlimited number of clients can be entered on this tab. However, please note that the number of clients permitted to seize linedevices at the same time is limited by the licensing agreement.
See also:
Deleting an entry
>
A31003-H3540-T170-5-7619, 11/2008
3-11
3.2.6
Access by CSTA clients (e.g. TAPI 120) via the CMD to the connected system is protected by
a licensing procedure. You can obtain information on the current license as well as any license
history that may exist. If available the administrator can enter a new license code here.
>
Activate the License tab in the CMD configuration dialog.
Display
The parameters contain the following information:
3-12
Parameter
Description
MAC ID
MAC ID, used for encryption.
This is the MAC ID of the first LAN interface in the system
network.
Current license
Current license code for licensing.
The administrator can download this key from the license
server and enter a new license code. If a license is changed,
the license key entered will be checked. Old keys are recorded in the license history. If the wrong license key is entered, no licenses are used.
Date
Limit date
Licenses
Details of license date, limit date and number of licenses
with the current license code.
License History
Previous licenses are displayed here with the relevant information.
A31003-H3540-T170-5-7619, 11/2008
Saving parameters
●
●
3.2.7
CMD version information
The version numbers of the components that are used and installed are listed in the Version
tab.
A31003-H3540-T170-5-7619, 11/2008
3-13
3.3
3.3.1
To edit TSP configuration parameters after installation, start the configuration dialog as follows:
1.
Open the Windows 2000 Control Panel via Start - Settings - Control Panel.
2.
Activate Telephone and Modem Options by double-clicking the associated icon.
3.
The Phone and Modem Options dialog is displayed.
–
Activate the Advanced Options tab
–
Select the entry HiPath TAPI 120/170 TAPI 2.0 SP from the list of providers displayed
–
and click Configure.
The TSP configuration dialog appears.
>
3-14
When using Microsoft Vista different confirmation prompts might appear during TSP
configuration. Furthermore, the configuration dialogs are possibly displayed in the
background after initiation. Then you can activate them using the task bar.
A31003-H3540-T170-5-7619, 11/2008
The following parameters can be edited during TSP configuration:
–
General TSP parameters
–
Advanced TSP parameters
–
TSP ACD parameters
–
TSP assignment parameters
–
TSP license parameters
–
TSP linedevice parameters
Up-to-date TSP version information can be found in the configuration dialog.
A31003-H3540-T170-5-7619, 11/2008
3-15
3.3.2
General TSP parameters
The type of system connected, the type of connection between the TSP and the system and
the relevant connection parameters must be specified when configuring general TSP parameters.
>
Activate the General tab in the configuration dialog.
Display
3-16
Parameter
Description
System
For selecting the connected system. The following baud rates can be
selected:
– HiPath OpenOffice ME
– HiPath OpenOffice EE
– HiPath 2000
– HiPath 3000
– HiPath 5000 RSM (Multi node) (default)
CSTA link
Connection type between TSP and the system. By default this is TCP/
IP and cannot be changed.
Call number
CAPI-DLL
A31003-H3540-T170-5-7619, 11/2008
Parameter
Description
CAPI controller
Baud rate
IP address
With connection to the HiPath 5000 RSM (Multi node) system, this parameter cannot be modified. You administrate the IP addresses of the
connected systems in the Assignment tab.
IP port
With connection to the HiPath 5000 RSM (Multi node) system, this parameter cannot be modified. You administrate the IP port of the connected systems in the Assignment tab.
>
If the System is changed, a message may appear indicating that the licensing information may have been changed. If this occurs, the licensing information for the new
system must be checked.
Saving parameters
>
>
>
It is necessary to re-start the TSP (net stop tapisrv), for instance after modifying the
connection type (CSTA link).
3.3.2.1
Importing / exporting general configuration parameters
Exporting
1.
The configured general configuration parameters can be exported to a file, e.g. to save a
specific level. Click Nodes Export to start exporting.
2.
Enter the name of the export file in the dialog displayed and confirm.
The entries are exported. The TSP configuration dialog re-appears.
A31003-H3540-T170-5-7619, 11/2008
3-17
Importing
1.
General configuration parameters can also be imported from a file, e.g. containing exported parameter information. Click Nodes Import to start importing.
2.
Select the file to be imported.
The entries are imported and the TSP configuration dialog re-appears.
3-18
A31003-H3540-T170-5-7619, 11/2008
3.3.3
Advanced TSP parameters
When configuring advanced TSP parameters, you are configuring parameters that are relevant
to the connection between the connected system and the TSP. System-dependent parameters
are defined on the system and should be specified here accordingly.
>
Activate the Advanced tab in the configuration dialog.
Display
Parameter
Description
Additional time in seconds until automatic re-installation
Consistency check period (s) Time interval (in seconds) for cyclical plausibility checks.
Trunk access code start
Trunk access code end
●
RCA port start
RCA port end
First and last port for announcement devices in accordance with configuration on the system.
With connection to the HiPath 5000 RSM (Multi
node) this parameter is not relevant.
A31003-H3540-T170-5-7619, 11/2008
3-19
Parameter
Description
RCA choice by index
This option must be activated to enable use of the ACD
announcement function.
Trace
Option for activating trace messages (CSTA messages)
that can be interpreted using separate standard debugging tools.
CSTA reestablish period (s)
TSP waiting time (in seconds) until a connection is re-established following connection failure. The default value is
20 seconds.
TSP timeout (in seconds)
TSP waiting time between two messages.
IP port data synchronization
IP port for recording the central database synchronization
pulse.
The default value is 8503.
CSTA3 user
CSTA3 user name of the system.
To record a change of the system user name here as well,
enter the new user name. Entering the name immediately
opens an input dialog in which you can enter and confirm
the new name, then return to the configuration dialog.
CSTA3 password
CSTA3 system password.
To record a change of the system password here as well,
enter the new password. Entering the password immediately opens an input dialog in which you can enter and
confirm the new password, then return to the configuration dialog.
>
CSTA-Login on the system is not possible if the CSTA3 password entered here
does not correspond to the system password.
Saving parameters
>
>
3-20
A31003-H3540-T170-5-7619, 11/2008
3.3.4
TSP ACD parameters
In the ACD tab you can specify parameters relevant to ACD and obtain information on ACD
functionality, or you can activate the ACD service in order to obtain this information.
>
Activate the ACD tab in the configuration dialog.
Display
>
The current ACD status and the number of ACD groups and agents (as configured in the
TSP line parameters, see TSP linedevice parameters) are displayed in the output field if
the ACD service is activated. If no information is displayed, click the Load data button.
This starts the ACD service and gathers and displays the information.
>
When using the ACD Busy signal option, you can determine whether or not the „Agent
busy“ status should be relayed to the TAPI ACD application.
>
This option must not be activated for use with HiPath Pro Center Office (HPCO),
as HPCO cannot process these messages.
Saving parameters
>
>
A31003-H3540-T170-5-7619, 11/2008
3-21
3.3.5
TSP assignment parameters
Configure the node parameters for connecting the TSP to the HiPath 5000 RSM (Multi node)
system in the Assignment tab.
>
Activate the Assignment tab.
Display
A list of assigned systems is displayed indicating this information:
Column/field
Description
Name
System description (from KDS) - usually the customer
name and / or location.
V-Node IDs
Node ID of the system (see system configuration)
IP address
IP address of the system (see system configurstion).
IP port
Port number of the system
Adding node IDs
1.
Click Add in the Assign tab.
2.
A list of all configured nodes is displayed. Select the nodes you wish to make available for
the TSP. Multiple selection is possible using the keyboard/mouse. To highlight all list entries
click Select All.
3.
Click Add to accept the selected entries followed by Close to exit the list window. The TSP
3-22
A31003-H3540-T170-5-7619, 11/2008
Deleting an entry
Highlight the entry to be deleted using the mouse and click Delete or press the b key. The
entry is deleted once the security prompt has been confirmed.
The list of V-Node IDs can be sorted in ascending/descending order according to column content by clicking the relevant column header, e.g., Name.
Saving parameters
>
>
A31003-H3540-T170-5-7619, 11/2008
3-23
3.3.6
This configuration dialog displays information on current TSP licensing and is applicable to applications that are subject to license. There are also license-free applications.
See also License-free applications).
>
Activate the license tab in the configuration dialog.
Display
Parameter
Description
MAC ID
MAC ID that is used for encryption.
This is the MAC ID of the first LAN interface in the system network.
Current license
Current license code for licensing.
The administrator can download this key from the license server and enter a new license code. If a license is changed, the license key entered
will be checked. Old keys are recorded in the license history. If the wrong
license key is entered, no licenses are used.
Date
Limit date
Licenses
license date, limit date and number of licenses with the current license
code.
Licenses for the
neutral line
Maximum number of licenses available with the neutral line. The neutral
line enables applications to seize linedevices at renting.
License History
3-24
A31003-H3540-T170-5-7619, 11/2008
>
To start TSP in demo mode, enter the text DEMOMODE instead of a licence key in the
Current Licence field. The TSP is switched into demo mode, with three freely configurable linedevices available for 2 hours. Afterwards, and once the 2 hours have
elapsed, the PC must be re-started.
Saving parameters
>
>
3.3.6.1
License-free applications
The following applications can be used without a license:
●
Personal Call Manager
●
GetAccount
●
HiPath Pro Center Office
●
Presence Manager
●
HiPath Pro Center Compact
A31003-H3540-T170-5-7619, 11/2008
3-25
3.3.7
TSP linedevice parameters
With configuring the longevity parameters you determine the different TSP linedevices and / or
TSP users.
Lines are assigned to the client PCs at a later stage in the case of a TAPI 170 Single node environment.
See also Linedevice assignment to client PCs
>
>
“Linedevices” correspond not only to callnumbers of agents or stations, but also to
UCD group call numbers or CO-trunk codes, etc.
Activate the Linedevices tab in the configuration dialog.
Display
Configured linedevices (TSP users) are listed in the dialog displayed under Call Number,
Name, licensed Line ID and ACD ID. The list of configured linedevices shows the total
number of linedevices, the total number of licensed linedevices as well as the number of
available licenses.
The Neutral Line serves as a reproduction tool for applications and adds linedevices while
the program is active. The settings for ACD marking are also used for the reproduced
linedevices. The settings for licensing the neutral line are not performed here, but in the
license tab (see also TSP license parameters). Any attempt to edit the licensing options
for the neutral line will produce an alert message.
3-26
A31003-H3540-T170-5-7619, 11/2008
The list of lines can be sorted in ascending/descending order according to column content by
clicking on the relevant column heading, e.g. Call Number.
Saving parameters
>
>
3.3.7.1
Adding lines
1.
Click Add in the Linedevices tab.
2.
A list of all call numbers configured for the connected system is displayed. Individually select the required entries (multiple selection is possible using the keyboard or mouse). Click
Select All to highlight all list entries.
3.
Click Add to accept the selected entries followed by Close to exit the list window. The TSP
>
3.3.7.2
Each additional linedevice uses resources on the TSP server. For this reason,
linedevices that are not required by the application should not be added.
Editing / deleting lines
Editing linedevices
To change the linedevice name, double-click the corresponding value. The value can then be
changed in the entry field displayed.
Deleting linedevices
1.
Click the entry to be changed.
2.
Then click Delete or press the * key. The entry is deleted.
3.3.7.3
Licensing linedevices
If linedevices should be used by a non-HiPath application, they must be licensed.
A31003-H3540-T170-5-7619, 11/2008
3-27
●
For licensing, select the license option for the relevant linedevice under licensed Line
(checkmark). If there are no more licenses available, a corresponding message appears
when selecting the option.
●
Delete the checkmark under licensed Line to cancel a linedevice license.
The settings for licensing the neutral line are not performed here, but in the license tab. Any
attempt to edit the licensing options for the neutral line will produce an alert message.
Licensed linedevices can then also be opened by other applications which are not featured in
the licence-free application s list.
See also:
License-free applications
3.3.7.4
>
Marking linedevices for UCD (ACD)
The UCD agent function in the Call Center requires that the appropriate lines are
marked for ACD, i.e., the option described must be selected.
●
To mark a linedevice as an UCD agent, select the ACD option for the relevant line under
ACD (checkmark).
●
To remove the ACD agent marking, delete the checkmark under ACD.
Linedevices that are marked with a grey checkmark in the ACD option are automatically marked
as UCD agents, e.g. if a station registers with an UCD group for the first time.
>
3-28
ACD marking uses resources on the server. For this reason, ACD marking for the
relevant linedevices should only be activated if requested by the application.
A31003-H3540-T170-5-7619, 11/2008
The number of UCD groups or UCD agents (excluding trunks) marked for ACD is also displayed
in the ACD tab.
See also
TSP ACD parameters
3.3.8
TSP version information
tab.
A31003-H3540-T170-5-7619, 11/2008
3-29
3.4
3.4.1
1.
2.
Activate the CSTA Service Provider by double-clicking the icon.
The CSP configuration dialog appears.
The following parameters can be edited during CSP configuration:
–
General CSP parameters
–
CSP mode parameters
–
Advanced CSP parameters
–
CSP assignment parameters
–
CSP licensing parameters
Up-to-date CSP version information can be found in the configuration dialog.
3-30
A31003-H3540-T170-5-7619, 11/2008
3.4.2
General CSP parameters
The type of system connected and the relevant access information must be determined when
configuring the general CSP parameters.
>
Activate the General tab in the CSP configuration dialog.
Display
Parameter
Description
System
For selecting the connected system. Only HiPath 5000
RSM (Multi node) is currently available for selection.
Client user
CSTA user name of the client user on the system (for logging in the application connected to the CSP).
Client password
CSTA password of the client user on the system (for logging in the application connected to the CSP). The password dialog opens automatically following input.
Listener port
CSP listener port
Saving parameters
●
●
A31003-H3540-T170-5-7619, 11/2008
3-31
3.4.3
CSP mode parameters
CSP mode settings can determine the content and scope of information exchanged between
the CSP and the connected application in the underlying CSTA protocol. The application connected to the CSP determines the settings required for this.
>
To configure the mode parameters, open the CSP Mode tab in the CSP.
Display
The following options and information in the underlying protocol can be activated or deactivated:
–
Send Call Linkage Data to client
If this option is activated, a data record with system-internal information is sent with
each call.
–
Send device ID as dialing number
If this option is activated, the device ID of the call is sent as a "dialing number". If deactivated, the device ID is sent as "implicit Private" for internal call numbers and "implicit Public" for external call numbers.
–
Send Originating NID to client
If this option is activated, the originating NID is sent for evaluation via TSP.
3-32
A31003-H3540-T170-5-7619, 11/2008
>
All options must correspond to the connected application.
Saving parameters
●
●
A31003-H3540-T170-5-7619, 11/2008
3-33
3.4.4
Advanced CSP parameters
When configuring advanced CSP parameters, you are configuring parameters that are relevant
to the connection between the connected system and the CSP. System-dependent parameters
are defined on the system and should be specified here accordingly.
>
Activate the Advanced tab in the CSP configuration dialog.
Display
Parameter
Description
Additional time in seconds until automatic re-installation
Consistency check period (s) Time interval (in seconds) for cyclical plausibility checks.
3-34
CSTA reestablish period (s)
CSP waiting time (in seconds) until a connection is re-established following connection failure.
CSP timeout (in seconds)
A31003-H3540-T170-5-7619, 11/2008
Parameter
Description
CSP waiting time between two messages.
Trace
Option for activating trace messages (CSTA messages)
that can be interpreted using separate standard debugging tools.
Saving parameters
●
●
A31003-H3540-T170-5-7619, 11/2008
3-35
3.4.5
CSP assignment parameters
The CSP still requires information on which CMDs the assignment (or connection) applies to.
>
To set the assignment parameters, open the Assignment tab in the CSP configuration
dialog.
Display
A list of configured assignments is displayed with this information:
Column/field
Description
Name
Name of the assigned CMD.
V-Node ID
Node ID of the system connected to the CMD.
CMD IP address
IP address of the connected CMD in the network.
CMD IP port
System port number for the connected CMD Listener Port,
usually 8001, 8002 etc.
Adding entries (assignments):
1.
Click Add in the Assignment tab.
2.
A list of all CMDs configured in the network is displayed. Select the CMD to be made available for the CSP. Multiple selection is possible using the keyboard or mouse. To highlight
all list entries click Select All.
3.
Click Add to accept the selected entries followed by Close to exit the list window. The CSP
3-36
A31003-H3540-T170-5-7619, 11/2008
Removing assignments
Highlight the assignment to be deleted using the mouse and click Remove or press the *
key. The entry is deleted from the list and the assignment is cancelled.
The list of CMD assignments can be sorted in ascending/descending order according to column content by clicking the relevant column heading, e.g. Name.
Saving parameters
>
>
A31003-H3540-T170-5-7619, 11/2008
3-37
3.4.6
CSP licensing parameters
This configuration dialog displays information on current CSP licensing and is applicable to applications that are subject to license.
>
Activate the license tab in the configuration dialog.
Display
Parameter
Description
MAC ID
MAC ID, used for encryption.
This is the MAC ID of the first LAN interface in the system network (e.g.
HG 1500).
Current license
Display of current license codes for licensing. The present date, validity and number of current licenses is displayed beneath it.
The administrator engineer can download this key from the license
server and enter a new license code here. The key entered is checked
when a license is changed. Older licenses are recorded in the license
history. If the wrong license key is entered, a message appears, no licenses are used.
License History
Saving parameters
>
3-38
A31003-H3540-T170-5-7619, 11/2008
>
3.4.7
CSP version information
tab.
A31003-H3540-T170-5-7619, 11/2008
3-39
3.5
3.5.1
General
CCMC (Central Configuration Manager Client) synchronizes configuration data between the
HiPath 5000 RSM database (Feature Provider Database) and the local TAPI 170 configuration
databases (mdb).
To edit CCMC configuration parameters after installation, start the configuration dialog as follows:
>
>
Activate the CCM Local Options by double-clicking the associated icon.
The CCMC Local Options dialog appears.
3-40
A31003-H3540-T170-5-7619, 11/2008
3.5.2
Configuring database parameters
At present this parameters are not relevant for TAPI 170. Therefore no changes are possible.
A31003-H3540-T170-5-7619, 11/2008
3-41
3.5.3
>
Configuring general CCMC parameters
Open the Miscellaneous tab and edit the following parameters:
Display
.
Parameter
Description
VAPL Event Delay in seconds
After configuration changes in the system so called VAPL
events occur. To avoid a permanent synchronisation after
possible multiple system configuration changes you enter
a delay time for data synchronisation.
The default value of 20 seconds should not be changed.
SQL DB Polling cycle in sec- At present this parameter is not relevant and therefore can
onds
not be changed.
MDB Polling cycle in seconds
At present this parameter is not relevant and therefore can
not be changed.
1.
You can start a possibly stopped data synchronization service (CCMC service) with clicking Start service.
2.
Press the Accept button to save your settings.
3-42
A31003-H3540-T170-5-7619, 11/2008
tapi170_enServer.fm
4
Additional Configurations on the Server PC
General
User or client call numbers are made available for installing the TSP during TAPI linedevice configuration (see TSP linedevice parameters). These must still be assigned to the relevant users
in the network. This ensures that network subscribers can only use the linedevices reserved
specifically for them.
4.1
>
The following description and figures are valid for Windows 2000. For other Windows
operation systems the description is valid accordingly.
1.
Open the Telephony dialog via Start - Programs - Administration - Telephony
or start the dialog by activating Start - Run, entering TAPIMGMT.MSC and confirming.
●
The Telephony dialog is displayed. Activate the HiPath TAPI 120/170 TAPI 2.2 SP entry
under Telephony. The configured lines and assigned user names are listed under Line
Name (see TSP linedevice parameters).
It is easier to assign configured linedevices to client PCs (network users) if the call number
has been entered in the Name field in addition to the user name during linedevice installation.
2.
Right-click the relevant user entry here and select Edit Users... in the context menu displayed.
A31003-H3540-T170-5-7619, 11/2008
4-1
tapi170_enServer.fm
Display
3.
Click the Add button in the Edit Users... dialog.
Display
4.
4-2
A list of users configured in the domain is displayed. Select the user to be assigned by double-clicking and confirm with OK.
A31003-H3540-T170-5-7619, 11/2008
tapi170_enServer.fm
Display
5.
The Edit Users dialog re-appears. The selected user is displayed here. Click OK to confirm.
Display
6.
If the line has already been assigned a user in the network, it is displayed in the Edit Users
dialog. Click the Remove button to cancel this assignment.
A31003-H3540-T170-5-7619, 11/2008
4-3
tapi170_enServer.fm
4.2
General
A user ID with administrator and domain administration rights must be assigned for the telephone service for operating the telephone server.
Proceed as follows to configure the telephone service:
1.
Open the telephone dialog via Start - Programs - Administration - Telephony.
2.
The dialog can be started by selecting Start - Run, entering TAPIMGMT.MSC in the entry
field and confirming.
3.
The Telephony dialog is displayed. Right-click the Computer Name entry in the left part of
the dialog. Activate the Properties entry in the context menu displayed.
Display
4.
Activate the Enable Telephony Server option in the Properties dialog and enter the user
ID for the telephone service in the User Name field.
You can also click the Choose User... button and select the relevant user.
5.
Enter the assigned password in the Password field.
4-4
A31003-H3540-T170-5-7619, 11/2008
tapi170_enServer.fm
Display
6.
Click OK to confirm. A security prompt is displayed for restarting the telephone service.
Display
7.
Click Yes to confirm this message. The telephone service is then restarted.
A31003-H3540-T170-5-7619, 11/2008
4-5
tapi170_enServer.fm
4-6
A31003-H3540-T170-5-7619, 11/2008
tapi170_enClient.fm
5
Microsoft TSP Configuration on a Client PC
A number of configuration steps must be performed on the relevant client PCs when using TAPI
170.
.
5.1
General
The following steps must be performed for installation and configuration on a client PC:
1.
Enter the server name on the client PC.
2.
Configure the Network Neighborhood properties.
5.1.1
Entering the server name on the client PC
General
The telephony server name must be entered on every client PC to ensure proper communication between the client and server PC. Proceed as follows in the case of a client PC running
Windows:
1.
Log on to Windows as a user with administrator rights.
2.
Click Run in the Start menu.
3.
Enter the following command: TCMSETUP /C remoteserver
where
●
remoteserver
is the name of the telephony server PC.
A31003-H3540-T170-5-7619, 11/2008
5-1
tapi170_enClient.fm
5.1.2
Configuring Network Neighborhood properties
General
The following settings must be checked/configured on every client PC running Windows:
1.
Right-click the Network Neighborhood icon on the desktop and activate Properties. The
Network and Dial-Up Connections dialog appears.
2.
Double-click LAN Connection for file and print sharing settings.
Display
3.
5-2
Click the Properties button.
A31003-H3540-T170-5-7619, 11/2008
tapi170_enClient.fm
Display
4.
If the File and Printer Sharing for Microsoft Networks (as shown above) is not available,
proceed as follows:
Installing the file and printer sharing service:
>
Click the Install button if the service for file and printer sharing is not already installed.
>
Click the Service entry and then click the Add... button. The Select Network Service
dialog is displayed.
A31003-H3540-T170-5-7619, 11/2008
5-3
tapi170_enClient.fm
>
Click the File and Printer Sharing for Microsoft Networks entry followed by OK. The
dialog displayed in step 3 re-appears. The new entry is now listed.
5.
Check if the service is activated. The service is activated if the checkmark is visible in the
check box beside the entry. If the checkmark is not visible, the service is not activated. Simply click the empty checkbox to activate it.
6.
Then click the Close button. The dialog shown in step 2 is displayed. Activate Close here.
7.
Click the LAN Connection entry in the Network Neighborhood dialog and activate the Network Identification entry in the Advanced menu to configure the login domains.
5-4
A31003-H3540-T170-5-7619, 11/2008
tapi170_enClient.fm
Display
8.
Activate the Network Identification... tab in the System Properties dialog displayed.
Display
A31003-H3540-T170-5-7619, 11/2008
5-5
tapi170_enClient.fm
●
The login domain for the client PC is displayed here under Domain. If the login domain is
not the server domain, it can be changed once the Properties button has been clicked.
9.
Click OK to confirm. The dialog displayed in step 7 re-appears. Close this dialog.
5-6
A31003-H3540-T170-5-7619, 11/2008
A
AnhangA.fm
Appendix A: TAPI 170 with Terminal Server / Citrix
In this section you find information relevant for HiPath TAPI 170 V2.0 with Terminal Server /
Citrix:
●
Terminal Server / Citrix overview
●
TAPI 170 (Single node) on Terminal Server / Citrix: Release and restrictions
●
Conditions for Domain Controller and Terminal Server
●
Special needs for Terminal Server / Citrix with >1 cluster server.
●
Terminal-Server / Citrix and HiPath 5000 RSM (Multi node)
A31003-H3540-T170-5-7619, 11/2008
A-1
AnhangA.fm
A.1
A terminal server provides access to its installed applications for terminal clients. Those applications run on terminal server. The input/output is exchanged between terminal server and terminal clients. For example Word can be installed on terminal server, will run there and can be
used from terminal clients.
See the following links for more details.
●
http://technet.microsoft.com/en-us/windowsserver/terminal-services/default.aspx
●
http://www.citrix.com/English/ps2/products/product.asp?contentID=1297817
(Citrix has developed this technology for Microsoft and distribute a feature added version
under the product name Citrix XenApp, formerly Citrix Presentation Server, formerly
"MetaFrame").
A-2
A31003-H3540-T170-5-7619, 11/2008
AnhangA.fm
TAPI 170 (Single node) on Terminal Server / Citrix: Release and restrictions
A.2
TAPI 170 (Single node) on Terminal Server / Citrix:
Release and restrictions
To ensure that users get access only to their own lines, TAPI 170 has to be installed on the
same machine as the terminal server / Citrix. The server has to be configured as telephony
server too (see section Additional Configurations on the Server PC).
Due to its software architecture the Remote-TSP from Microsoft cannot be used in a terminal
server / Citrix environment, since the Remote-TSP will always run in the context of the user,
who first uses the Remote TSP. This problem exists on all operating system and terminal server
/ Citrix variants.
Released configuration (Single node) / not relesed configuration
Released configuration
(Single Node)
Not released configuration
A31003-H3540-T170-5-7619, 11/2008
A-3
AnhangA.fm
A.3
The operation of a telephony server requires a Windows Domain incl. Domain Controller due
to Microsoft's TAPI architecture. In the easiest case the Domain Controller could be the PC as
the telephony server. On the PC with the telephony server however there has to be Terminal
Server / Citrix installed too.
But Microsoft advises against the installation of a Terminal Server on a Domain Controller due
to performance and security issues. Therefore it is to see to it that the Domain Controller is installed on a different PC than the combination of telephony server and Terminal Server / Citrix.
>
A-4
Only for pure test operation - however not in productive environment - the Domain
Controller can be installed on the same PC along with telephony server and Terminal
Server.
A31003-H3540-T170-5-7619, 11/2008
AnhangA.fm
A.4
Overview
Please note the following statements if TAPI is used in a Terminal Server / Citrix Farm build by
more than one Cluster Server:
●
Any server that needs TAPI has to be configured as telephony server and has its own TAPI
170.
●
Each server needs its own Licensing, meaning that the same lines have to be licensed at
all servers.
●
Assignment of user to TAPI lines has to be done at each server.
Assignment is stored in a file tsec.ini.
●
Up to 4 TAPI 170 can be connected directly to HiPath.
●
More than 4 TAPI 170 in parallel needs special examination and project specific release.
A31003-H3540-T170-5-7619, 11/2008
A-5
AnhangA.fm
A.5
For TAPI 170 on HiPath 500 RSM (Multi node) the same restrictions as described at TAPI 170
(Single node) on Terminal Server / Citrix: Release and restrictions are valid.
Not released configuration
A-6
A31003-H3540-T170-5-7619, 11/2008
Tapi170_enAbkuerzung.fm
List of abbreviations
Y
This list contains the abbreviations used in this manual.
Abbreviation
Definition
CCMC
Central Configuration Manager Client
CMD
CSTA Message Dispatcher
CSP
CSTA Service Provider
CSTA
Computer Supported Telephony Application
CTI
Computer Telephony Integration
TAPI
Telephony Application Programming Interface
TSP
TAPI Service Provider
A31003-H3540-T170-5-7619, 11/2008
Y-1
Tapi170_enAbkuerzung.fm
Y-2
A31003-H3540-T170-5-7619, 11/2008
Tapi170_enSIX.fm
Index
Index
Z
I
A
ACD parameters 3-21
C
CCMC 1-1, 1-6, 1-8
CCMC configuration 3-40
CCMC database parameters 3-41
CCMC general parameters 3-42
CMD 1-1, 1-6
CMD advanced parameters 3-5
CMD assignment parameters 3-7
CMD general parameters 3-3
CMD installation 2-4
CMD license parameters 3-12
CMD parameters for CTI firewall 3-10
CMD version information 3-13
Copy protection 1-7
CSP 1-1, 1-6
CSP advanced parameters 3-34
CSP assignment parameters 3-36
CSP configuration 3-30
CSP general parameters 3-31
CSP licensing parameters 3-38
CSP mode parameters 3-32
CSP version information 3-39
D
Data synchronization 1-8
Dongle 1-7
Dongle driver 1-6
E
Environment 1-3
Installation medium 1-13
Installation sequence 1-13
L
Licence code 1-7
License monitoring 1-7
License-free applications 3-25
Licensing 1-7
Limitations 1-12
M
Multi node 1-1, 1-3, 2-2, 2-3, 2-4, 2-5, 2-6, 27, 3-3, A-6
S
Setup type 1-14
Single node 1-1, 1-3, 2-2, 2-3, 2-6, 3-26, A-3
Software requirements 1-11
Starting installation 2-2
T
TAPI 170 ports 1-12
Telephone service on the server PC 4-4
TSP 1-1, 1-6
TSP ACD parameters 3-21
TSP advanced parameters 3-19
TSP assignment parameters 3-22
TSP configuration 3-14
TSP General Parameters 3-16
TSP license parameters 3-24
TSP line parameters 3-26
TSP parameters 3-19
TSP version information 3-29
F
Features 1-9
H
Hardware requirements 1-11
A31003-H3540-T170-5-7619, 11/2008
Z-1
Tapi170_enSIX.fm
Index
Z-2
A31003-H3540-T170-5-7619, 11/2008

Documentation HiPath TAPI 170 V2.0 MultiNode Installation and

Transcription

Similar documents

HiPath 3000/5000 HiPath TAPI 120 V2.0

Documentation HiPath TAPI 120 V2.0 Installation and Configuration

Benutzerhandbuch

ERNW Newsletter 2