Using Bootp/Dhcp - AudioCodes Mediant 1000 User Manual

User's Manual
Note 1:
Note 2:
Note 3:
Note 4:
6.3

Using BootP/DHCP

The Mediant 1000 uses BootP (Bootstrap protocol) and DHCP to configure the Mediant
1000's initial parameters. BootP/DHCP enables network administrators to manage the
basic configuration of the Mediant 1000 from a central server.
RFC 951, RFC 1542, and RFC 2132 (IETF Requests for Comment) describe BootP in
detail. The protocol has been extended to enable BootP/DHCP to configure additional
parameters specific to the Mediant 1000.
As the flow chart in the figure above illustrates, a BootP/DHCP request is issued after a
power reset, a device exception, or when calling acResetRemoteBoard() API (assuming
that the Mediant 1000 was not reset by an acOpenBoard() API).
Note:
Version 4.6
The BootP/DHCP server should be defined with an ini file name when you
need to modify configuration parameters or when you're working with a large
Voice Prompt file that is not stored in non-volatile memory and must be
loaded after every reset.
The default time duration between BootP/DHCP requests is set to 1 second.
This can be changed by the ini file parameter BootPDelay. Also, the default
number of requests is 3 and can be changed by the ini file parameter
BootPRetries, (both parameters can also be set using the Command Line
Switches in the BootP/TFTP Server).
The ini file configuration parameters are stored in non-volatile memory after
the file is loaded. When a parameter is missing from the ini file, a default
value is assigned to this parameter and stored in non-volatile memory
(thereby overriding any previous value set for that parameter). Refer to
''Using BootP/DHCP'' on page
on page 197.
By default, the configuration files are stored in non-volatile memory. Use the
ini file parameter, 'SaveConfiguration=0', to refrain from storing the
configuration files in the non-volatile memory after loading.
BootP is normally used to configure the initial parameters of the Mediant
1000. Thereafter, BootP is no longer required as all parameters can be
stored in the Mediant 1000's non-volatile memory and used when BootP is
inaccessible. BootP is required again (for example) to change the IP
address of the Mediant 1000.
6. Mediant 1000 Initialization & Configuration Files
53 and the Appendix, ''BootP/TFTP Server''
53 August 2005