HiPath Manager PCM V2.0 Administrator Manual

7/21/2019 HiPath Manager PCM V2.0 Administrator Manual

http://slidepdf.com/reader/full/hipath-manager-pcm-v20-administrator-manual 1/80

HiPath Manager PCM

Version 2.0

Administrator Manual





pcm_shbIVZ.fm

A31003-H2620-A100-1-76A9, 09-2004

HiPath Manager PCM V2.0, Administrator Manual 0-1

For internal use only Contents

Contents 0

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 Data Protection and Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 About the HiPath Manager PCM Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

1.2.1 Available Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31.2.2 Electronic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31.2.3 Terminology Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31.2.4 Document Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

1.3 Overview of Mouse Key Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 HiPath Manager PCM System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.2 Installation Routine – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.3 Starting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2.3.1 Installing HiPath Manager PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.3.1.1 Complete Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.3.1.2 Custom Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62.3.1.3 Creating Backup Directories and Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.4 Installing Individual Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.5 Basic Configuration of HiPath Manager PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

2.5.1 Importing Basic Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.5.2 Adding the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.5.3 Special System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.5.3.1 Inserting a Routing Prefix via CSTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.5.3.2 Correct Mulap Configuration for Use via the PCM . . . . . . . . . . . . . . . . . . . . 2-10

2.6 Checking Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.6.1 Setting up the Internet Information Server (IIS)

for LDAP Telephone Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.6.2 Checking or Manually Configuring DCOM Component Properties . . . . . . . . . . . 2-142.6.3 Checking Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

2.7 Updating HiPath Manager PCM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-182.8 Windows Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19



Contents For internal use only

A31003-H2620-A100-1-76A9, 09-2004

0-2 HiPath Manager PCM V2.0, Administrator Manual

pcm_shbIVZ.fm

3 HiPath Manager PCM Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1.1 Functional Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.1.2 Prerequisites for Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.1.3 Dependencies/Limitations Vis-À-Vis Other TAPI Applications . . . . . . . . . . . . . . . . 3-2

3.2 Starting, Logging in, Closing HiPath Manager PCM Administration . . . . . . . . . . . . . . . 3-33.2.1 Starting HiPath Manager PCM Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.2.2 Logging on to HiPath Manager PCM Administration . . . . . . . . . . . . . . . . . . . . . . . 3-33.2.3 Closing HiPath Manager PCM Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.3 Error and Event Reporting Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.4 User Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

3.4.1 Creating a New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.4.2 Editing the User Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.4.3 Administering Access Privileges for Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3.4.4 Deleting a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.4.5 Exporting a User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103.5 Administering General Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

3.5.1 Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.5.1.1 Importing the Configured Node Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.5.1.2 Editing Node Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123.5.1.3 Exporting a Node List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

3.5.2 Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153.5.2.1 General Properties of Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153.5.2.2 Importing Configured Extension Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153.5.2.3 Editing Extension Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

3.5.2.4 Exporting an Extension List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-173.6 PCM Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

3.6.1 Properties of PCM Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193.6.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-203.6.1.2 Telephone directory/LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-223.6.1.3 Discriminating call number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-233.6.1.4 Web links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

3.6.2 User Administration for PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-253.6.2.1 Editing a User for PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-253.6.2.2 PCM User Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-273.6.2.3 Exporting a PCM User List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

3.6.3 Destination Number Identification for External Calls . . . . . . . . . . . . . . . . . . . . . . 3-293.6.3.1 Creating a New Extension Number Entry for External Calls . . . . . . . . . . . . . 3-293.6.3.2 Deleting an Extension Number Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.7 Application-Specific Configuration Changes and System Settings. . . . . . . . . . . . . . . 3-303.7.1 HiPath Assistant - Routing Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-303.7.2 HiPath Assistant - Automatic Call Acceptance CSTA . . . . . . . . . . . . . . . . . . . . . 3-313.7.3 HiPath Assistant - Mulap Group Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-313.7.4 Internet Information Server - Internet Services Manager . . . . . . . . . . . . . . . . . . . 3-31



pcm_shbIVZ.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only Contents

4 HiPath Manager PCM Trace Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.2 Starting and Ending the Trace Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.3 Trace Monitor Screen Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.4 Print Setup for the Trace Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.5 General Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

4.5.1 Opening/Closing a Trace Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.5.2 Printing the Contents of a Trace Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.5.3 Deleting the Trace Window Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.5.4 Freezing the Trace Window Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.5.5 Arranging the Trace Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

4.6 Exporting Trace Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

5 Saving and Restoring Data for HiPath Manager PCM . . . . . . . . . . . . . . . . . . . . . . . . 5-1

6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1



Contents For internal use only

A31003-H2620-A100-1-76A9, 09-2004


pcm_shbIVZ.fm



INTRO.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only IntroductionData Protection and Data Security

1 Introduction

The HiPath Manager PCM (Personal Call Manager) is a browser-based application for config-

uring and administering call forwarding features. Personal settings can be accessed either withthe help of a local network PC system or by remote access via the intranet/Internet.

The PCM call handling functionality should not be confused with conventional call forwardingor conventional call destination lists. PCM features a user-specific, standalone forwarding func-tion based on its very own connection strategy. PCM is used to improve and speed up personalavailability during office hours, working hours and periods of absence.

Administrative PCM parameters and PCM users are configured by means of the HiPath Man-ager PCM Administration program (see Section , "HiPath Manager PCM Administration").

1.1 Data Protection and Data Security

Handling personal data

This system processes and uses personal data, amongst other things, e.g. in displays andwhen entering customer data.

In Germany, the processing and use of such personal data are subject to various regulationsof the Federal Data Protection Law (Bundesdatenschutzgesetz = BDSG). For other countries,please follow the appropriate national laws.

The aim of data protection is to ensure that the rights of individuals are not infringed uponthrough the use of their personal data. By protecting data against misuse during all stages ofprocessing, privacy legislation also protects the material interests of the individual and of thirdparties.

> HiPath Manager PCM Web is optimized for use in conjunction with Internet Explorer(V4.01 SP2 or higher). Deviations in terms of display and functionality may occur inother script-based browsers on account of browser-specific behavior. We thereforeonly recommend the use of Internet Explorer.



Introduction For internal use only

A31003-H2620-A100-1-76A9, 09-2004


INTRO.fm

Data Protection and Data Security

Guidelines for Siemens employees

Employees of Siemens AG are required to observe business and data secrecy laid down in thestatement of conditions of employment.

In order to ensure that the statutory requirements during service – (whether on-site or remote)– are consistently met, you should always observe the following rules. This safeguards the inter-ests of the customer and offers added personal protection.

Guidelines for handling personal data

You can contribute to ensuring data protection and data security by appreciating theproblem and acting in a responsible manner:

● Ensure that only authorized persons have access to customer data.

●

Take full advantage of password allocation options; do not inform unauthorized persons ofpasswords, e.g. by means of a written note.

● Ensure that no unauthorized person is able to process (store, modify, transmit, disable, de-lete) or use customer data in any way.

● Do not allow unauthorized persons to gain access to data media, e.g. on backup disks orprotocol printouts. This applies both to service calls and to storage and transport.

● Ensure that data media which are no longer needed are completely destroyed. Ensure thatnone of the papers are left behind for general access.

● Cooperate with your contacts in the customer’s company: this creates mutual trustand reduces your workload.



INTRO.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only IntroductionAbout the HiPath Manager PCM Documentation

1.2 About the HiPath Manager PCM Documentation

This section contains information on the technical documentation available for HiPath ManagerPCM.

1.2.1 Available Documents

Administrator Manual

This manual is addressed to the HiPath Manager PCM service engineer or administrator. It de-scribes the installation of HiPath Manager PCM and provides information on the necessarysteps for configuring and administering HiPath Manager PCM.

HiPath Manager PCM Operating Manual

The HiPath Manager PCM has its own operating manual, which is specially designed for theend user and explains everything in easy-to-follow steps.

1.2.2 Electronic Documentation

The above-mentioned manuals are available in electronic form as PDF documents on the CDsupplied with the product.

1.2.3 Terminology Conventions

To make for easier reading, the present documentation uses the abbreviated form "PCM" inplace of the full product name "HiPath Manager PCM".

The name of the PCM interface is "myPersonalWebManager".



Introduction For internal use only

A31003-H2620-A100-1-76A9, 09-2004


INTRO.fm

Overview of Mouse Key Functions

1.2.4 Document Conventions

The following conventions were adopted in these operating instructions to provide a clearer dis-tinction between the different types of information.

