AudioCodes MediaPack MP-114, User Manual

Page: 21 / 164

User's Manual 4. Device Initialization & Configuration Files
Version 6.6 21 MediaPack Series
4.3 Using BootP/DHCP
Notes:
•
This sub-section is not applicable to Mediant 3000 HA.
•
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 BootPDelay ini file parameter. Also,
the default number of requests is 3 and can be changed by the
BootPRetries ini file parameter. Both parameters can also be set using the
Command Line Switches in the BootP reply packet.
•
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 below.
The device uses the Bootstrap Protocol (BootP) and the Dynamic Host Configuration
Protocol (DHCP) to obtain its networking parameters and configuration automatically after
it is reset. BootP and DHCP are also used to provide the IP address of a TFTP server on
the network, and files (cmp and ini) to be loaded into memory.
Both DHCP and BootP are network protocols that enable a device to discover its assigned
IP address; DHCP differs from BootP in that it provides a time-limited "lease" to the
assigned address. Both protocols have been extended to enable the configuration of
additional parameters specific to the device.
While BootP is always available, DHCP has to be specifically enabled in the device
configuration, before it can be used.
A BootP/DHCP request is issued after a power reset or after a device exception.
Note:
BootP is normally used to initially configure the device. Thereafter, BootP is no
longer required as all parameters can be stored in the gateway’s non-volatile memory
and used when BootP is inaccessible. For example, BootP can be used again to change
the private (local) IP address of the device.
4.3.1 BootP/DHCP Server Parameters
BootP/DHCP can be used to provision the following parameters (included in the
BootP/DHCP reply. Note that some parameters are optional):

IP address, subnet mask - These mandatory parameters are sent to the device every
time a BootP/DHCP process occurs. Note that in High Availability (HA) mode, this IP
address is only private (local) and is not the HA System (global) IP address that must
be configured separately through the Interface Table.

Default gateway IP address - An optional parameter that is sent to the device only if
configured in the BootP/DHCP server.