Troubleshooting
PN: 1725-36038-001-H.doc
129
Message
Description
Action
Erasing Memory
Handset has determined that a
download should occur and is erasing
the current software from memory.
None. When the progress bar fills the
display line the erase operation is
complete.
Do not turn the handset off during this
operation.
Files Too Big
Handset software download files are
incorrect or corrupted.
Download new software from the
Polycom website per
Software
Maintenance
.
Flash Config Error Handset internal configuration is
corrupt.
Perform "Restore Defaults" operation
via administrator menus (or re-program
with Configuration Cradle).
Initializing …
The handset is performing power-on
initialization.
None. This is informational only.
Initializing SIP
The handset is performing a power-on
initialization of the SIP application.
The phone is initializing its data
structures and attempting to access
the SIP TFTP server and download the
SIP configuration files.
None. This is informational only.
Internal Err. # #
The handset has detected a fault from
which it cannot recover.
Record the error code so it can be
reported.
Turn the handset off then on again.
If error persists, try registering a
different handset to this telephone port.
If error still persists, contact Polycom
Technical Support and report the error.
Invalid Usr/Pwd
When WPA2-Enterprise or Cisco FSR
is selected, the handset failed to
connect due to incorrect device
credentials or unavailability of
authentication server. If the error is
because of the incorrect device
credentials then the username or
password doesn’t match with those
configured on the authentication
server.
Verify that the required credentials
{username, password} are created on
the authentication server and should
match the handset. This may also
happen when the authentication server
is not reachable while doing the EAP
authentication. Make sure the
authentication server is active and
reachable from the WLAN access
points/controller at all times.
Multiple GW Res
More than one SpectraLink 8000 SVP
Server has responded.
Caused by two or more handsets
sharing the same IP address. Assign
unique IP addresses to each handset.
Multiple SVP Reg
yyy.yyy.yyy.yyy
y…y = SVP IP address
Handset received responses from
multiple SVP Servers; displays IP
address of one responding SVP
Server.
This can happen if the handset has
been reconfigured to use a different
SVP server and then powered on
before the previous server has had time
to determine that the handset is no
longer connected to it. The problem
should go away after about 30 seconds.