1. The individual steps for operating instructions are numbered.

● Items in lists are marked by a bullet.

Names of operating elements, such as keys and mask titles are printed in bold, e.g. Login Options.

1.3 Overview of Mouse Key Functions

>This symbol is used to indicate information to which you should pay particular atten-tion or that simplifies program operation.

7This symbol indicates high-priority information. This information must be observedto avoid damaging the system or losing data.

Terms Explanation

Click Press the left or right mouse button briefly

Double-click Briefly press the left mouse button twice in quick succession

Drag Click on an object or area and hold the left mouse button downDrag&Drop Click on an object or area, hold the left mouse button down, and move the

object to the required area. Then release the mouse button.

>The TAB. and RETURN= keys can be used to enter data.



Install.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only InstallationHiPath Manager PCM System Requirements

2 Installation

2.1 HiPath Manager PCM System Requirements

Hardware Structure

The HiPath Manager PCM server PC runs on a Windows 2000 Server operating system. Theminimum hardware requirements are detailed below:

To install the HiPath Manager PCM server software (MSDE, database, TSP, etc.), you will re-quire approx. 100 MB on your local PC. The processor performance required by the HiPathManager PCM server application depends partly on the number of times this application is ac-cessed. Also, the network topology can be another important factor in determining the systemload.

Components Description

PC Intel Pentium III, 700 MHz and 256 MB RAM, PS/2 mouse and keyboard

Hard disk 10-GB hard disk with high data throughput

Drives 3.5 inch, 1.44 MB; CD-ROM drive

Cards LAN adapter 10/100-Mbit LAN interface with QoS

Ports Two free serial ports

Monitor 17-inch SVGA color monitor

Operating system Windows 2000 Server licence with SP2; Internet Information Server

Browser Microsoft Internet Explorer version 4.01 SP2 or higher

Backup medium Medium and software (e.g. streamer or ZIP drive)

7When configuring the HiPath Manager PCM server PC in the customer LAN, there-fore, care should be taken that the components are really suitable for use in that con-text.



Installation For internal use only

A31003-H2620-A100-1-76A9, 09-2004


Install.fm

Installation Routine – Overview

2.2 Installation Routine – Overview

Please refer to the following description to familiarize yourself with the general installation rou-tine before beginning the actual installation.

The installation program permits both the basic installation of the HiPath Manager PCM, includ-ing its system administration component, and also the later installation of individual compo-nents. The table below lists the components installed.

The HiPath Manager PCM can be installed in Custom or Complete mode. Custom mode al-lows components to be excluded from setup.

● To perform a Complete setup, please refer to Section 2.3.1.1.

● To perform a Custom setup, please refer to Section 2.3.1.2.

● Information on how to perform an update can be found in Section 2.7.

The following software components are installed in a typical initial installation process:

Component Server PC

TAPI Service Provider 170 V1.0 yes

Administration yes

HiPath Manager PCM (basic package component), browser-based applicationfor setting up and administering personal call forwarding operations

yes

Trace Monitor (basic package component), analysis tool yes

