Documentation. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration. Communication for the open minded. Administrator Documentation

(1)

Documentation

HiPath TAPI 170 V2.0 MultiNode

Installation and Configuration

Administrator Documentation

(2)

tified by an external certification company.

Siemens Enterprise Communications GmbH & Co. KG is a Trademark Licensee of Siemens AG

Reference No.: A31003-H3540-T170-7-76A9 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.

Siemens Enterprise Communications www.siemens.com/open

(3)

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

2.1 General . . . 2-1 2.2 Starting installation . . . 2-2 2.3 Installing the CMD component. . . 2-5 2.4 Installing the CSP component . . . 2-6 2.5 Installing the TSP component . . . 2-7 2.6 Installing the CCMC component . . . 2-8 2.7 Installing the dongle driver . . . 2-9 2.8 Ending installation . . . 2-9

3 Configuring Components. . . 3-1

(4)

A31003-H3540-T170-7-76A9, 09/2010

0-2 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

3.3.5 TSP assignment parameters . . . 3-22 3.3.6 TSP license parameters . . . 3-24 3.3.6.1 License-free applications . . . 3-25 3.3.7 TSP linedevice parameters . . . 3-26 3.3.7.1 Adding lines . . . 3-27 3.3.7.2 Editing / deleting lines . . . 3-27 3.3.7.3 Licensing linedevices . . . 3-27 3.3.7.4 Marking linedevices for UCD (ACD) . . . 3-28 3.3.8 TSP version information . . . 3-29 3.4 Configuring the CSP component. . . 3-30 3.4.1 Starting the configuration dialog . . . 3-30 3.4.2 General CSP parameters . . . 3-31 3.4.3 CSP mode parameters . . . 3-32 3.4.4 Advanced CSP parameters . . . 3-34 3.4.5 CSP assignment parameters . . . 3-36 3.4.6 CSP licensing parameters . . . 3-38 3.4.7 CSP version information. . . 3-39 3.5 Configuring CCMC components . . . 3-40 3.5.1 General. . . 3-40 3.5.2 Configuring database parameters . . . 3-41 3.5.3 Configuring general CCMC parameters . . . 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

5.1 Configuring the TSP on a client PC . . . 5-1 5.1.1 Entering the server name on the client PC. . . 5-1 5.1.2 Configuring Network Neighborhood properties . . . 5-2

A Appendix A: TAPI 170 with Terminal Server / Citrix. . . A-1

A.1 Terminal Server / Citrix overview . . . A-2 A.2 TAPI 170 (Single node) on Terminal Server / Citrix:

Release and restrictions . . . A-3 A.3 Conditions for Domain Controller and Terminal Server . . . A-4 A.4 Special needs for Terminal Server / Citrix with multiple cluster server. . . A-5 A.5 Terminal-Server / Citrix and HiPath 5000 RSM (Multi node) . . . A-6

(5)

General

1 Introduction

1.1 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/pres-ence display of telephones connected to a communication 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 communication systems in a network to a logical CSTA.

This allows applications to control the phones of all connected communication systems via the CSP.

● CSTA Message Dispatcher CMD

The CSTA links of multiple applications are merged on the CSTA interface on a communi-cation 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 Mi-crosoft-defined interfaces.

(6)

A31003-H3540-T170-7-76A9, 09/2010

1-2 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration,Administrator

Documenta-General

Documentation

● Various abbreviations are used in this document to improve readability. An overview of all

abbreviations can be found in the List of abbreviations.

● To improve readability, "telecommunications system(s)" has been abbreviated to

"sys-tem(s)" or "communication sys"sys-tem(s)"in this document.

● The product name has also been abbreviated to TAPI 170 for the same reason.

● All described operation sequences and dialogs refer to older Windows versions, e.g.

(7)

Setup type (environment) and components

1.2 Setup type (environment) and components

Setup types (environment)

