AudioCodes Mediant 1000 User Manual page 192

Problem Possible Cause
BootP did not reply to
the Mediant 1000
TFTP server down
ini file was
not loaded
TFTP server didn't
get the request
Mediant 1000 didn't
request the file from
your TFTP
TFTP server bug
BootP sent to a board
with the wrong TFTP
server address
ini file does not exists
in the default
directory of the TFTP
server
Wrong ini file name
TFTP server's
timeout is too short
ini file is not in the
Wrong ini
correct position
file loaded
ini file corrupted
Other BootP servers
BootP reply
contain the MAC
from wrong
address of the
BootP
board/module
server
User's Manual
Table 9-1: Solutions to Possible Common Problems
Solutions
Check the validity of the IP address, subnet and default
gateway.
If the default gateway is not used, enter 0.0.0.0
Check if the BootP server replied to the Mediant 1000 at
restart by viewing the log of the BootP server.
Try to restart the BootP server.
Check the MAC address of the board/module in the
BootP server.
Check if the TFTP server is working.
Check the log of the TFTP server.
Check that the TFTP server's IP address is the one that
the Mediant 1000 is trying to use by viewing the Syslog.
Try to restart the TFTP server.
Check the IP address of the TFTP server being used.
Check the default directory of the TFTP server and
check that the ini file exists there.
Verify in Windows Explorer that file extensions are
displayed and the ini file is not XXX.ini.ini by mistake.
Also verify that the extension ini is in lowercase letters.
Verify that the TFTP server settings are as follows:
Timeout = 2 sec,
# of retransmission = 10
An old ini file was probably loaded. Check which ini file
was loaded by using the Syslog server. The Gateway
displays contents of ini file before it began.
Check the ini file syntax
Check that only your BootP server contains the Mediant
1000 MAC address.
192
Digital Mediant 1000
Document # LTRT-66401