AASTRA SIP-DECT (Release 3.0)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 161)

SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects
Aastra depl-1624/1.0 Page: 161 (241)
•
A TFTP server is no longer required for boot of an RFP (L) 35/36/37 IP or
RFP (L) 43 WLAN.
•
TFTP, FTP(S), HTTP(S) are supported for RFP (L) 35/36/37 IP or RFP (L) 43WLAN
software update.
9.5 SIP–DECT Startup
This chapter contains detailed information on the startup (booting) process of the SIP–DECT
solution.
For booting an RFP (L) 32/34 or RFP (L) 42 WLAN, there must be at least one TFTP server
on the attached network to load the OMM/RFP application software.
RFP (L) 35/36/37 IP or RFP (L) 43 WLAN uses the internal flash to start the boot image. A
fileserver is only needed for software update over the network, please see chapter 9.11.5.
The essential network settings can be alternatively:
•
Communicated by a DHCP server at startup time.
•
Configured on the RFP with the OM Configurator tool (see chapter 9.6). The settings
made by the OM Configurator will be saved permanently in the internal flash memory of
each OMM/RFP.
9.5.1 TFTP and DHCP Server Requirements
TFTP server requirements
The RFP gets the boot image file from a TFTP server. The requirement list for the used
TFTP server is defined as follows:
•
The support of RFC 1350 /1/ is mandatory.
•
To accelerate the download of a boot image file for older RFPs, it is possible to increase
the packet size of the transmitted TFTP packets from 512 bytes per packet to 1468 bytes
per packet. To use this optional feature, the TFTP server has to support RFC 2347 /3/ and
RFC 2348 /4/.
•
To reduce the overall download time of the older RFPs in a system, it is possible to use
TFTP multicast download. To use this optional feature, the TFTP server has to support
RFC 2090 /2/ and RFC 2349 /5/.
Note: Current RFPs operating the SIP–DECT 3.0 software do not support packets larger
than 512 bytes and also no multicast with TFTP.
To use the TFTP multicast option, the attached network has to support multicast too.
Furthermore a support of IGMP, RFC 2236 /6/ is required.
Note: If many RFPs loading the boot image simultaneously, the network load could
increase significant. To balance the network load or for backup reasons, it is
possible to configure more than one TFTP server in a network.
DHCP server requirements
A DHCP server needs to support RFC 2131 /9/. The TFTP and DHCP server need not to
reside on the same host.