10.3.1 |
Plug&Play Startup of IP Workpoints |
Procedure |
| 1. | When you connect an IP workpoint, it receives both it's own IP address as well as that of the DLI by contacting the DHCP server implemented on the HiPath Xpressions Compact board. |
| 2. | The IP workpoint registers with the Deployment service (DLI) within HiPath Xpressions Compact. |
| 3. | The Deployment Service checks whether it is necessary to configure the default values for the IP workpoint (for example, if this is the first startup). |
| Note: For IP workpoint configuration, a template in XML format is defined for each IP workpoint type and stored in the HiPath Xpressions Compact file system. There is exactly one template per supported IP workpoint type, regardless of the software version. The first time that an IP workpoint is started, the Deployment Service checks whether there is a suitable template for this type. If a template exists, the IP workpoint is supported and the configuration data from the template and the plug&play data (such as, the gatekeeper address) are supplied to the IP workpoint. If this is an IP workpoint type for which no template is available, a general template is provided. |
| Each additional logon with the Deployment service results in a plug&play-only configuration (supply of gatekeeping address, etc.). In this way, the attributes assigned by template and changed locally on the IP workpoint are not overwritten by the Deployment service with each new logon. |
| 4. | The Deployment Service sends configuration data from the matching template together with the plug&play data to the IP workpoint. |
| 5. | The IP workpoint logs on to the gateway and is operational. |
| Plug&play configuration of SIP-based workpoints is not possible. |
| HiPath 3000/5000 V9, Service Documentation, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3590S100017620 | 2014-02-27 |