use the Craft ADDR procedure and enter the correct HTTP and or HTTPS File Server IP
address in the File Server field.
3. An alternative protocol known as LLDP can also supply call server, and file server with
HTTP and HTTPS IP addresses. This IETF standard protocol requires the network to be
equipped and configured to support LLDP. You can provide HTTP and the HTTPS Server
and call server IP addresses with LLDP in the network using proprietary Transport Layer
Values (TLVs) to pass information to the phones.
LLDP setup and troubleshooting steps
Note:
If system value
STATIC
is set to 0 which is the default setting, the DHCP or the 46xxsettings
file might overwrite the static addresses.
Proposed solution for DHCP configured deskphones
Procedure
1. Using the Craft
ADDR
procedure, set
Phone
to
0.0.0.0
.
2. Verify or set
SSON
to
242
which is the default value.
3. Administer the DHCP server option 242 to include
MCIPADD=
xxx.xxx.xxx.xxx
where
xxx.xxx.xxx.xxx
is the call server IP address.
4. Verify that the DHCP server and the deskphone are on the same VLAN.
5. Verify the
DHCP server
port 67 and or the
DHCP client
port 68 are not blocked on the
switch.
6. Verify the configuration of the DHCP Relay Agent on the switch or on a separate PC, for
example, MS Windows Server 2000/2003 whether the deskphones and DHCP Server are
placed on different networks or subnets. DHCP broadcast messages do not, by default,
cross the router interface.
Proposed solution for script-configured deskphones
Procedure
1. Edit the 46xxsettings.txt file to contain a valid Call Server IP address with the line
SET
MCIPADD
xxx.xxx.xxx.xxx
where
xxx.xxx.xxx.xxx
is the Call Server IP address.
2. Verify that the 96xxupgrade.txt file contains the line
GET 46xxsettings.txt
as the last
command line of the upgrade file.
LLDP setup and troubleshooting steps
May 2018
Installing and Administering Avaya J169/J179 IP Phone H.323
197