 |
|
|
|
12.1.8 |
HiPath User Management |
| HiPath User Management will be implemented in Small Remote Site scenarios in HiPath 3000/5000 V5.0 and later. These are networks in which HiPath 4000 functions as a central system. HiPath 3000 systems are used in smaller branch locations (Small Remote Sites, SRS). |
| IP stations can be "relocated" from one branch (HiPath 3000) to another (HiPath 3000) or from the central office (HiPath 4000) to a branch (HiPath 3000) and vice versa via HiPath User Management. |
Small Remote Site Concept |
| In normal mode, all IP workpoint clients (system clients) are registered with the central system HiPath 4000. In an emergency (failure of the central HiPath 4000 system or the CorNet IP network), the IP workpoint clients in the branch react and automatically register with their branch HiPath 3000 via the SRS concept. These workpoint clients are then available to users with all features of HiPath 3000. |
| The IP workpoint clients (system clients) reregister with the central HiPath 4000 system when normal mode is resumed. |
| The Small Remote Site concept requires that the branch systems and central system are connected with each other via an IP network. System clients (IP workpoint clients) such as OpenStage CorNet-IP (HFA) or OpenScape Personal Edition are supported. |
| For further information on the Small Remote Site concept, refer to the HiPath 3000/5000 V8 Feature Description. |
HiPath 3000 Element Manager |
| The link between HiPath User Management and the HiPath 3000 systems involved is the HiPath 3000 Element Manager. For the central HiPath 4000 system, access is accomplished via Element Manager in HiPath 4000 Manager. |
| Element Manager allows the central administration of a Small Remote Site scenario via HiPath User Management. |
| After installing HiPath 3000 Element Manager, configure the HiPath 3000 systems to be administered via HiPath User Management. You can do this via the HiPath 3000 Element Manager web-based configuration interface. You can add or remove individual systems in the node configuration menu. Once you have added a system (node), any information on its configured IP workpoint clients (system clients) is retrieved immediately via SNMP. |
| The basic configuration of HiPath 3000 for an SRS scenario is carried out via HiPath 3000/5000 Manager E (Settings menu: Set up station (emergency mode)). User Management recognizes the configured system clients and identifies them internally as HiPath 3000 SRS telephones. |
| The next procedure depends on customer specifications: |
| • | The IP workpoint clients in the Small Remote Sites (branches) should use the same call numbers in normal mode (registered with HiPath 4000) and in emergency mode (registered with HiPath 3000). |
| In this case, the call numbers are assigned via HiPath User Management. When configuring the IP workpoint clients (system clients) via HiPath 3000/5000 Manager E their call numbers should be deleted. Otherwise it is not possible to assign call numbers via HiPath User Management without taking further steps. |
| • | The IP workpoint clients in the Small Remote Sites (branches) should use different call numbers in normal mode (registered with HiPath 4000) and in emergency mode (registered with HiPath 3000). |
| In this case, the call numbers are assigned via HiPath 3000/5000 Manager E when configuring the IP workpoint clients (system clients). An IP workpoint client configured in this way can then be assigned a HiPath 4000 call number for normal mode via HiPath User Management. |
| The following configuration data for an IP workpoint client is modified via HiPath User Management: |
| • | Internal call number |
| • | DID number |
| • | Directory name |
| • | CFSS destination |
| • | Access groups |
|
| HiPath 3000/5000 V8, Service Documentation, Issue 10 | up  |
|
|
||
| Disclaimer & Copyright | ID: P31003H3580S100017620 | 2011-01-24 |