As an individually marketed product, TAPI 170 can be used with one system / one server (Sin-gle node setup type or sin(Sin-gle node environment) or can be used in conjunction with several sys-tems / 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 envi-ronment.

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 communication system (here: OpenScape Office), using Ethernet LAN and CSTA protocol.

PC clients in a network with the TAPI applications are in the same domain as the TAPI 170 serv-er with the TSP, and access the TAPI sserv-ervserv-er PC via Microsoft's remote TAPI functionality.

(8)

A31003-H3540-T170-7-76A9, 09/2010

Documenta-Setup type (environment) and components

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

communica-tion system in a multi node environment. Stacommunica-tion data for the systems connected in the work is retrieved from the HiPath 5000 RSM database. If station data is changed in the net-work, TSP is automatically notified of the change.

● PC clients with TAPI applications in the network must be located in the same domain as

(9)

Setup type (environment) and components

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 sys-tems in the same sequence as in a standalone communication system and presents them to the CSTA application. Applications thus overlook whether the CSTA interface is operated on a standalone communication 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

con-nected to each individual communication system via Ethernet LAN and CSTA protocol.

● CSP components retrieve station data for the communication systems connected in the

(10)

A31003-H3540-T170-7-76A9, 09/2010

Documenta-Setup type (environment) and components

TAPI 170 components

The following TAPI 170 components are installed irrespective of the solution:

● 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 (only with 32-bit operation system versions)

Required for installing (updating) TAPI versions licensed via TAPI 170 V1.0 dongle licens-ing.

You can select this component for installation with the setup type Custom. The dongle driv-er is not installed if license codes are used for licensing.

See also:

(11)

Licensing and copy protection

1.3 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 further on 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

(12)

A31003-H3540-T170-7-76A9, 09/2010

Documenta-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

(13)

Features

1.5 Features

The following features are available depending on the system installed and the support provid-ed for the TAPI applications usprovid-ed.

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.

(14)

A31003-H3540-T170-7-76A9, 09/2010

1-10HiPath TAPI 170 V2.0 MultiNode Installation and Configuration,Administrator

Documenta-System connection

1.6 System connection

(15)

Hard- and software requirements

1.7 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

● 32-bit operation system versions:

– Windows 2003 Server / 2003 Server R2

– / 2003 Server / 2003 Server or Windows 2008 Server

– Windows 2008 Server – Windows 2008 R2 Server

Software requirements for client PCs

– Windows XP Professional

– or Windows Vista (except Home editions)

– or Windows 7 (except Starter / Home Basic / Home Premium editions)

– Windows 7 (except Starter / Home Basic / Home Premium editions)

>

For TAPI 170 on a server PC with Terminal Server / Citrix please consider informa-tion given in the section Appendix A: TAPI 170 with Terminal Server / Citrix.

(16)

A31003-H3540-T170-7-76A9, 09/2010

Documenta-Hard- and software requirements

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).

● Installation of TAPI 170 must be executed by an user with administration and domain

ad-ministration 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)

Limitations

Operating TAPI 170 and TAPI 120 on the same PC is not possible.

Port number Description

7001 CSTA-link to the system (HiPath OpenOffice EE / 2000 / 3000 / 5000 RSM) 8001 CSTA-link to CMD

(17)

Installation medium and installation sequence

1.8 Installation medium and installation sequence

Installing TAPI 170

Either an installation CD is provided or the software can be downloaded from the software sup-ply center.

Contents of the TAPI 170 installation CD

The TAPI 170 installation CD contains these folders:

Installation sequence

As the installation can include different components from various vendors, the following instal-lation sequence must be observed.

1. Installing Components

2. Configuring Components

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 Contains the USB-compliant CAPI drivers for the DIVA Pro 2.0 ISDN card for Windows 2000.

\Diehl_w2k3 Contains the USB-compliant CAPI drivers for the DIVA Pro 2.0 ISDN card for Windows 2003.

\Diehl_w2k_diva30 Contains the USB-compliant CAPI drivers for the DIVA Pro 3.0 ISDN card for Windows 2000.

\doc Contains documentation for customers and develop-ers.

\MS Contains the Microsoft documentation for TAPI config-uration.

(18)

A31003-H3540-T170-7-76A9, 09/2010

Documenta-Installation medium and installation sequence

Following the installation of a component the configuration dialog of this component is dis-played directly. Thus you can determine the necessary parameters during the setup. Alterna-tively you can configure the parameters after setup completion.

You define the components to be installed by selecting a setup type or by selecting the compo-nents directly with custom installation. The setup determines the sequence of the compocompo-nents installation.

See also:

Configuring the CMD component Configuring the TSP component Configuring the CSP component Configuring CCMC components

(19)

General

2 Installing Components

2.1 General

Scope of installation

The components to be installed can be selected directly or indirectly when installing TAPI com-ponents. The following components are available:

● CMD ● CSP ● TSP ● CCMC ● Dongle driver See also:

Setup type (environment) and components Installing the CMD component

Installing the CSP component Installing the TSP component Installing the CCMC component Installing the dongle driver

Installation and configuration

(20)

A31003-H3540-T170-7-76A9, 09/2010

Starting installation

2.2 Starting installation

Starting installation

