SIP User's Manual
46
Document #: LTRT-65409
MediaPack
Series
4.2 Startup
Process
The startup process (illustrated in the following figure) begins when the gateway is reset
(physically, using the Embedded Web Server, or using SNMP) and ends when the
operational software is running. In the startup process, the network parameters, and
software and configuration files are obtained.
After the gateway powers up or after it's physically reset, it broadcasts a BootRequest
message to the network. If it receives a reply (from a BootP server), it changes its network
parameters (IP address, subnet mask and default gateway address) to the values
provided. If there is no reply from a BootP server and if DHCP is enabled (DHCPEnable =
1), the gateway initiates a standard DHCP procedure to configure its network parameters.
After changing the network parameters, the gateway attempts to load the
cmp
and various
configuration files from the TFTP server’s IP address, received from the BootP/DHCP
servers. If a TFTP server’s IP address isn’t received, the gateway attempts to load the
software (
cmp
) file and / or configuration files from a preconfigured TFTP server (refer to
'Automatic Update Mechanism' on page
231
). Thus, the gateway can obtain its network
parameters from BootP or DHCP servers, and its software and configuration files from a
different TFTP server (preconfigured in the i
ni
file).
If BootP/DHCP servers are not located or when the gateway is reset using the Embedded
Web Server or SNMP, it retains its network parameters and attempts to load the software
(
cmp
) file and / or configuration files from a preconfigured TFTP server. If a preconfigured
TFTP server doesn’t exist, the gateway operates using the existing software and
configuration files loaded on its non-volatile memory.
Note that after the operational software runs and if DHCP is configured, the gateway
attempts to renew its lease with the DHCP server.
Notes:
•
Though DHCP and BootP servers are very similar in operation, the
DHCP server includes some differences that could prevent its operation
with BootP clients. However, many DHCP servers such as Windows
™
NT
DHCP server are backward-compatible with BootP protocol and can be
used for gateway configuration.
•
By default, the duration between BootP/DHCP requests is one second
(configured by the BootPDelay
ini
file parameter). The number of
requests is three by default (configured by the BootPRetries
ini
file
parameter). Both parameters can also be set using the BootP command
line switches.
Summary of Contents for Mediapack mp-11x
Page 1: ...Document LTRT 65409 August 2007 User s Manual Version 5 2...
Page 2: ......
Page 14: ...SIP User s Manual 14 Document LTRT 65409 MediaPack Series Reader s Notes...
Page 18: ...SIP User s Manual 18 Document LTRT 65409 MediaPack Series Reader s Notes...
Page 22: ...SIP User s Manual 22 Document LTRT 65409 MediaPack Series Reader s Notes...
Page 44: ...SIP User s Manual 44 Document LTRT 65409 MediaPack Series Reader s Notes...
Page 47: ...Version 5 2 47 August 2007 SIP User s Manual 4 Getting Started Figure 4 1 Startup Process...
Page 322: ...SIP User s Manual 322 Document LTRT 65409 MediaPack Series Reader s Notes...
Page 380: ...SIP User s Manual 380 Document LTRT 65409 MediaPack Series Reader s Notes...
Page 388: ...SIP User s Manual 388 Document LTRT 65409 MediaPack Series Reader s Notes...
Page 390: ...User s Manual Version 5 2 www audiocodes com...