MSDE SQL database server including service pack (basic package component) yesFeature Server (HiPath 5000 Feature Server, (basic package component), data-base server which controls HiPath 3000/5000 application access to the gateway.

yes

HiPath 3000/5000 Manager C (Client Setup) yes, option-al

HiPath 3000/5000 Manager E/I (must then be separately installed by rerunningthe server setup as described in Installing Individual Components).

yes

Update (brings all basic package components up-to-date). Depending on theUpdate version installed, this application may uninstall the component complete-

ly and then re-install it.

–



Install.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only InstallationInstallation Routine – Overview

General installation sequence (server PC)

1. Log on as administrator, insert the installation CD and start installation

2. Install the feature provider (if not yet installed)

3. Install the TSP (if not yet installed)

4. Install the MSDE

5. Install SP2 for the MSDE

6. Install the database and database update if appropriate

7. Install the PCM service, the HiPath Manager PCM and configure/register the components

8. Configure the data backup directory and connect the database




A31003-H2620-A100-1-76A9, 09-2004


Install.fm

Starting the Installation

2.3 Starting the Installation

1. Insert the installation CD.

The installation program is started via the autorun function. Alternatively you can initiateSetup via Windows Explorer under

<CD-ROM drive letter>:\setup.exe.

2. Select the language you require for the Setup browser. German and English versions arecurrently available.

The Important Information entry contains the latest installation descriptions and notes.

3. Click Install Server to install the HiPath Manager PCM.

2.3.1 Installing HiPath Manager PCM1. Click the entry Install server components for HiPath Manager V2.0. For more detailed

information on this topic, please refer to Section 2.3.1.1.

The Setup Wizard starts running.

2. Click Next and confirm the license agreements in the subsequent dialog. Then click Next.

3. Enter the name of the user and organization in the Customer Information mask. This in-formation is transferred to the operating system after being defined in conjunction with thecustomer.

4. Now select the language you require for the HiPath Manager PCM - myPersonalWeb-Manager.

The languages selected are for the HiPath Manager PCM client application; the adminis-tration user interface is available in German and English only.



Install.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only InstallationStarting the Installation

5. Then click Next.

The Setup Type mask appears.

In the Setup Type mask, you can choose between a Complete (see Section 2.3.1.1) andCustom setup (see Section 2.3.1.2).

2.3.1.1 Complete Setup

If the Complete option is selected, all available program features and components are installedand default path information is adopted.

1. Click Install.

System messages on the installation of Feature Server are displayed when the HiPathManager PCM is installed for the first time. Feature Server is a central service which pro-vides access to the node-specific system data.

2. Confirm these messages with OK.

The installation procedure starts. See also Section 2.3.1.2, "Custom Setup" for informationon the configuration and installation of additional components.

>It takes approx. 15 minutes to install the database engine (MSDE) for the firsttime.




A31003-H2620-A100-1-76A9, 09-2004


Install.fm

Starting the Installation

2.3.1.2 Custom Setup

By selecting Custom setup, you can choose which Feature Server components or features areto be installed.

Press the mask’s Help button for explanatory information on the various setup options.

The Space function provides an overview of the drives available on the server PC and theircapacity. Drives which do not have enough disk space are highlighted.

Via Change... you can enter an installation path that differs from the default.

1. Select the relevant components and features (see Section 2.3.1.1).

2. Click Next followed by Install.

This activates the installation process with the settings you made. The HiPath TAPI 170Service Provider is installed at a later stage of setup.



Install.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only InstallationInstalling Individual Components

Installing the TAPI Service Provider

Next, the HiPath TAPI 170 Service Provider is installed.

1. Confirm the subsequent message which prompts you to activate the ACD functionality withYes.

To configure it, open Telephone and Modem Options on theControl Panel (after basic server configuration).

For further information, please refer to the Online Help for the TAPI 170Service Provider.

2.3.1.3 Creating Backup Directories and Jobs

A backup directory must now be created for automatic data backup. The services for PCM are

then started.

1. Adopt the default settings where applicable. This directory is created on initial installation.

2. Backup jobs are saved on the SQL server after confirmation with OK.

Press Browse... to select a different backup directory from the default directory.

The installation procedure for HiPath Manager PCM is complete.You will now be requested to restart the PC. To avoid having to restart the PC again, firstperform the steps described below.

2.4 Installing Individual Components

HiPath TAPI 170, the HiPath 5000 server and HiPath 3000 Manager E (incl. deployment tool)and HiPath 3000 Manager I administration tools can be individually installed.

1. Display Setup and click Install Server.

2. Click the entry Installation of Individual Components.3. Choose the relevant component.

Now restart the server.

>The SQLServer Agent must be active for performing backup jobs. The start typemust be set to automatic for the service. This is automatically configured during thesetup operation.




A31003-H2620-A100-1-76A9, 09-2004


Install.fm

Basic Configuration of HiPath Manager PCM

2.5 Basic Configuration of HiPath Manager PCM

Now prepare the HiPath 3000 node for operation at HiPath Manager PCM as described in theservice manual.

2.5.1 Importing Basic Server Configuration

1. Activate HiPath 3000 Manager E.

2. Activate HiPath 5000 Server via the File - HiPath 5000 - Transfer menu or via the appro-priate button in the toolbar.

3. Specify the server you have just installed via the Find button and load the basic configura-tion by clicking the Server -> Manager button.

4. Click OK.

>The menu item File - New - HiPath 5000 Server is only used to create a CDBmemory generated offline.



Install.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only InstallationBasic Configuration of HiPath Manager PCM

2.5.2 Adding the Node

1. To add the node, activate HiPath 3000 in the File - HiPath 5000 - New menu. The followingwindow is displayed:

2. Select load from system and load the CDB by entering the IP address from the HiPath3000.

Then click Add Node in the next window.

3. Finally, rewrite the HiPath 3000 Manager E data to the server and reset the HG1500 cards.




A31003-H2620-A100-1-76A9, 09-2004


Install.fm

Checking Installation

2.5.3 Special System Configurations

2.5.3.1 Inserting a Routing Prefix via CSTA

You must enable the option Insert routing prefix via CSTA in HiPath 3000 Manager E, underSystem Parameters.../Plus Product Flags. Only by enabling this option can it be guaranteedthat incoming external calls will be recorded in a format that permits correct dialing by the call-back function of the WEB application.

2.5.3.2 Correct Mulap Configuration for Use via the PCM

Before a Mulap group (BasicMulap) in the PCM can be used as a PCM-supervised terminal oras a forwarding destination, this (these) Mulap group(s) must be set up as follows:

● One virtual station must be set up for each Mulap group and assigned to the Mulap group.

● The virtual station is only given the member parameter "acoustic signal"; all other stationsare configured as "Master" with "acoustic signal". All the other parameters of the "actually"existing members are optional.

● The virtual station does not need to be included in the TAPI line configuration, but all Mulapcall numbers and all individual station numbers must be included.

● The PCM user should be assigned not just any station in the group, but the Mulap call num-ber itself.

● When calls are forwarded to Mulaps, the Mulap call number should be entered in the PCM

accordingly as the forwarding destination.

2.6 Checking Installation

2.6.1 Setting up the Internet Information Server (IIS) for LDAPTelephone Directory Access

Where an LDAP server for directory enquiries is provided in a network (domain), Windows NT/ Windows 2000 security mechanisms will normally have been set up for controlling access. As

a rule, registered and logged-on system users have the right of access to this server.This is not the case when access is via a Web application running on the Web Server insteadof the client PC environment (browser). In this case the IUSR_[server name], which is automat-ically set up locally on the Web Server, identifies every user and every access as a standarduser with standard rights. However, this user is not known to the network (domain) or the LDAPserver. Queries to the LDAP server are therefore rejected on the grounds of insufficient rights.

There are two ways of achieving this anonymous access:



Install.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only InstallationChecking Installation

1. by giving the local IUSR_[Server name] user the right to address the LDAP server in thedomain or

2. by reassessing the anonymous accesses to the Web and thus to the LDAP server as being

from a user registered in the network (domain) (or from a domain user created specially forthis purpose). This can be achieved by making the following settings on the HiPath Man-ager PCM server PC on which the Web Server "Internet Information Server" is running:

– Select Start - Programs - Administrative Tools to activate the Internet ServicesManager.

– Under Internet Information Services, double-click the computer name and then the De-fault Web Site entry.

– In the context menu (right mouse button) of the ManagerPCM2 entry, click on Prop-erties and select the Directory Security tab in the subsequent mask, Properties ofManagerPCM2.




A31003-H2620-A100-1-76A9, 09-2004


Install.fm


– Click Edit in the Anonymous Access and Authentication Control area. The Au-thentication Methods dialog box is displayed.



Install.fm

A31003-H2620-A100-1-76A9, 09-2004



– Activate the Allow Anonymous Access checkbox and click Edit to enter the anony-mous user.

– In the Anonymous User Account dialog box, enter the name and password of other(domain) users and deactivate the option Allow Password Control by IIS.

– After confirming this with OK, you will be prompted to enter the password again.




A31003-H2620-A100-1-76A9, 09-2004


Install.fm


2.6.2 Checking or Manually Configuring DCOM Component Properties

The configuration steps described below are performed automatically during the installationprocess and are only described here for checking purposes.

1. To open the DCOM configuration properties, click Start, Run, enter dcomcnfg as the inputparameter and then click OK.

The Distributed COM Configuration Properties mask appears.

2. Check the default under Default Access Permissions / Edit Default... in the Default Se-curity tab to see whether the user Everyone is configured with Allow Access privileges.

3. Check the default under Default Launch Permissions / Edit Default... to see whether theuser Everyone is configured with Allow Launch privileges.

4. Check the following settings in the Default Properties tab (see mask below):



Install.fm

A31003-H2620-A100-1-76A9, 09-2004



5. Applications tab: select the PCM2 application and activate Properties...: Adopt the set-tings shown in the following masks for Location, Security and Identity.




A31003-H2620-A100-1-76A9, 09-2004


Install.fm


Location tab

Security tab



Install.fm

A31003-H2620-A100-1-76A9, 09-2004



Identity tab

This is where the HiPathAdmin user automatically created on setup must be selected.

6. Confirm your entries with OK.

7. The computer must be rebooted after changing the DCOM settings.

2.6.3 Checking Services

1. Select Start, Settings, Control Panel, Administrative Tools to open the Services man-agement console.

The following services must be started:

Service

● PCM2 - Personal Call Management 2.0

● MSSQL Server

● SQL Server Agent

● HiPath DB Server

● Telephony (TAPI)




A31003-H2620-A100-1-76A9, 09-2004


Install.fm

Updating HiPath Manager PCM Components

2.7 Updating HiPath Manager PCM Components

In general, all components are brought up to date in the course of an update. Depending on theversion installed, an update may uninstall the component completely and then re-install it. Sep-

arate updates are available for server and client applications.Please read the latest information in the readme.doc file on the installation CD before updatingthe software components installed.

1. Insert the installation CD if necessary.

The installation program is started via the autorun function. Alternatively, you can start thesetup from Windows Explorer by selectingCD-ROM drive letter\setup.exe.

2. Select the language you require for the setup browser.

3. Click Install Server; then click Server Update.

4. Follow the on-screen user prompts.

Restart the PC once the update procedure is complete.

>All active applications must be closed down before an update. Use the ServicesControl Manager to exit the Telephony and HiPath Database Server services.

7

For security reasons, you should make a backup of the TAPI Service Provider con-figuration (configuration and lines) and the CDB for the connected system.



Install.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only InstallationWindows Settings

2.8 Windows Settings

This chapter describes how you can optimize the Windows 2000 Server operating system forthe operation of HiPath Manager PCM.

Component Description

Optimizing the physicalmemory

Windows 2000 Server is normally optimized to maximumthroughput as a file server. For a HiPath 5000 server, however,significantly less memory is needed for the system-wide diskcache.To optimize the memory go to Settings – Network and Dial-upConnections – Local Area Network – Properties – File andPrinter Sharing for Microsoft Networks – Properties and se-lect the option Balance.

Optimizing the virtualmemory

To do this, go to Settings – Control Panel – System – Advanced – Performance Options – Virtual memory – Change and setthe Total paging file size for all drives to 512 MB.The same values should be entered for the virtual memory’s up-per and lower thresholds so that the paging file does not have tobe extended during operation.

Optimizing availability If Windows 2000 crashes (blue screen), it creates a file containingdebugging information from the paging file the next time the sys-tem starts. If the size of this file is the same size as the system’sphysical memory, almost all of the virtual memory will be used for

generating this file during system startup.This may cause certain services on the HiPath 5000 server to ex-perience problems in starting up. To recover this problem, youshould go to Control Panel – System – Advanced – Startupand Recovery and select the option (none) under Write Debug-ging Information.All other options are viable. The Auto restart option forces an au-tomatic restart if Windows 2000 crashes, thus considerably in-creasing the server’s availability.

SMTP service The SMTP service in Windows 2000 should always be disabled

as HiPath 5000 provides its own SMTP link which may conflictwith the Windows 2000 service. To do this, go to Start – Settings – Control Panel – Add/Remove Programs – Add/RemoveWindows Components – Internet Information Service – De-tails – remove the SMTP service.




A31003-H2620-A100-1-76A9, 09-2004


Install.fm

Windows Settings

HiPath Manager PCM and Internet Information Server

The option "Cache ISAPI Applications" must not be disabled.This option can be found under Start - Programs -AdministrativeTools - Internet Services Manager by navigating to Default WebSite – Properties – Home Directory – Configuration – Appli-cation Mapping.If the option were disabled, the Personal Call Manger would loseits "memory" of the users currently logged on and the error mes-sage "You are not logged on..." is displayed permanently.

Application log Configure the following by right-clicking Properties in the Win-dows Event Viewer for system and application protocol: 'Over-

write events as needed' and set 'Maximum log size' to approx. 2MB.

Component Description



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM AdministrationIntroduction

3 HiPath Manager PCM Administration

3.1 Introduction

HiPath Manager PCM Administration is a program for updating the administrative parametersfor the applications. These parameters are saved in the central database created for the appli-cation and, where applicable, read and evaluated by the PCM. HiPath Manager PCM Adminis-tration belongs to the HiPath Manager PCM program package.

The display of HiPath Manager PCM Administration conforms to the Windows 2000 manage-ment console. For information on the general functions and basic operation of the managementconsole, please refer to the Windows 2000 documentation or online help. This manual thereforeonly provides a brief description of the general user interface.

3.1.1 Functional Overview

HiPath Manager PCM Administration manages parameters for the following functional areas:

User Administration

● for HiPath Manager PCM Administration itself

● for the HiPath Manager PCM

General Settings

● for importing and administering node information (configured PBXs in the network)

● for importing and administering extension information for the configured nodes

Personal Call Management

● for administering the general parameters for PCM

● for administering the parameters for PCM users

● for administering the call number detection parameters for external calls



HiPath Manager PCM Administration For internal use only

A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

Introduction

3.1.2 Prerequisites for Use

HiPath Manager PCM Administration must be installed on the server PC with an appropriatedatabase before it can be used. HiPath Manager PCM Administration is also started there for

parameter processing.

3.1.3 Dependencies/Limitations Vis-À-Vis Other TAPI Applications

If several TAPI applications are monitoring TAPI lines through the third-party TSP, there may beconflict between two or more applications using a line (station) concurrently. For instance, ifPCM and the HPCO call center system are using the same line, one application could take thecall away from the other, thereby perhaps causing processing and statistic errors. For this rea-son, we strongly recommend separating the call number ranges or assigning only one TAPI ap-plication to the individual stations.

Limitations in certain constellations

The following constellations have the limitations described:

● PCM users with an assigned station number (Mulap), an IP phone, Anates, optiClient 130s,optiSet entry cannot activate or deactivate the PCM via a telephone key, because thesetelephones do not have keys that can be monitored.

● If changes are made to the PCM user-specific parameters through the HiPath ManagerPCM Administration program, these changes will be automatically taken over when PCMcall handling is started. It is not necessary to restart the user-specific call handling actions.Services are not restarted, however, following changes to general PCM parameters, suchas properties of PCM, discriminating call numbers or identification of external calls. Pleaseremember to restart a service after making changes to it.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM AdministrationStarting, Logging in, Closing HiPath Manager PCM Administration

3.2 Starting, Logging in, Closing HiPath Manager PCMAdministration

3.2.1 Starting HiPath Manager PCM AdministrationA program group called HiPath Manager PCM in which the Administration is integrated is cre-ated during HiPath Manager PCM Server installation.

To start HiPath Manager PCM Administration select Start - Programs - HiPath ManagerPCM Administration.

3.2.2 Logging on to HiPath Manager PCM Administration

The login mask appears when the program is started.

1. The User id field contains the ID of the last user to log in. You can enter another ID.

2. In the Password field, enter the password associated with the ID. If the input is correct,HiPath Manager PCM Administration is started. If the input is incorrect, e.g. wrong pass-word or unknown user ID, an appropriate error message appears. This must be confirmed.You are then returned to the login window.

Provided you have appropriate access privileges, you can now start parameter administration(see also Section 3.4.3, "Administering Access Privileges for Users").

3.2.3 Closing HiPath Manager PCM AdministrationHiPath Manager PCM Administration is ended by the standard Windows procedure, either byclicking the system menu and selecting Close, by double-clicking the system menu or with thekey combinationh +D .




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

Error and Event Reporting Procedures

3.3 Error and Event Reporting Procedures

Important events, information or errors in the configuration of parameters in HiPath ManagerPCM Administration are logged automatically in the Event Viewer of the Windows 2000 Device

Manager.This Event Viewer can be activated in two ways:

1. Select Settings - Control Panel - Administrative Tools - Device Manager.

2. Activate Event Viewer in HiPath Manager PCM Administration in the branch Event Viewer(Local).

Device Manager appears in the layout of a Windows 2000 management console. The event ad-ministration for HiPath Manager PCM Administration events can be found in the branch Sys-tem - Event Administration - Application.

HiPath Manager PCM Administration entries are archived with the source "ADMIN", the admin-istrator’s user ID and a code (e.g. message, database, etc.).

The event administration log might contain the following entries:

● Starting/ending administration

● Import information

● Starting/ending processing individual configuration elements

● Information about deletions

● Faults or problems that occurred

● Interrupted actions, e.g. login cancellation

The log can, for example, be displayed in various views, exported to a file or else deleted. Logproperties such as maximum log size, action to be taken when this size is reached, or filter set-tings, can be configured.

>This manual does not explain how to operate the Windows 2000 management con-sole or the specific operating and configuration options offered by Event Administra-tion. This know-how is a prerequisite for users. For more information, please refer to

the Windows 2000 documentation or the online help.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM AdministrationUser Administration

3.4 User Administration

The user ID, password and additional user information (e.g. user names) are administered un-der User Administration for each user in HiPath Manager PCM Administration. Users can thus

be administered for the following applications:● Users for HiPath Manager PCM Administration itself

● Users for the HiPath Manager PCM

To administer user information in HiPath Manager PCM Administration, the user must belogged in with access privileges for at least HiPath Manager PCM Administration (applica-tion) and System Administrator (function).

When HiPath Manager PCM Administration is started, User Administration can be found in theHiPath Manager PCM Administration - User Administration branch in Tree View:

3.4.1 Creating a New User

To create a new user, proceed as follows:

1. Open the User Administration branch in Tree View.

2. Mark the entry User.

3. Open the context menu there or in the detail view and select New....

The New User mask appears:




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

User Administration

4. Enter the following data:

5. Confirm your input by clicking OK.

6. If the entries under Password and Confirm new password match, your information issaved, the mask is closed and the new user is displayed in detail view.

Field name Meaning

User id User id

Description Description of the user, e.g. name or area of activity

Apostrophe Form of address used for the user. This information is not used or

displayed in HiPath Manager PCM Administration; this field canremain blank.

Password User’s password. The password uses hidden numbering andmust contain at least 3 characters.

Confirm new password For repeated password entry. The new user is only created if theentry in Password corresponds to this entry. The password is notcase-sensitive. The entry in this field also uses hidden number-ing.

>A field length (number of characters) of 8 is always shown in the Password andConfirm new password fields once the user data is saved, even if the pass-word saved contains a different number of characters. When entering data inthese fields, the real input length is displayed.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



3.4.2 Editing the User Entry

Apart from the user ID, all values defined automatically when the new user was created can beedited. To modify a user’s ID, delete the user with the old ID and create a new user with the new

ID.To edit a user, proceed as follows:

1. Open the User Administration branch in tree view and mark the entry Users.

2. Open the context menu for the user to be edited in detail view and select Edit....

3. The Edit User - <user ID> mask appears.

4. Edit the values in the usual manner and confirm your inputs with OK.

5. If the entries under Password and Confirm new password match, your information is

saved, the mask is closed and the user is displayed in detail view.

>A field length (number of characters) of 8 is always shown in the Password andConfirm new password fields, even if the password saved contains a differentnumber of characters. When entering data in these fields, the real input lengthis displayed.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

User Administration

3.4.3 Administering Access Privileges for Users

When creating a new user, this user is configured in the system without activated access priv-ileges. Privileges are assigned to the user in a separate step.

To administer access privileges for a user, proceed as follows:


2. Open the context menu for the user whose access privileges you want to configure in detailview and select Access Privileges....

3. The Access Privileges - <user ID> mask appears.

4. Activate or deactivate the relevant access privileges and confirm your inputs with OK. Yourinputs are saved and will activate the next time the user logs in.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



The following access privileges can be set:

3.4.4 Deleting a UserTo delete a user, proceed as follows:


2. In detail view, open the context menu for the user to be deleted and select Delete.

3. Confirm the security prompt. The user will be deleted when you press OK.

Application Function Meaning

HiPath ManagerPCM Administra-tion

CCM-Administrator Not relevant for PCM.CM-Administrator The user can enter settings for PCM properties.

System-Administrator

In HiPath Manager PCM Administration, the usercan administer users and make settings for gener-al parameters.The branches HiPath Manager PCM Adminis-tration - User Administration and HiPath Ad-ministration - General Settings are available tothis user in tree view after login.

WACC-

Administrator

Not relevant for PCM.

Personal CallManagement

PCM user The user can start HiPath Manager PCM.

>The branch HiPath Manager PCM Administration - About HiPath AllServeAdministration can be viewed by any user of HiPath Manager PCM Adminis-tration, even if he does not possess any access privileges.

>The SERVICE user is reserved for the service technician and cannot be deleted.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

User Administration

3.4.5 Exporting a User List

To export the user information displayed to a file, proceed as follows:

1. Open the User Administration branch in tree view and mark the entry Users.2. Open the context menu, select Export List....

3. Select the destination directory for the export file in the ensuing mask and give the exportfile a name.

4. After pressing Save, the column-based user information shown in detail view is exportedwith the column headers to the specified file.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM AdministrationAdministering General Settings

3.5 Administering General Settings

The following information is administered and updated during the configuration of general set-tings in HiPath Manager PCM Administration:

● Information about the nodes configured in the TCP/IP network (Hicom PBXs)

– Importing the configured nodes

– Editing the node data

● Information about the extensions configured at the nodes

– Importing the extensions configured on the nodes

– Editing the extension data

To administer general settings in HiPath Manager PCM Administration, the user must belogged on with access privileges for at least HiPath Manager PCM Administration (applica-tion) and System Administrator (function), see also Section 3.4.3, "Administering AccessPrivileges for Users").

