14.1  
Feature explanation 
 

HiPath 4000 as a central office, HiPath 3000 as a branch  
This concept is based on scenarios where HiPath 4000 operates as a central system. HiPath 3000 systems are implemented in smaller branch offices (Small Remote Sites, SRS).
From V5.0 or later, HiPath 3000 can be connected to HiPath 4000 (from V2) as a survivable node when the "Small Remote Site" feature is used. This functionality ensures cost-effective failure tolerance of IP workpoints.
In normal mode the IP workpoint clients are registered with the HiPath 4000 system. Calls that arrive via a HiPath 3000 trunk connection are transferred via the IP network to HiPath 4000 system and forwarded to the correct station.
From HiPath 3000 V8 and HiPath 4000 V5 only the SIP-Q V2 protocol is used to IP network these two systems and the CorNet-NQ protocol is used for TDM networking. The CorNet-IP protocol is no longer supported.  

Normal and emergency mode  
The IP workpoint clients that are registered during normal mode with the central HiPath 4000 react in the event of system failure, and register themselves automatically and independently with the HiPath 3000 system via the SRS concept. These workpoint clients are then available to the user together with all HiPath 3000 features.
The IP workpoint clients required in this case are configured via Manager E.

Systems, telephones and clients  
The Small Remote Site concept is supported by:
 •   HiPath 3000 V5 to V7
 •   HiPath 4000 V2 to V4
 •   optiPoint 410 economy, standard and advanced
 •   optiPoint 420 economy, standard, and advanced
 •   OpenScape Personal Edition
 •   OpenStage CorNet-IP (HFA)
optiPoint 410 and 420 entry with no display are approved. The user does not see on the display that the system has changed.  

HiPath 3000/5000 V9, Feature Description, Issue 7   up Top
Disclaimer & Copyright   ID: P31003H3590F100017618   2012-06-25