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

Transcription

1 Documentation HiPath TAPI 170 V2.0 MultiNode Installation and Configuration Administrator Documentation P31003-H3540-T A9, 09/2010 Communication for the open minded Siemens Enterprise Communications

2 Our Quality and Environmental Management Systems are implemented according to the requirements of the ISO9001 and ISO14001 standard certified by an external certification company. Copyright Siemens Enterprise Communications GmbH & Co. KG 2010 Hofmannstr. 51, München Siemens Enterprise Communications GmbH & Co. KG is a Trademark Licensee of Siemens AG Reference No.: A31003-H3540-T A9 Communication for the open minded Siemens Enterprise Communications 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.

3 Tapi170_enTOC.fm Contents Contents 0 1 Introduction General Setup type (environment) and components Licensing and copy protection Data Synchronization Features System connection Hard- and software requirements Installation medium and installation sequence Installing Components General Starting installation Installing the CMD component Installing the CSP component Installing the TSP component Installing the CCMC component Installing the dongle driver Ending installation Configuring Components General Configuring the CMD component Starting the configuration dialog General CMD parameters Advanced CMD parameters CMD assignment parameters Adding nodes deleting an entry Exporting / importing parameters (nodes) CMD parameters for CTI Firewall Editing / deleting an entry Adding a CSTA client CMD license parameters CMD version information Configuring the TSP component Starting the configuration dialog General TSP parameters Importing / exporting general configuration parameters Advanced TSP parameters TSP ACD parameters HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 0-1

4 Tapi170_enTOC.fm Contents Nur für den internen Gebrauch TSP assignment parameters TSP license parameters License-free applications TSP linedevice parameters Adding lines Editing / deleting lines Licensing linedevices Marking linedevices for UCD (ACD) TSP version information Configuring the CSP component Starting the configuration dialog General CSP parameters CSP mode parameters Advanced CSP parameters CSP assignment parameters CSP licensing parameters CSP version information Configuring CCMC components General Configuring database parameters Configuring general CCMC parameters Additional Configurations on the Server PC Linedevice assignment to client PCs Configuring the telephone service on the server PC Microsoft TSP Configuration on a Client PC Configuring the TSP on a client PC Entering the server name on the client PC Configuring Network Neighborhood properties 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 List of abbreviations Y-1 Index Z HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

5 tapi170_eneinl.fm Introduction 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/presence 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 communication 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 1-1

6 1-2 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentatapi170_enEinl.fm Introduction General Nur für den internen Gebrauch 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 "system(s)" or "communication system(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. Windows XP. With using newer Windows versions you have to activate the functions accordingly.

7 tapi170_eneinl.fm Introduction 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 (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 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 server with the TSP, and access the TAPI server PC via Microsoft's remote TAPI functionality. > Using TAPI 170 in a single node environment with the OpenScape Office system every CSTA link TAPI 170 is using requires a single licence. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 1-3

8 1-4 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentatapi170_enEinl.fm Introduction Setup type (environment) and components Nur für den internen Gebrauch 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 communication system in a multi node environment. Station data for the 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.

9 tapi170_eneinl.fm Introduction 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 systems 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 connected to each individual communication system via Ethernet LAN and CSTA protocol. CSP components retrieve station data for the communication systems 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 1-5

10 1-6 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentatapi170_enEinl.fm Introduction Setup type (environment) and components Nur für den internen Gebrauch 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) This component will be installed for multi node environment by default. CCMC (Central Configuration Manager Client) This component will be installed for multi node environment by default. Dongle driver (only with 32-bit operation system versions) 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

11 tapi170_eneinl.fm Introduction 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 Licensing of CSTA application links within CSP HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 1-7

12 1-8 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentatapi170_enEinl.fm Introduction Data Synchronization Nur für den internen Gebrauch 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.

13 tapi170_eneinl.fm Introduction Features 1.5 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 1-9

14 1-10HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentatapi170_enEinl.fm Introduction System connection Nur für den internen Gebrauch 1.6 System connection TCP/IP is generally used for connecting TAPI 170 components to each other or to the system(s).

