14.3.4 |
Behavior of the Branch-Office IP Workpoint Clients in Emergency Mode |
| The following applies for the IP workpoint clients registered in an emergency with HiPath 3000 via SRS: |
| • | The features of HiPath 3000 are available. |
| • | The HiPath 3000 user interface is implemented in emergency mode. |
| • | This also applies to the key layout of the IP workpoint clients. |
| • | The IP workpoint clients have a preconfigured database in the HiPath 3000 system for emergency mode. |
| • | The functionality described is implemented in the standard system software. |
| • | No HiPath 3000 feature is restricted or blocked. |
| • | The system configuration must facilitate emergency mode. This means that stations, LCR, COS, etc., also require administration in this regard. |
| • | In emergency mode, the display of the IP workpoint client shows a corresponding message. The display of the message can be administered via HiPath 3000 Manager E. |
| • | In the HiPath 3000 system, preconfigured station numbers must be used for outgoing calls. This also applies to preconfigured COS entries. |
| • | The LCR feature must be administered in HiPath 3000 in such a way that internal calls within the private network are handled via TDM lines. |
| • | In emergency mode, calls can also be directed via preconfigured alternative LCR routes (e.g. for the operator). |
| • | Calls can also be traced in emergency mode. |
| • | There are no specific security requirements with regard to H.235 that deviate from the conditions generally valid for HiPath 3000 (HG 1500) and IP workpoint access. |
| HiPath 3000/5000 V9, Feature Description, Issue 7 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3590F100017618 | 2012-06-25 |