When HiPath Manager PCM Administration is started, the general settings are located in theHiPath Manager PCM Administration - General Settings branch in tree view:




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

Administering General Settings

3.5.1 Nodes

HiPath Manager PCM considers the Hicom PBXs configured in the TCP/IP network as nodes.Nodes cannot be created or deleted in HiPath Manager PCM Administration. Node data is

transferred to the Feature Server by means of data import via the network, displayed in Admin-istration and made available for further processing. Normally there is only one node availablein HiPath Manager PCM (Standalone).

3.5.1.1 Importing the Configured Node Data

To import the configured node data, proceed as follows:

1. Open the HiPath Manager PCM Administration - General Settings branch in tree view.

2. Mark the entry Nodes.

3. Open the context menu and select All Tasks - Load Node Information.

The node data is imported. During an import operation, new node data is incorporated andinformation on existing nodes is updated. Information available in Administration and noton the node, such as a description of the node, is not overwritten during an import job.

If errors occur when importing node data, these are reported and logged in the Event View-er under Device Manager in Windows 2000 (see Section 3.3, "Error and Event ReportingProcedures").

The nodes available after the import are listed in detail view.

3.5.1.2 Editing Node Entries

Various parameters are still needed after importing the node data. You can update this datawhen editing the node call information.

To edit node data, proceed as follows:


2. Mark the entry Nodes.

3. In detail view, open the context menu for the node to be edited and select Edit....



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



The Edit Node - <node ID> mask appears

Enter the following data:

Field name Meaning

Node id Output field for the node’s ID which is read out of the node’s con-figured data and transferred to HiPath Manager PCM Administra-tion. This ID is used to reference the node internally in Administra-tion. Consequently, the repeated import of (updated) nodeinformation is possible without overwriting existing node data. Thenode ID cannot be changed.

Node name Name of the node used in HiPath Manager PCM Administration forthe node.

Description Description of the node; this can, for example, indicate the locationof the node.

IP address IP address of the node in the TCP/IP network; this is read out ofthe configured node data.

Currency symbol Currency symbol of the node




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm


4. After editing the data, press OK to save your inputs. The edited node data is displayed in

detail view.

3.5.1.3 Exporting a Node List

To export the node information displayed to a file, proceed as follows:

1. Open the General Settings branch in tree view and mark the entry Nodes.

2. Open the context menu, select Export List....


4. After pressing Save, the column-based node information shown in detail view is exportedwith the column headers to the specified file.

Rate of exchange Rate of exchange for the node currency (e.g. USD, GBP, etc.).This field is not relevant to the HiPath Manager PCM in its standa-

lone marketing variant.Country code Output field with the country code of the node in accordance with

the configured node data.

Area code Output field with the area code of the node in accordance with theconfigured node data.

System call number Node system call number.After updating the HiPath Manager PCM, this field must be updat-ed (see also Canonical system call no.)

Canonical system call

no.

The system call number is determined from the entries in the fields

Country code, Area code and System call number and is outputin canonical format. HiPath Manager PCM (Personal Call Manag-er) needs the system call number to be correctly displayed in ca-nonical format so that it can compare it with the canonical systemcall number stored in the telephone directory and thereby deter-mine whether the station is to be called internally or externallywhen dialing from the telephone directory (the station is always incanonical format in LDAP).

Tax rate (%) Applicable tax rate for the node (e.g. VAT) in per cent.

Field name Meaning



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



3.5.2 Extensions

Information about configured node extensions is required in HiPath Manager PCM Administra-tion for further processing. Extension data cannot be created or deleted in Administration, but

is imported into the HiPath Manager PCM database via the network and displayed and madeavailable for further processing in Administration.

3.5.2.1 General Properties of Extensions

3.5.2.2 Importing Configured Extension Data

To import extensions configured on the node, proceed as follows:


2. Mark the entry Extensions.

3. Open the context menu and select All Tasks - Load extension information.

The extension data is imported. During an import operation, new extension data is incor-porated and information on existing extensions is updated. Information available in Admin-istration and not on the node, such as a description of the extension, is not overwritten dur-ing an import job.

If errors occur when importing extension data, these are reported and logged in the EventViewer under Device Manager in Windows 2000 (see Section 3.3, "Error and Event Re-porting Procedures").

The extensions available after the import are listed in detail view.

The default settings made in the Properties of extension mask for all new extensions createdby data import apply to immediate printout and destination number suppression (cf. Section3.5.2.1). These settings can be adapted for each individual extension after the import operation(cf. Section 3.5.2.3).

>The entries in the extensions properties dialog box are only relevant to the HiPathManager PCM in its sales variants for HiPath AllServe or HiPath 3000/5000, but notfor the standalone version.No description is therefore included in the present HiPath Manager PCM documen-

tation for the standalone variant.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm


3.5.2.3 Editing Extension Entries

Various parameters are still needed after importing the extension data. You can update thisdata when editing the extension information.

To edit extension data, proceed as follows:


2. Mark the entry Extensions.

3. In detail view, open the context menu for the extension to be edited and select Edit....

The Edit Extension - <extension number> mask appears. Select the General tab in thismask.


5. After editing the data, press OK to save your inputs. The edited extension data is displayedin detail view.

Field name Meaning

Extension Extension number

Description Description of the extension, e.g. department or owner function

Name Name of the extension owner as per the name entered at the node

Node Node at which the extension is configured.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



3.5.2.4 Exporting an Extension List

To export the extension information displayed to a file, proceed as follows:

1. Open the General Settings branch in tree view and mark the entry Extensions.



4. After pressing Save, the column-based extension information shown in detail view is ex-ported with the column headers to the specified file.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

PCM Management

3.6 PCM Management

Overview

The following information is administered and updated during the configuration of parametersfor HiPath Manager PCM in HiPath Manager PCM Administration:

● Supplementary parameters for users with access to HiPath Manager PCM:

● External call destination number identification

HiPath Manager PCM Administration does not provide further information on functions and pa-rameters for operating HiPath Manager PCM; these can be found in the user interfacemyPersonalWebManager and in the associated PCM user manuals.

To administer the PCM parameters in HiPath Manager PCM Administration, the user must be

logged in with access privileges for at least HiPath Administration (application) and SystemAdministrator (function), see also Section 3.4.3, "Administering Access Privileges for Users").

When HiPath Manager PCM Administration is started, the PCM parameters are located in theHiPath Manager PCM Administration - Personal Call Management (PCM) branch in treeview:



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM AdministrationPCM Management

3.6.1 Properties of PCM Management

General settings for call forwarding in HiPath Manager Personal Call Management can bemade in the Properties of PCM mask in Administration. To do this, proceed as follows:

1. Open the HiPath Manager PCM Administration - Personal Call Management (PCM) branch in tree view.

2. Open the context menu there and select the entry Properties...

