AASTRA SIP-DECT (Release 3.0)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 164)

SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects
Aastra depl-1624/1.0 Page: 164 (241)
9.5.3.1 DHCP Client
Within the initial boot process the DHCP client supports the following parameters:
•
IP address mandatory
•
Net mask mandatory
•
Gateway mandatory
•
Boot file name mandatory for older RFPs
•
TFTP server mandatory for older RFPs
•
Public option 224: “OpenMobility” / “OpenMobilitySIP-DECT” mandatory
•
VLAN-ID optional
•
TFTP server list optional
9.5.3.1.1 DHCP Request
The DHCP client sends the vendor class identifier (code 60) “OpenMobility3G” (current
RFPs) or “OpenMobility” (older RFPs) and requests the following options in the parameter
request list (code 55):
•
Subnet mask option (code 1)
•
Router option (code 3)
•
VLAN ID option (code 132)
•
TFTP server list (code 150)
•
Public option 224 (code 224) (string “OpenMobility” or “OpenMobilitySIP-DECT”)
•
Public option 225 (code 225) (VLAN ID, not relevant for SIP–DECT)
•
Public option 226 (code 226) (not relevant for SIP–DECT)
9.5.3.1.2 DHCP Offer
The DHCP client selects the DHCP server according to the following rules:
•
The public options (code 224) has a value equal to the string “OpenMobility”,
or
•
the public options (code 224) has a value equal to the string “OpenMobilitySIP-DECT”.
If none of the two rules above match, the DHCP offer is ignored.
Information retrieved from the DHCP offer:
•
The IP address to use is taken from the yiaddr field in the DHCP message.
•
The IP net mask is taken from the subnet mask option (code 1).
•
The default gateway is taken from the router option (code 3).
•
The TFTP server IP address is taken from the siaddr field in the DHCP message and
additionally DHCP option 150, if available.
•
The boot image filename is taken from the file field in the DHCP message, if this field is
empty, the default filename is used.