After VLANTEST expires, if the phone receives a non-zero L2QVLAN value, the phone
releases the IP address and sends DHCPDISCOVER on that VLAN. Any other release
requires you to perform a manual reset before the phone attempts to use a VLAN on which
VLANTEST has expired.
The phone ignores any VLAN ID administered on the call server if a non-zero VLAN ID is
administered either by LLDP, manually, through DHCP, or through the settings file.
Related links
About DNS addressing
IP deskphones support DNS addresses, dotted decimal addresses, and colon-hex addresses. The
phone attempts to resolve a non-ASCII-encoded dotted decimal IP address by checking the
contents of DHCP Option 6. At least one address in Option 6 must be a valid, non-zero, dotted
decimal address. Otherwise DNS fails. The text string for the DOMAIN system parameter, Option
15 is appended to the addresses in Option 6 before the phone attempts DNS address resolution. If
Option 6 contains a list of DNS addresses, those addresses are queried in the order given if no
response is received from previous addresses on the list. As an alternative to administering DNS
by DHCP, you can specify the DNS server and or the domain name in the HTTP script file. But first
SET the DNSSRVR and DOMAIN values so that you can use those names later in the script.
Note:
Administer Options 6 and 15 with DNS servers and domain names respectively.
EAP-TLS support for authentication
You can use the EAP-TLS as the mode of authentication. To activate this mode, you must add a
new parameter DOT1XEAPS, with valid values of
MD5
or
TLS
to the settings file. The default value
is
MD5
. The call server supports EAP-TLS as specified in RFC 2716 if and only if an identity
certificate is present in the deskphone and if the value of DOT1XEAPS is
TLS
. If an EAP method
requires the authentication of a digital certificate, and if you have enabled the Supplicant on the
phone and the value of
DOT1XEAPS
changes, the Supplicant will transmit an EAPOL-Logoff
message and return to the CONNECTING state.
Related links
Activating EAP-TLS for authentication
Scenarios for using EAP-TLS based authentication
on page 136
Deploying EAP-TLS based authentication for phones using 802.1x and MD5
on page 137
Deploying EAP-TLS on phones running without any type of 802.1x authentication
on page 138
Administering your phone
May 2018
Installing and Administering Avaya J169/J179 IP Phone H.323
134