14.4  
Requirements for HiPath 3000 from V5.0 
 
No phones or clients should be operate on a HiPath 3000 in a small remote site scenario in normal operation which is installed in a branch as the communications system.  
Although there are no restrictions in relation to the configuration, the station should be configured in such a way only features for emergency operation are possible because the configuration of features such as ACD, hunt group, MULAP etc lead to inconsistent behavior even if the stations are connected at the same physical location.  
Generally, HiPath 3000 does not prevent users or administrators from configuring features for emergency mode.  
HiPath 3000 V5.0 and later support alternative registration of HiPath 4000 IP workpoint clients, in the event that the HiPath 4000 IP workpoint clients lose their "connection" to HiPath 4000. If a HiPath 4000 is detected by an IP workpoint client as unavailable in the network, the IP workpoint client registers with a remote HiPath 3000 that operates as a local gateway in a branch office.
As soon as the HiPath 4000 IP workpoint client detects that the HiPath 4000 is available again, it reregisters automatically with the HiPath 4000 as its central system. The IP work client also reregisters automatically when a service engineer performs a manual reset.

The following emergency mode scenarios may occur in a branch office:  
 •   The IP connection of a HiPath 4000 workpoint client (connected in the branch office) to the central system is lost: emergency mode is activated.
 •   HiPath 4000 is down: emergency mode is activated for the configured IP workpoint clients.
 •   HiPath 3000 is down: emergency mode is not activated.
 •   An optional HiPath Management Server is down: emergency mode is not activated.
 •   An optional HiPath 5000 Server is down: emergency mode is not activated.
 •   The TDM backup cannot be accessed: emergency mode is not activated.
 •   A HiPath 5000 is not supported as a branch office system.
 •   Cascading errors (e.g. an "emergency" HiPath error) are not taken into account.
 •   The selection of a suitable HiPath 3000 should be supported by HiPath Management, however this is optional.
 •   The switchover to a branch office system and the automatic switchover back to the central system is implemented by the IP workpoint clients.

HiPath 3000/5000 V9, Feature Description, Issue 10   up Top
Disclaimer & Copyright   ID: P31003H3590F100017618   2014-02-27