You can edit parameters in the following tabs:

– GeneralGeneral settings for call and pause times and display texts

– Telephone directory/LDAPSettings for the LDAP telephone directory

– Discriminating call numberConfiguration of system-wide discriminating call numbers to which the forwarding ofcalls can be prevented.

– Web linksCentral configuration of the homepages/URLs available in PCM for users.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

PCM Management

3.6.1.1 General

The parameters configured here are default parameters which will be adopted as a new PCMuser’s personal parameters. Users can edit their individual parameters in PCM.

1. Select the tab General in the Properties of PCM mask.

The following mask appears:


Field name Meaning

Call time per call for-warding (s)

Call time in seconds at one call destination before the PCM for-wards the call to the next destination.

Time unit per pausefunction ’P’

Pause time in seconds before a call is forwarded to enable call ac-ceptance or to modify the call management individually eventhough call handling has been configured. PCM users can enterthe pause function in their configured forwarding destination lists,if needed.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



3. Switch to the required tab if you wish to edit more parameters. Click OK to save your inputsand exit the dialog.

Forwarding monitor-ing canceled after

Here you can define the conditions under which call forwardingmonitoring should be canceled. You can choose from the following

options:● Call time expires at last destination● Forwarding to last destination● Call acceptance or hang upThe PCM can forward only one call at a time. Further calls will re-main at the telephone until the ongoing forwarding monitoring ac-tivity is finished.

(Display text)With activated PCM

Display text that should appear on the terminal while call handlingis activated.● If the option Continually display activation text is not en-

abled, this text will be displayed only for the duration of timeentered under Message display time (s) after call handling isactivated.

● If the option Continually display activation text is enabled,this text will be continually displayed while call handling re-mains active.

(Display text)If call handling is de-activated

Display text that should appear on the terminal while call handlingis activated.● This text appears when call handling is deactivated and re-

mains visible for the duration of deactivation.

Continually displayactivation text Enable this option if the display text on the terminal should be per-manently displayed after activation.

Message display time(s)

Duration of the text display on the terminal (in seconds) when callhanding is activated.

Field name Meaning




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

PCM Management

3.6.1.2 Telephone directory/LDAP

The LDAP telephone directory set up here is adopted by default as the new PCM user’s per-sonal parameters. However, users can also set up another telephone directory or select other

optional discriminating criteria, such as Organization, as part of their individual user settings inPCM.

1. Select the tab Telephone directory/LDAP in the Properties of PCM mask.


2. Enter the following data under LDAP parameters:

Field name Meaning

Server (name or IP) Name or IP address of the LDAP server (telephone directory serv-er)

base of search (op-tional)

You can specify a particular base where the search for entriesshould start in the LDAP folder in the base of search field. The en-tries can be made in either of two formats:● <Level 3> =<Name>, <Level 2> =<Name>, <Level 1> =<Name> ● or

<Level 1> =<Name> / <Level 2>=<Name> / <Level 3> =<Name> If you do not specify a restrictive search base, the entire LDAP fold-er will be the search base.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004




3.6.1.3 Discriminating call number

When setting their forwarding options, PCM users can specify that calls may also be forwardedto a redirected or forwarded station. Users can deactivate forwarding to call numbers storedsystem-wide, such as voicemail, collective call numbers, ACD groups, etc, because forwarding

to such call numbers is perhaps not desirable or may cause problems in the further course ofcall forwarding. These system-wide call numbers are recorded here.

1. In the Properties of PCM dialog box, select the Discriminating call number tab.

This opens the following dialog box with a list of the configured discriminating call numbers,stating the call number and description:

LDAP field descrip-tors

To ensure that LDAP entries are correctly mapped for users inmyPersonalWebManager, the LDAP folder field names that

should be displayed in myPersonalWebManager column informa-tion must be entered under LDAP field descriptors.

Field name Meaning




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

PCM Management

2. Click Add to record another discriminating call number. In the next mask, enter the Callnumber and the respective Description and confirm with OK. The mask closes and thenew call number appears in the list.

3. To remove a discriminating call number from the list, select the call number and click Re-move. The discriminating call number is deleted.


3.6.1.4 Web links

The PCM browser user interface ("myPersonalWebManager") features a Homepages fieldwith a list of link addresses for direct selection by PCM users. The system-wide entries in thislist are made centrally here in the Administration program.

1. In the Properties of PCM dialog box, select the Web links tab.

This opens the following dialog box with a list of the Web links configured, stating the Webaddress/URL and description:

2. Click Add to record an address. In the next mask, enter the Web address/URL and therespective Description and confirm with OK.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



The mask closes and the new Web address appears in the list.

3. To remove a Web address from the list, select the call number and click Remove. The Webaddress is deleted.


3.6.2 User Administration for PCM

3.6.2.1 Editing a User for PCM

Users who have been created in PCM User Administration and have access to HiPath ManagerPCM are assigned a user ID and password. Specific additional settings can now be adminis-tered for the PCM user in PCM User Administration. To do this, proceed as follows:

1. Open the Personal Call Management (PCM) entry in tree view.

2. Mark the entry PCM User Administration.

The detail view lists all users who are configured in PCM User Administration and are per-

mitted to start PCM, i.e. those for whom the access privileges Personal Call Manager (ap-plication) and PCM user (function) are activated (see also Section 3.4.3, "AdministeringAccess Privileges for Users").

3. Open the context menu for the user to be edited in detail view and select Edit....

The Edit PCM User - <user ID> mask appears:

4. Select the General tab.