1. Log on as an administrator and close all running applications.

2. Insert the TAPI 170 installation CD. Select the \TAPI170\setup.exe file on the installa-tion drive under Start - Run and confirm with OK.

3. Select the language for the installation dialogs, the installation is prepared. 4. After installation preparation the welcome-Dialog appears. Confirm it with Next.

5. Continue installation with clicking Next.

6. The installation setup type must then be specified:

Display

>

The setup determines the operation system version (32-bit or 64-bit) and auto-matically starts the installation of the correct TAPI 170 setup version.

>

Under Windows Vista, Windows 2008 or Windows 7 please confirm the UAC (User Account Control) prompt, that appears now.

(21)

The relevant installation components are automatically assigned once the Single node and Multi node setup types have been selected.

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 individ-ual components.

7. Click Next to confirm your selection.

8. Installation of the selected components is started after clicking Install.

Components Setup type TSP CMD CSP CCMC Dongle driver Single node ✓ - - - -Multi node ✓ ✓ ✓ ✓ -Custom (✓) (✓) (✓) (✓) (-)

>

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 Con-trol Panel will override the existing installation, i.e., all installed components that are not explicitly selected in the custom installation dialog will be uninstalled.

>

The initial installation of TAPI 170 on a PC with Windows Vista or Windows 7 requires a reboot of the TAPI-PC. In that case the installation dialog displays an additional red marked notice.

You then can cancel the installation. For continuing the installation you click on

(22)

A31003-H3540-T170-7-76A9, 09/2010

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 instal-lation routine (the exact time is dependent on the instalinstal-lation components selected). To activate the ACD service, click Yes.

(23)

Installing the CMD component

2.3 Installing the CMD component

The CMD component is included in the standard scope of installation for Multi node environ-ment or after customized selection.

1. A welcome dialog is not displayed when installing the CMD component. Progress is dis-played 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

(24)

A31003-H3540-T170-7-76A9, 09/2010

Installing the CSP component

2.4 Installing the CSP component

The CSP component is included in the standard scope of installation for Multi node environ-ment 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. The required parameters can be entered in this dialog or configured at a later stage.

Display

(25)

Installing the TSP component

2.5 Installing the TSP component

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 prompt-ed to select the IP address to be usprompt-ed.

3. The TSP configuration dialog opens automatically following successful TSP installation. The required parameters can be entered in this dialog or configured at a later stage.

Display

The individual configuration parameters are described in detail under Configuring the TSP component.

(26)

A31003-H3540-T170-7-76A9, 09/2010

Installing the CCMC component

2.6 Installing the CCMC component

The CSP component is included in the standard scope of installation for Multi node environ-ment 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 installa-tion. The required parameters can be entered in this dialog or configured at a later stage.

Display

(27)

Installing the dongle driver

2.7 Installing the dongle driver

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.

>

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

(28)

A31003-H3540-T170-7-76A9, 09/2010

HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-1

General

3 Configuring Components

3.1 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:

● Configuring the CMD component ● Configuring the TSP component ● Configuring the CSP component ● Configuring CCMC components

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).

(29)

Configuring the CMD component

3.2 Configuring the CMD component

3.2.1 Starting the configuration dialog

Activating the configuration dialog

To edit the CMD configuration parameters after installation, start the configuration dialog as fol-lows:

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.

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.

(30)

A31003-H3540-T170-7-76A9, 09/2010

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 se-lected: ● OpenScape Office ● 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 rel-evant.

(31)

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.

CAPI controller Connected to HiPath 5000 RSM (Multi node) this parameter is nor rel-evant.

Baud rate Connected to HiPath 5000 RSM (Multi node) this parameter is nor rel-evant.

CMD IP port Connected to HiPath 5000 RSM (Multi node) this field is inactive. pa-rameter is nor relevant. You onfigure this papa-rameter in the

Assign-ment tab.

>

If the system is changed, a message may appear indicating that the licensing infor-mation may have been changed. If this occurs, the licensing information for the new system must be checked.

(32)

A31003-H3540-T170-7-76A9, 09/2010

3.2.3 Advanced CMD parameters

The advanced CMD parameters are determining settings relevant for to the connection be-tween 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.

Display

Enter the following parameters:

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.

(33)

> 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.

Heartbeat period (s) Time interval (seconds) for checking CSTA interface activ-ity. 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-establish-ment 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-es-tablished following connection failure. The default value is 120 seconds. CSTA invoke timeout (s) CMD timeout in seconds.

The default value is 120 seconds.

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 pa-rameters.

(34)