15 tapi170_eneinl.fm Introduction 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 64-bit operation system versions: Windows 2008 Server Windows 2008 R2 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 32-bit operation system versions: Windows XP Professional or Windows Vista (except Home editions) or Windows 7 (except Starter / Home Basic / Home Premium editions) 64-bit operation system versions: Windows 7 (except Starter / Home Basic / Home Premium editions) > The listed operation systems above are not released in virtual environments. > When using Microsoft Vista, Microsoft Windows 7 or Windows 2008 / 2008 R2 different confirmation prompts might appear during TAPI 170 configuration. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 1-11

16 1-12HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentatapi170_enEinl.fm Introduction Hard- and software requirements Nur für den internen Gebrauch 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 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 (HiPath OpenOffice EE / 2000 / 3000 / 5000 RSM) 8001 CSTA-link to CMD 8800 CSTA-link to the system OpenScape Office 8503 IP port for data synchronization of TSP Limitations Operating TAPI 170 and TAPI 120 on the same PC is not possible.

17 tapi170_eneinl.fm Introduction 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 supply center. Contents of the TAPI 170 installation CD The TAPI 170 installation CD contains these folders: File / folder \Diehl_NT_2.36 \Diehl_w2k \Diehl_w2k3 \Diehl_w2k_diva30 \doc \MS \TAPI170 \Tools Description Contains the USB-compliant CAPI drivers for the DIVA Pro 2.0 ISDN card for Windows NT. Contains the USB-compliant CAPI drivers for the DIVA Pro 2.0 ISDN card for Windows Contains the USB-compliant CAPI drivers for the DIVA Pro 2.0 ISDN card for Windows Contains the USB-compliant CAPI drivers for the DIVA Pro 3.0 ISDN card for Windows Contains documentation for customers and developers. Contains the Microsoft documentation for TAPI configuration. Contains the TAPI 170 installation files. 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 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 1-13

18 1-14HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentatapi170_enEinl.fm Introduction Installation medium and installation sequence Nur für den internen Gebrauch 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 setup completion. 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

19 tapi170_eninstallation.fm Installing Components General 2 Installing Components 2.1 General Scope of installation The components to be installed can be selected directly or indirectly when installing TAPI components. 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 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 2-1

20 tapi170_eninstallation.fm Installing Components Starting installation Nur für den internen Gebrauch 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 installation 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 automatically 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. Make sure, that the service-control dialog and all TAPI applications are inactive. Corresponding to this a red marked notice appears in the installation dialog. 2-2 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

21 tapi170_eninstallation.fm Installing Components Starting installation 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 Setup type Single node Multi node - 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. > > 7. Click Next to confirm your selection. 8. Installation of the selected components is started after clicking Install. > 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. 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 Install, the PC automatically reboots. After logging on you return to this point of the TAPI 170 installation procedure. 9. To finish installation click on the Finish button displayed in the final dialog. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 2-3

22 tapi170_eninstallation.fm Installing Components Starting installation Nur für den internen Gebrauch 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. 2-4 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

23 tapi170_eninstallation.fm Installing Components Installing the CMD component 2.3 Installing the CMD component 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 2-5

24 tapi170_eninstallation.fm Installing Components Installing the CSP component Nur für den internen Gebrauch 2.4 Installing the CSP component 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. 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 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. 2-6 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

25 tapi170_eninstallation.fm Installing Components 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 prompted to select the IP address to be used. 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. TSP installation is complete once you have exited the configuration dialog. Further components may now be installed automatically depending on the setup type selected. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 2-7

26 tapi170_eninstallation.fm Installing Components Installing the CCMC component Nur für den internen Gebrauch 2.6 Installing the CCMC component 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. 2-8 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

27 tapi170_eninstallation.fm Installing Components Installing the dongle driver 2.7 Installing the dongle driver > 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 2-9

28 tapi170_enkonfiguration.fm Configuring Components 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). It is necessary to restart the TSP (net stop tapisrv), for instance after modifying the connection type (CSTA link). HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-1

29 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component 3.2 Configuring the CMD component 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, Microsoft Windows 7 or Windows 2008 / 2008 R2 different confirmation prompts might appear during TAPI 170 configuration. 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-2

