Mitel Deutschland GmbH 68635RFP36U-01 Manuel D’Utilisation
Configuration and Administration
223
7.4 NETWORK INFRASTRUCTURE PREREQUISITES
To establish and maintain an SIP-DECT installation, a network infrastructure is assumed, which
comprises at least the following components:
comprises at least the following components:
•
RFPs
•
DECT phones
•
IP PBX/media server (e.g. Asterisk)
•
TFTP server
Depending on the operational modes the following services should be provided:
•
DHCP
•
TFTP
•
SNTP
•
DNS
•
LDAP
•
Syslog daemon
Notes on network infrastructure prerequisites
•
In NA outdoor RFPs may only be installed with the antennas shipped with the units. No other
antennas or cabling are permitted. In EMEA the outdoor RFPs are shipped without antennas and you
may use the units with one of the optional antennas (separate order no.).
may use the units with one of the optional antennas (separate order no.).
•
A TFTP server is no longer required for boot of an RFP 35/36/37 IP or RFP 43 WLAN.
•
TFTP, FTP(S), HTTP(S), SFTP are supported for RFP 35/36/37 IP or RFP 43 WLAN software
update.
7.5 SIP-DECT STARTUP
This section contains detailed information on the startup (booting) process of the SIP-DECT solution.
For booting an RFP 32/34 or RFP 42 WLAN, there must be at least one TFTP server on the attached
network to load the OMM/RFP application software.
network to load the OMM/RFP application software.
RFP 35/36/37 IP or RFP 43 WLAN uses the internal flash to start the boot image. A fileserver is only
needed for software update over the network.
needed for software update over the network.
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 section 7.6). The settings made by the OM
Configurator will be saved permanently in the internal flash memory of each OMM/RFP.
7.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 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 2
nd
generation RFPs, it is possible to