Filter
Top Products
285
Advanced Troubleshooting and Repair
TFTP load failure Option 128 is not set up
to point to the right
TFTP server
(Controller).
Check the DHCP server, and confirm that
option 128 is pointing to the right TFTP
server (usually the SX-200 ICP system IP
address).
No network connectivity
between the controller
and the phone.
Confirm that the controller is connected to
the network.
For a Cisco L2 switch: verify that the L2
switch is access port (Voice LAN).
For an HP L2 switch: verify that the L2
switch is untagged (Voice LAN).
If the router is involved, make sure that
router’s MTU is set to 600 or more.
Firmware on controller
is missing or corrupted.
Verify that the firmware is in the sysro/tftp
directory (particularly if the user has
manually copied the firmware).
Confirm if TFTP on the controller is
corrupted (this can be verified by
connecting the IP Phone directly on the
controller, or by observing the behavior of
other IP Phones).
Tips: If you have Option 132/133
programmed on the controller’s internal
DHCP server, disable them before trying
Step 2.
Waiting for link Option 129 is not
programmed correctly.
Check Option 129 on DHCP to confirm that
the IP address of the SX-200 ICP
controller is correctly programmed.
The Layer 2 switch port
may be running
spanning tree.
Turn port fast on or disable Spanning tree
(whichever is possible).
The application server
is broadcasting or
multicasting on IP
Phone port or on PC
behind the IP Phone.
Turn off multicasting.
The PC behind the IP
Phone is changing
speed 100/10.
Depending on the NIC, you may need to
hardcode to 100 MB instead of auto
negotiation.
Table 58: IP Phone Registration Troubleshooting (continued)
Error Message on
Display
Probable Cause Corrective Action
(Page 4 of 5)