30 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Nur für den internen Gebrauch 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 System CSTA link Call number CAPI-DLL Description For selecting the connected system. The following systems can be selected: OpenScape Office HiPath OpenOffice EE HiPath 2000 HiPath 3000 HiPath 5000 RSM (default) Connection type between CMD and the system. By default this is TCP/IP and cannot be changed. Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. 3-3 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

31 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Parameter CAPI controller Baud rate CMD IP port Description Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-4

32 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Nur für den internen Gebrauch 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. Display Enter the following parameters: Parameter CSTA3 user CSTA3 password Description 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 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. 3-5 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

33 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Parameter Heartbeat period (s) Heartbeat timeout (s) Consistency check period (s) CSTA reestablish period (s) CSTA invoke timeout (s) Transmission interval (ms) Trace Description 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. Additional time in seconds until automatic re-establishment in the case of CSTA interface failure. The default value is 10 seconds and should not be changed. Time interval in seconds for cyclical plausibility checks. The value 0 disables the check. The default value 60 seconds should not be changed. CMD waiting time in seconds until a connection is re-established following connection failure. The default value is 120 seconds. CMD timeout in seconds. The default value is 120 seconds. Waiting time between two CMD messages. The default value is 50 ms. 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 > 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-6

34 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Nur für den internen Gebrauch 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 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. 3-7 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

35 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component 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 > 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 registration database. Click Yes to confirm this message 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-appears. A maximum of 64 systems/nodes can be configured 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 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. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-8

36 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Nur für den internen Gebrauch The entries are imported and the CMD configuration dialog re-appears. 3-9 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

37 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component 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. Display You will see a list of the CSTA clients (IP addresses) already configured for access: Entries are displayed with the following information: Column Name Call number TAPI 120 IP addresses Description Freely chosen name for the CSTA client (e.g. TAPI 120), enabling a single entry in the firewall to be identified. Enter the call number of the CSTA client. Enter the IP address of the CSTA client. 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 > To save entries, click Apply (to configure parameters in other tabs for example) or OK (to exit the configuration dialog and save changes). HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-10

38 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Nur für den internen Gebrauch > A confirmation message appears in both cases before the parameter values are saved in the database. Click Yes to confirm this message 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 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: CMD license parameters 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 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

39 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component 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: Parameter MAC ID Current license Date Limit date Licenses License History Description MAC ID, used for encryption. This is the MAC ID of the first LAN interface in the system network. 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. Details of license date, limit date and number of licenses with the current license code. Previous licenses are displayed here with the relevant information. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-12

40 tapi170_enkonfiguration.fm Configuring Components Configuring the CMD component Nur für den internen Gebrauch 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 CMD version information The version numbers of the components that are used and installed are listed in the Version tab HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

41 tapi170_enkonfiguration.fm Configuring Components Configuring the TSP component 3.3 Configuring the TSP component Starting the configuration dialog To edit TSP configuration parameters after installation, start the configuration dialog as follows: Activating the configuration dialog 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. > When using Microsoft Vista, Microsoft Windows 7 or Windows 2008 / 2008 R2 different confirmation prompts might appear during TAPI 170 configuration. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-14

42 tapi170_enkonfiguration.fm Configuring Components Configuring the TSP component Nur für den internen Gebrauch Configuration parameters 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 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation

43 tapi170_enkonfiguration.fm Configuring Components Configuring the TSP component 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 The parameters contain the following information: Parameter System CSTA link Call number CAPI-DLL Description For selecting the connected system. The following baud rates can be selected: OpenScape Office HiPath OpenOffice EE HiPath 2000 HiPath 3000 HiPath 5000 RSM (Multi node) (default) Connection type between TSP and the system. By default this is TCP/ IP and cannot be changed. Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation 3-16

44 tapi170_enkonfiguration.fm Configuring Components Configuring the TSP component Nur für den internen Gebrauch Parameter CAPI controller Baud rate IP address IP port Description Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. Connected to HiPath 5000 RSM (Multi node) this parameter is nor relevant. 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. 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. > 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 registration database. Click Yes to confirm this message. > 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. It is necessary to re-start the TSP (net stop tapisrv), for instance after modifying the connection type (CSTA link) 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 HiPath TAPI 170 V2.0 MultiNode Installation and Configuration, Administrator Documentation