A31003-H3540-T170-7-76A9, 09/2010

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/configura-tion (KDS) - usually the customer name and / or locainstallation/configura-tion. 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.

(35)

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.

> A confirmation message appears in both cases before the parameter values are saved in the registration database. Click Yes to confirm this message.

3.2.4.1 Adding nodes

3. 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-ap-pears.

A maximum of 64 systems/nodes can be configured.

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.

(36)

A31003-H3540-T170-7-76A9, 09/2010

(37)

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 linede-vice, 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), en-abling a single entry in the firewall to be identified.

(38)

A31003-H3540-T170-7-76A9, 09/2010

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

> 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.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 num-ber of clients permitted to seize linedevices at the same time is limited by the licensing agree-ment.

See also:

CMD license parameters

(39)

3.2.6 CMD license parameters

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:

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.

(40)

re-A31003-H3540-T170-7-76A9, 09/2010

3.2.7 CMD version information

(41)

Configuring the TSP component

3.3 Configuring the TSP component

3.3.1 Starting the configuration dialog

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.

(42)

A31003-H3540-T170-7-76A9, 09/2010

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

(43)

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 parame-ters.

> Activate the General tab in the configuration dialog.

Display

System For selecting the connected system. The following baud rates can be selected:

– OpenScape Office

– HiPath OpenOffice EE – HiPath 2000

– HiPath 3000

(44)

A31003-H3540-T170-7-76A9, 09/2010

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.

CAPI controller Connected to HiPath 5000 RSM (Multi node) this parameter is nor rel-evant.

Baud rate Connected to HiPath 5000 RSM (Multi node) this parameter is nor rel-evant.

IP address With connection to the HiPath 5000 RSM (Multi node) system, this pa-rameter 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 pa-rameter cannot be modified. You administrate the IP port of the con-nected systems in the Assignment tab.

>

If the System is changed, a message may appear indicating that the licensing infor-mation may have been changed. If this occurs, the licensing information for the new system must be checked.

>

It is necessary to re-start the TSP (net stop tapisrv), for instance after modifying the connection type (CSTA link).

(45)

Importing

1. General configuration parameters can also be imported from a file, e.g. containing export-ed parameter information. Click Nodes Import to start importing.

2. Select the file to be imported.

(46)

A31003-H3540-T170-7-76A9, 09/2010

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

Heartbeat period (s) Time interval (seconds) for checking CSTA interface ac-tivity. The value 0 disables the check.

The default value 10 seconds should not be changed. Heartbeat timeout (s) Additional time in seconds until automatic re-installation

in the case of CSTA interface failure.

The default value 15 seconds 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. Trunk access code start

Trunk access code end

● With connection to the HiPath 5000 RSM (Multi

node) this parameter is not relevant. RCA port start

RCA port end

(47)

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 debug-ging tools.

CSTA reestablish period (s) TSP waiting time (in seconds) until a connection is re-es-tablished following connection failure. The default value is 20 seconds.

CSTA invoke timeout (s) TSP timeout (in seconds)

The default value is 120 seconds.

Transmission interval (ms) TSP waiting time between two messages. The default value is 50 ms.

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 immedi-ately opens an input dialog in which you can enter and confirm the new password, then return to the configura-tion dialog.

>

CSTA-Login on the system is not possible if the CSTA3 password entered here does not correspond to the system password.

(48)

A31003-H3540-T170-7-76A9, 09/2010

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.

(49)

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:

Name System description (from KDS) - usually the customer name and / or location.

(50)

A31003-H3540-T170-7-76A9, 09/2010

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 con-tent by clicking the relevant column header, e.g., Name.

(51)

3.3.6 TSP license parameters

This configuration dialog displays information on current TSP licensing and is applicable to ap-plications that are subject to license. There are also license-free apap-plications.

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 en-vironment.

See also Linedevice assignment to client PCs

> Activate the Lines 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.

(54)

A31003-H3540-T170-7-76A9, 09/2010

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.

3.3.7.1 Adding lines

1. Click Add in the Lines tab.

2. A list of all call numbers configured for the connected system is displayed. Individually se-lect the required entries (multiple sese-lection 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 configuration dialog re-appears.

3.3.7.2 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.

(55)

● 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:

TSP license parameters License-free applications

3.3.7.4 Marking linedevices for UCD (ACD)

● 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.

>

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.

(56)

A31003-H3540-T170-7-76A9, 09/2010

The number of UCD groups or UCD agents (excluding trunks) marked for ACD is also displayed in the ACD tab.

3.3.8 TSP version information

(57)

Configuring the CSP component

3.4 Configuring the CSP component

3.4.1 Starting the configuration dialog

1. Open the Windows Control Panel via Start - Settings - Control Panel. 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

(58)

A31003-H3540-T170-7-76A9, 09/2010

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

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 log-ging in the application connected to the CSP).

