TDK 3300 ICP - Manual (Page 37)

SpectraLink Corporation Setup and Administration—NetLink e340/i640 Wireless Telephone
Mitel Networks 3300 ICP and 5220 IP Phone emulation
PN: 72-1084-02-B.doc Page 37
Message Description Action
CRC Code Error The software which has been TFTP
downloaded has a bad redundancy
code check. Try the download again, it is
possible the software was
corrupted during download. If the
error repeats, check that the
download image on the TFTP
server is not corrupted.
Code Mismatch! The software loaded into the
Wireless Telephone is incorrect for
this model phone. Replace the software image on the
TFTP server with software that is
correct for the phone model.
DHCP Error (1-4) DHCP Error 1 The Wireless Telephone cannot
locate a DHCP server. It will try
every 4 seconds until a server is
located.
DHCP Error 2 The Wireless Telephone has not
received a response from the
server for a request to an IP
Address. It will retry until a server
is found.
DHCP Error 3 The server refuses to lease the
Wireless Telephone an IP
Address. It will keep trying.
DHCP Error 4 The server offered the Wireless
Telephone a lease that is too short.
The minimum lease time is 10
minutes but SpectraLink engineers
recommend at least one hour
minimum lease time. The Wireless
Telephone will stop trying.
Reconfigure the server and power
cycle the Wireless Telephone.
DHCP Lease Exp The Wireless Telephone’s DHCP
lease has expired, and the call (if
any) cannot continue. The Wireless Telephone failed to
renew its DHCP lease, either
because the DHCP server is not
running, or because the
configuration has been changed by
the administrator. The Wireless
Telephone will attempt to negotiate
a new lease, which will either work,
or change to one of the above
DHCP errors (1-4).
DHCP NACK error A NACK (Negative ACKnowledge)
was received from the DHCP server. The DHCP lease currently in use
by the Wireless Telephone is no
longer valid, which forces the
Wireless Telephone to restart. This
problem should resolve itself on
the restart. If it does not, the
problem is in the DHCP server.