>Internal or external URLs with different protocols (http://, https://, file://,etc.) can be entered. It is therefore important to enter the complete URL includingthe protocol.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

PCM Management


Field name Meaning

User User ID based on the definition in the User Administration.The field is an output field; inputs are not accepted.

Description User name based on the definition in the User Administra-

tion. The field is an output field; inputs are not accepted.Extension List field for selecting the user extension. All configured ex-tensions that have not yet been assigned to a user areavailable for selection.

Type of terminal List field for selecting the PCM user terminal type. The ter-minal type determines which and how many keys are avail-able to PCM users for configuring the activation/deactiva-tion of their standard call handling. You can choose fromthe following options:● optiset E basic, optiPoint 500 entry●

optiset E standard● optiset E comfort & memory, optiPoint 500 basic &standard

● optiPoint 500 advanced, optiPoint 600 office● IP Phones and IP Clients● other terminals and groups● analog terminals



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



Differences and restrictions for terminal types

– other terminals and groups

cannot accept (but can forward) a call when Web call monitoring is active,cannot initiate callbacks from caller lists,cannot use the entire CTI dial functionality (disabled),cannot configure a PCM key.

– analog terminals

cannot accept (but can forward) a call when Web call monitoring is active,can initiate callbacks from caller lists but cannot clear down the call,can use the entire CTI dial functionality but cannot clear down the call (disabled).

– IP terminals and softphones (clients)

cannot configure a PCM key– all other terminal types

have the exact same functionalities as the physical terminal (for example, number ofkeys)

6. Click OK to save your inputs.

3.6.2.2 PCM User Status

PCM users can activate/deactivate the individually configured call handling. Call handling acti-vated for a specific user can also be deactivated via the Administration program. To do this, pro-ceed as follows:


2. Mark the entry PCM User Administration.

The detail view lists all users who are configured in PCM User Administration and are per-mitted to start PCM, i.e. those for whom the access privileges Personal Call Manager (ap-plication) and PCM user (function) are activated (see also Section 3.4.3, "AdministeringAccess Privileges for Users").

3. Open the context menu for the user to be edited in detail view and select Edit....The Edit PCM User - <user ID> mask appears:

4. Select the Status tab.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

PCM Management

The current status is displayed, i.e. PCM activated or PCM deactivated. Click Deactivate to disable an active call handling.


3.6.2.3 Exporting a PCM User List

To export the displayed PCM user information to a file, proceed as follows:1. Open the Personal Call Management (PCM) branch in tree view and mark the entry PCM

User Administration.



After pressing Save, the column-based PCM user information shown in detail view is exportedwith the column headers to the specified file.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004



3.6.3 Destination Number Identification for External Calls

PCM must be able to recognize external calls in order to perform internal call monitoring. Youmust therefore enter:

● all configured trunks

● all routing codes (if configured)

● all external connections in accordance with the HiPath 3000 Manager E dial plan (if con-figured)

Enter the HiPath 3000 system here so that the PCM can recognize the appropriate externalconnections.

3.6.3.1 Creating a New Extension Number Entry for External Calls

To create a new extension number entry, proceed as follows:


2. Mark the entry External Call Destination Number Identification. All configured exten-sion number entries are listed in detail view.

3. Open the context menu in detail view and select New....

The mask Destination Number Identification for External Calls appears:




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm

Application-Specific Configuration Changes and System Settings



3.6.3.2 Deleting an Extension Number Entry

To delete an extension number entry, proceed as follows:

1. Open the Personal Call Management (PCM) branch in tree view and mark the entry Ex-ternal Call Destination Number Identification.

2. Open the context menu for the entry to be deleted in detail view and select Delete.

3. Answer the ensuing security prompt with OK, the entry is deleted.

3.7 Application-Specific Configuration Changes and SystemSettings

3.7.1 HiPath Assistant - Routing Prefix

To ensure that the callback functionality works properly, incoming external calls must be loggedwith the correct CO codes in HiPath Manager PCM Web. This is achieved in HiPath 3000 Man-ager E by setting the flag Direction prefix send via CSTA under Settings/System parame-ters.../Plus Products Flags and entering the CO code configured for the HXG route to the COsystem (for example, "0") under “2nd trunk code” in the Settings/Lines/networking.../Routes tab.

Field name Meaning

Selected digits The trunk, the routing code or the dial plan entry in accor-dance with HiPath 3000 Manager E for initiating an exter-nal call.

Description Description of the trunk, the routing code or the dial planentry.

>The extension number bands in directly connected series systems or satellite sys-tems must also be configured here, e.g. for all stations on the 300-399 extensionnumber band --> dialed digit "3" or for all stations on the 670-679 extension number

band --> dialed digits "67". In the case of mixed extension number configuration, thisconfiguration must, where applicable, be broken down into the station number. Spe-cial external tie trunk connections, such as a voicemail solution, must be configuredaccordingly.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM AdministrationApplication-Specific Configuration Changes and System Settings

3.7.2 HiPath Assistant - Automatic Call Acceptance CSTA

To make the callback functionality more convenient, set the flag autom. connection, CSTA un-der Settings/Set up station .../Station/Param/Flags. If this is set, the loudspeaker automati-

cally activates when you initiate a callback. The calling PCM user can set up the call withoutlifting the handset. If you do not set this flag, you will not be able to clear down a callback thatis still waiting at your terminal and has not yet been routed to the destination. In this case, theerror message "Unable to find call" appears.

3.7.3 HiPath Assistant - Mulap Group Configuration

Each Mulap group should be assigned to a separate virtual station under Settings/Incomingcalls.../Groups/Hunt groups if you want a Mulap group to be monitored by an application,such as HiPath Manager PCM. The real group members (optiset/optiPoint, CMI) are assigned

the member parameters Master, Acoustic call and Automatic seizure outgoing (A). The vir-tual station is only assigned the member parameter Acoustic call. The Mulap group numbermust be configured in the HiPath TAPI 170’s TAPI configuration.

3.7.4 Internet Information Server - Internet Services Manager

When using the HiPath Manager PCM telephone directory over an LDAP server, you may en-counter access difficulties if the LDAP server present in the domain performs user authentica-tion. Authentication over the HiPath Manager PCM Web pages is normally performed withoutthe knowledge of other network components, that is, it is performed over an anonymous useraccount that was automatically configured specially for IIS and that is not known to other serv-ers in the network. This results in error messages or blank search results following a search inthe LDAP telephone directory. You can circumvent this problem by making the following config-uration change:

1. Start the Internet Services Manager by selecting Start/Settings/Control Panel/Adminis-trative Tools/Internet Services Manager.

2. Double-click the server where IIS is running.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm


3. Double-click the Default Web Site service.

4. Right-click the ManagerPCM Web site and select Properties from the context menu.



Admin.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM AdministrationApplication-Specific Configuration Changes and System Settings

5. Click Edit... in the Directory Security tab to activate anonymous access and authentica-tion control.




A31003-H2620-A100-1-76A9, 09-2004


Admin.fm


6. Click Edit... under Anonymous access.

7. Change the local, anonymous Internet user account into a user account known within thedomain.Clear the Allow IIS to control password check box so that the password can be storedfor the user entered. You must re-enter the password after you click OK to ensure you didnot make any mistakes.



Trace.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM Trace MonitorGeneral

4 HiPath Manager PCM Trace Monitor

4.1 General

Communication between the various HiPath Manager PCM applications is organized via vari-ous buffer tables and messages. You can follow the progress of each entry in the various buffertables, each instant message exchange, and each program or communication message fromthe components involved, in a separate trace window. In other words, a window is opened foreach component or application involved.

The trace windows can be viewed with the help of the Trace Monitors and transferred to externalstorage for further processing.

Trace messages can be observed for the following HiPath applications:

● HiPath Manager PCM AdministrationAdministration of the configuration parameters for component control by users, for generalsettings, call charge management and evaluation.

● HiPath Manager PCM (Personal Call Manager)

Implementation of call handling and call forwarding by means of definable profiles.

>The interpretation of the contents of the Trace Monitor’s various trace windows is not

explained in the current documentation. This information is interpreted by the ser-vice technician or Siemens for problem analysis when maintenance is required.The following is a description of the necessary steps for navigating and controllingthe Trace Monitor and for exporting the trace contents to a file for further processing.



HiPath Manager PCM Trace Monitor For internal use only

A31003-H2620-A100-1-76A9, 09-2004


Trace.fm

Starting and Ending the Trace Monitor

4.2 Starting and Ending the Trace Monitor

A program group (HiPath Manager PCM) comprising the Administration and Trace tools is cre-ated during HiPath PCM server installation.

1. To start the Trace Monitor, select Start - Programs - HiPath Manager PCM - Trace Mon-itor for HiPath Applications.

The Trace Monitor screen appears:

To close the Trace Monitor, proceed as follows:

1. Select File - Exit

– or press the key combinationh +D

– or select the item Close from the Trace Monitor’s system menu.



Trace.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM Trace MonitorTrace Monitor Screen Layout

4.3 Trace Monitor Screen Layout

An application window with the following layout appears when you start the Trace Monitor:

Title bar

Menu bar

Workspace(open trace win-dow)

Trace Monitor sys-tem menu Minimize

MaximizeClose

Status bar

Trace windowsystem menu




A31003-H2620-A100-1-76A9, 09-2004


Trace.fm

Trace Monitor Screen Layout

The menu titles/commands available are listed in menu bar. The following menu functions areavailable:

Menu Command Function

File Print Setup Configure the printer to output trace messages tothe printer

Exit Close the Trace Monitor.

Trace Use Hexfont Change the output of special trace messagescontaining non-printing characters into a hex font(option activated) or ANSI font (option deactivat-ed). Default messages are always shown in ANSIformat.

Colored Text Change between color (option activated) and

black/white display (option deactivated) for tracemessages.

Add Date/Timestamp If this option is selected, a timestamp is appliedto every new trace message.

Show Window for new Appli-cation

If this option is selected, a separate trace windowappears as soon as an application that writestrace messages is activated.If this option is deactivated, trace window can bemanually opened or closed for active applica-tions by selecting the entry Trace - <name of ap-

plication> , e.g. Trace - WinAccount.Window Cascade Displays trace windows in a cascading arrange-

ment

Tile Vertically Displays trace windows in a vertically tiled ar-rangement

Tile Horizontally Displays trace windows in a horizontally tiled ar-rangement

Arrange Icons Arranges the minimized trace window icons

? About... Displays Trace Monitor program information



Trace.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM Trace MonitorPrint Setup for the Trace Monitor

4.4 Print Setup for the Trace Monitor

The printer must be configured for printing out trace window contents. You can decide whetheryou want to print to the Windows default printer or another installed printer. If you select another

printer, this is defined as the Windows default printer for all other applications on your PC.To configure the printer, proceed as follows:

1. Select File - Print Setup.


2. In the Name field, select the printer to which the Trace Monitor should print. Define the in-dividual printer properties you want including paper and format parameters.

3. Confirm your settings by pressing OK.




A31003-H2620-A100-1-76A9, 09-2004


Trace.fm

General Functions

4.5 General Functions

4.5.1 Opening/Closing a Trace Window

A number of options are available for opening/closing trace windows:

1. Select Show Window for new Application (tick visible in front of the entry) in the Trace menu to automatically open/close trace windows when the relevant application is started/ ended. To deactivate this option, simply select the entry; the tick disappears.

2. If this option is not set, you can open and close the trace windows for the active applicationsmanually. To do this, activate the Trace menu. The available trace windows are the firstentries available. Open trace windows are checkmarked.

– To open a closed window, activate the entry, a tick appears and the trace window is

opened.– To close an open window, select the entry once again, the tick disappears and the

trace window is closed.

4.5.2 Printing the Contents of a Trace Window

You can also print out a screen dump of the current trace window to the Trace Monitor’s config-ured printer for documentation purposes:

1. Activate the system menu or else the context menu (right-click trace window) for the rele-

vant trace window and select the entry Print Messages.2. The current contents of the trace window are sent to the configured printer.

4.5.3 Deleting the Trace Window Contents

To delete the contents of a trace window, proceed as follows:

1. Activate the system menu or else the context menu (right-click trace window) for the rele-vant trace window and select the entry Delete Messages.

2. The contents are deleted, the window is empty.



Trace.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only HiPath Manager PCM Trace MonitorExporting Trace Windows

4.5.4 Freezing the Trace Window Contents

The current trace window display can be frozen to stop messages scrolling. To do this, proceedas follows:

1. Activate the system menu or else the context menu (right-click trace window) for the rele-vant trace window and select the entry Stop Window Scrolling.

The window option is set, the contents are frozen, new trace messages are loaded to thebuffer but not displayed.

2. To deactivate this option, simply select the command Stop Window Scrolling once more.

The option is removed, the last messages are displayed.

4.5.5 Arranging the Trace Window

The Trace Monitor’s active trace windows can be arranged as follows:

● Cascade

– Press< +E

– or activate the command Window - Cascade

● Tile Horizontally

– Press< +F

– or activate the command Window - Tile Horizontally● Tile Vertically

– Press< +D

– or activate the command Window - Tile Vertically

If the trace windows are minimized to icons, these can be arranged across the status line byactivating the command Window - Arrange Icons.

4.6 Exporting Trace Windows

Each trace window can accommodate 1000 (for the server PC under Windows 95/98) or 5000entries (for the server PC under Windows NT or Windows 2000). Once this capacity is reached,the oldest entry in a trace window is deleted for every new entry. To document a trace windowsituation, you can capture the current trace window status in an external file:




A31003-H2620-A100-1-76A9, 09-2004


Trace.fm

Exporting Trace Windows

1. Activate the system menu or else the context menu for the relevant trace window and selectthe entry Write Messages to File.

A message field appears in which the path/file name of the export file for the trace window

is displayed:

2. Confirm the message with OK.

The so-called shell user directory in Windows 2000 is selected by default as the destinationdirectory for export files:

● C:\Documents and settings

\[Windows user]

\My files

\[Application ID]

\[Trace file name]

The naming convention for export files is:

<Application ID><time> .trc

the time is saved in the format YYYYMMDDhhmm .

Example of the file name of an exported trace file:

– Windows user: Mayer

– Application: PCM:

– exported on: 07.11.2002

– at: 14:54:11

C:\Documents and settings

\Administrator

\My documents\\PCM

\PCM20021107145411.trc



Sichern.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only Saving and Restoring Data for HiPath Manager PCM

5 Saving and Restoring Data for HiPath ManagerPCM

Data backup procedure

SQL server data backup cannot be performed during live operation with a File Copy or TapeBackup program because these programs can only be opened via the SQL server. For this rea-son, the SQL server provides a backup function to save data during online operation.

This backup function is guaranteed by the backup jobs that were created during installation.The following databases are backed up by the jobs:

● Master backup at 1:00Main system database of the SQL server

● MSDB backup at 1:30Job administration

● VenusApp backup at 2:00Configuration data from PCM

The backup jobs create a backup media for each individual database in the configured folder(see installation) in three-day cycles. The jobs are executed at the above-mentioned times. Onthe fourth day, the first day’s media is overwritten; on the fifth day, the second day’s media isoverwritten, etc.

> When data is completely restored to the database, all changes and call charge datarecords created since the backup are lost.



Saving and Restoring Data for HiPath Manager PCM For internal use only

A31003-H2620-A100-1-76A9, 09-2004


Sichern.fm

1. Select Start - Programs - HiPath to start the Restore Database program.

The following dialog appears.

2. Select the backup media for the database to be restored in the selection window.

To restore the database from the most up-to-date media, check the backup media dis-played.

The backup date corresponding to the selected media is displayed.

The media is checked for data consistency with Check .3. Click Restore to start the backup process.



Problem.fm

A31003-H2620-A100-1-76A9, 09-2004


For internal use only Troubleshooting

6 Troubleshooting

No. Error description Solution1 Calls cannot be forwarded to an external

destinationThe CO code must be entered under"Destination number identification for ex-ternal calls" in the Server Administrationprogram.

2 Calls cannot be forwarded to groups Only Mulap groups are supported. Whensetting up Mulaps, a virtual station withan acoustic signal must be entered in theregistry value privileges for the Mulap.The extension of the Mulap user must bethe Mulap call number.

3 Modification of the call time for every for-warded call

The letter "P" for pause can be enteredone or more times in the PCM call desti-nation list. The length of the pause is setfor each user individually in myPerson-alWebManager.

4 No trace monitor for the PCM application For test and debugging purposes only:Open DCOMCNFG/ Properties of PCM-Mgr.clsMgr and select Interactive user inthe Identity tab.Please reset in normal operation.

5 Changes are not applied in Server Adminis-tration.

● Restart PCM Service

● Check whether the node is operat-ing (can be activated by means of aping command)



Troubleshooting For internal use only

A31003-H2620-A100-1-76A9, 09-2004


Problem.fm



pcm_shbSIX.fm

A31003-H2620-A100-1-76A9, 09-2004

HiPath Manager PCM V2.0, Administrator Manual Z-1

For internal use only Index

Index Z

AAccess privileges for users 3-8AllServe server PC

Hardware 2-1Assistant I/E 2-2

BBuffer tables 4-1

C

Communication messages 4-1Confirm new password 3-6Currency symbol 3-13

DData protection and data security 1-1Database 3-1Destination number identification 3-29, 6-1Dial plan 3-29Display text 3-21

EEvent Viewer 3-4Exporting a node list 3-14Exporting a user list 3-10Exporting a user list (PCM) 3-28Exporting an extension list 3-17Extension 3-26Extension list, exporting 3-17Extension number entry, creating 3-29Extension number entry, deleting 3-30Extensions 3-15Extensions, editing 3-16Extensions, importing 3-15External connections 3-29External file 4-7

FFeature Provider 2-2Forwarding monitoring 3-21

GGeneral settings 3-1, 3-11

HHiPath 3000 Manager 2-2HiPath 3000 Manager C 2-2HiPath Manager PCM 2-2HiPath Manager PCM (Personal Call Manag-er) 3-18

IImmediate messages 4-1Importing extensions 3-15Importing nodes 3-12

LLogin 3-3

MManagement console 3-1, 3-4Memory capacity, checking 2-6

Mulaps 6-1NNew user, creating 3-5Node 3-12, 3-15, 3-16Node id 3-13Node list, exporting 3-14Nodes, editing 3-12Nodes, importing 3-12

P

Password 3-3, 3-6Pause function 3-20Personal Call Management (PCM) 3-1Program messages 4-1Program, closing 3-3Program, starting 3-3



Index For internal use only

A31003-H2620-A100-1-76A9, 09-2004

Z-2 HiPath Manager PCM V2.0, Administrator Manual

pcm_shbSIX.fm

RRate of exchange 3-14Routing codes 3-29

SSQL database server 2-2System call number 3-14System call number, canonical 3-14

TTelephone directory 3-22Trace monitor 6-1Trace Monitor tool 2-2Trace window 4-1

Trace window contents, deleting 4-6Troubleshooting 6-1Trunks 3-29

UUpdate 2-2, 2-18User - access privileges 3-8User (PCM), editing 3-25User Administration 3-1, 3-5User Administration for PCM 3-25User id 3-3

User list (PCM), exporting 3-28User list, exporting 3-10User, deleting 3-9Users, editing 3-7

WWindows

Application log 2-20availability 2-19Internet Information Server 2-19physical memory 2-19

SMTP service 2-19virtual memory 2-19

Windows default printer 4-5





The information provided in this document contains merely general de-

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

www.siemens.com/hipath