|
|
|
| Host-client configuration (master-slave configuration)
|
|
| You can only initiate the relocate feature on optiPoint 500 or OpenStage TDM host (master) telephones in the idle state.
|
| The data from any client (slave) stations that may be connected will also be exchanged if a client (slave) is preconfigured for each port. In addition, the client (slave) must be active on the port where the procedure is being carried out.
|
| The affected client (slave) telephones are reset during the execution of the exchange, just as the hosts (master) are.
|
| In cases where, for example, a client (slave) is not active for only one of the telephone ports (for example, the adapter has been removed), only the host (master) telephone is relocated.
|
|
|
|
| Only optiPoint 500 and OpenStage TDM telephones are supported.
|
|
| Client (slave) telephones
|
|
| Client (slave) telephones can be UP0/E stations (optiPoint phone adapter), analog stations (optiPoint analog adapter) and S0 stations (optiPoint ISDN adapter, only the default station of the associated port is considered here).
|
|
|
|
| S0 telephones do not use the Relocate feature These telephones operate automatically on any port, i.e. they do not require the Relocate feature.
|
| In the case of S0 telephones with LIN, the LIN must be manually updated via the HiPath 3000/5000 Manager E when changing the telephone port.
|
|
| E911 emergency service for USA
|
|
| For V3.0 SMR-7 and later, the Relocate feature guarantees that the LIN remains assigned to the physical telephone port.
|
|
|
|
| It is not possible to execute the feature on telephones that have programming authorization.
|
|
|
|
| You cannot execute the feature over DISA/DISA internal.
|
|
|
|
| If the user confirms the feature with associated services (default: *83<DID>#9419) the call does not follow the call management for non-physical ports.
|
| It is not possible to activate the feature via associated services.
|
|
| Physically not available stations
|
|
| For incoming calls to stations, which are no longer physically available, the call follows the call management (CFW to PM instead dropping the call to the intercept). This mechanism is available 1 minute after proceeding with this feature or 5 minutes after a system hard restart.
|
|
| Display status information
|
|
| If a relocate session was successful the user will see relevant status information on the display of his or her optiPoint 500 or OpenStage TDM. Higher prior display texts like "View Messages" cover up the status indication.
|
|
|
|
| Access to this feature can be set up on a key of an optiPoint 500 or OpenStage TDM station. The LED of this key will be never used.
|
|
|
|
| Hoteling is possible with code lock active. To delete the status indication, during code lock active, is possible.
|
|
|
|
| Activation of the feature is only possible if the station is idle.
|
|
| First two SLMO or SLU hardware ports
|
|
| The feature cannot be accessed on the first two SLMO or SLU hardware ports.
|
|
| OpenScape Personal Edition
|
|
| The feature is not available in the OpenScape Personal Edition.
|
|
|
|
| You cannot execute the feature with any IP device.
|
|
|
|
| It is not possible to activate the feature via associated services.
|
|
|
|
| The feature cannot be executed if a UCD agent is logged on to a participating host (master) telephone.
|
|
|
|
| When the relocate feature is performed, the participating telephones will go out of service and restart. Activated features will be handled accordingly. That means that all callback calls and sent messages will be deleted, all other features remain unaffected.
|
|