
Proposed solution for DHCP– configured deskphones
Procedure
1. Using the local 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. For more details about
configuration of a DHCP Relay Agent on Windows Server 2003, see
http://technet2.microsoft.com/WindowsServer/en/library/929704d8-0e1c-4b8d-
b424-16c312ad1edf1033.mspx
Note:
Do not embed spaces in DHCP Option 242 strings. For more information, see
DHCP Server Administration
in Chapter 5 of the
Administering Avaya IP
Deskphone H.323 9608, 9611G, 9621G, and 9641G
.
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.
3. Verify that the deskphone can reach the HTTP server and whether the HTTP server
is activated.
4. Verify that the 96xxupgrade.txt and 46xxsettings.txt files are placed in the proper
directory of the HTTP server to access these files.
Troubleshooting
88 Installing and Maintaining Avaya IP Deskphone H.323 9608, 9611G, 9621G, and 9641G
August 2013