Code Parameter
10 L2QVLAN
11 PHY1STAT
12 PHY2STAT
13 PROCSTAT
14 SIG
15 SIP_CONTROLLER_LIST
Extending use of DHCP lease
9600 Series IP Deskphones support configuration of network parameters using DHCP as per RFC
2131. However, when a DHCP server becomes unreachable and the DHCP lease currently held
by the phone expires, the phone continues to use the same lease until the DHCP server becomes
reachable. This functionality is controlled by setting the following parameter:
Parameter name Default value Description
DHCPSTD 0 Specifies if the expired DHCP lease is used.
Value operation:
• 0: Continue use of the expired DHCP lease if
the lease could not be renewed.
• 1: Stop using the DHCP lease immediately
when it expires, as per the standard.
The parameter is configured through the
46xxsettings.txt file.
When this feature is enabled (DHCPSTD=1), the phone continues to use the lease data, including
IP address, router and other options if the lease could not be renewed. In this state, the phone will
attempt to reach a DHCP server every 60 seconds. When a DHCP server becomes available and
a lease is renewed or new lease obtained, the phone performs a duplicate address detection on
the offered IP address. If no conflicts are detected, this IP address is assigned to the local network
interface for use.
Parameter configuration through DHCP
The phones support the DHCP configuration option called Site Specific Option (SSON). Using this
option, custom parameters can be configured on the phone through a DHCP server. In DHCP
DISCOVER, the phone requests for the SSON, typically configured in DHCP Option 242. To
respond to this request, configure the DHCP server with proper data supplied in the offer for this
option value. The following is an example of such configuration:
option avaya-option-242 L2Q=1,L2QVLAN=1212,httpsrvr=192.168.0.100
The following parameters can be configured with this feature:
Configuration through DHCP
January 2020 Installing and Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP
Deskphones SIP 29
Comments on this document? infodev@avaya.com
To Next Page
Loading...