Client password CSTA password of the client user on the system (for log-ging in the application connected to the CSP). The pass-word dialog opens automatically following input.

(59)

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 con-nected 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 deac-tivated:

– 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

(60)

A31003-H3540-T170-7-76A9, 09/2010

(61)

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

Heartbeat period (s) Time interval (seconds) for checking CSTA interface ac-tivity. The value 0 disables the check.

The default value 10 seconds should not be changed. Heartbeat timeout (s) Additional time in seconds until automatic re-installation

in the case of CSTA interface failure.

(62)

A31003-H3540-T170-7-76A9, 09/2010

Transmission interval (ms) CSP waiting time between two messages. The default value is 50 ms.

Trace Option for activating trace messages (CSTA messages) that can be interpreted using separate standard debug-ging tools.

(63)

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:

Adding entries (assignments):

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.

(64)

A31003-H3540-T170-7-76A9, 09/2010

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 col-umn content by clicking the relevant colcol-umn heading, e.g. Name.

(65)

3.4.6 CSP licensing parameters

This configuration dialog displays information on current CSP licensing and is applicable to ap-plications that are subject to license.

> Activate the license tab in the configuration dialog.

Display

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, valid-ity and number of current licenses is displayed beneath it.

(66)

A31003-H3540-T170-7-76A9, 09/2010

3.4.7 CSP version information

(67)

Configuring CCMC components

3.5 Configuring CCMC components

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).

Starting the configuration dialog

To edit CCMC configuration parameters after installation, start the configuration dialog as fol-lows:

> Open the Windows Control Panel via Start - Settings - Control Panel.

(68)

A31003-H3540-T170-7-76A9, 09/2010

3.5.2 Configuring database parameters

(69)

3.5.3 Configuring general CCMC parameters

> Open the Miscellaneous tab and edit the following parameters:

Display

.

1. You can start a possibly stopped data synchronization service (CCMC service) with click-ing Start service.

2. Press the Accept button to save your settings.

VAPL Event Delay in sec-onds

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-onds

At present this parameter is not relevant and therefore can not be changed.

MDB Polling cycle in sec-onds

(70)

A31003-H3540-T170-7-76A9, 09/2010

Linedevice assignment to client PCs

4 Additional Configurations on the Server PC

General

User or client call numbers are made available for installing the TSP during TAPI linedevice con-figuration (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 Linedevice assignment to client PCs

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 installa-tion.

2. Right-click the relevant user entry here and select Edit Users... in the context menu dis-played.

(71)

Display

3. Click the Add button in the Edit Users... dialog.

Display

(72)

A31003-H3540-T170-7-76A9, 09/2010

Display

5. The Edit Users dialog re-appears. The selected user is displayed here. Click OK to con-firm.

Display

(73)

Configuring the telephone service on the server PC

4.2 Configuring the telephone service on the server PC

General

A user ID with administrator and domain administration rights must be assigned for the tele-phone service for operating the teletele-phone server.

Telephony server / service on a Windows Server2008 / 2008 R2 PC

To get the telephony server/service to work with a domain-admin/admin account on a Windows Server 2008 / 2008 R2, it is required to assign two additional user rights to the corresponding user account manually:

● On a Domain Controller:

– Run gpme.msc – Select tab All

– Select Default Domain Controllers Policy, click OK

– Open tree: Computer Configuration/Policies/Windows Settings/Security

Set-tings/Local Policies/User Rights Assignment

– Double click policy Replace a process level token and add corresponding user – Double click policy Generate security audits and add corresponding user

● On a Server, that isn't a Domain Controller:

– Run secpol.msc

– Open tree: Security Settings/Local Policies/User Rights Assignment

– Double click policy Replace a process level token and add corresponding user – Double click policy Generate security audits and add corresponding user

Proceed as follows to configure the telephone service:

1. Open the telephone dialog via Start - Programs - Administration - Telephony.

(74)

A31003-H3540-T170-7-76A9, 09/2010

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.

(75)

Display

6. Click OK to confirm. A security prompt is displayed for restarting the telephone service.

Display

(76)

A31003-H3540-T170-7-76A9, 09/2010

Configuring the TSP on a client PC

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 Configuring the TSP on a client PC

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 communica-tion 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

(77)

Configuring the TSP on a client PC

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