Mitel Deutschland GmbH 68635RFP36U-01 ユーザーズマニュアル
Configuration and Administration
251
7.9 RFP CONFIGURATION FILES
IP-RFPs support two RFP configuration files (downloaded from a server) to get configuration settings.
There is one common file “ipdect.cfg” for all RFPs and one file specific file “<MAC>.cfg” for every IP-
RFP. The RFP requests the “ipdect.cfg” file if a URL is provided. The RFP specific <MAC>.cfg is
requested if this is indicated in the common “ipdect.cfg” file. It is possible that all RFPs request
“ipdect.cfg” and only selected RFPs request the <MAC>.cfg to obtain a specific configuration on some
RFPs.
There is one common file “ipdect.cfg” for all RFPs and one file specific file “<MAC>.cfg” for every IP-
RFP. The RFP requests the “ipdect.cfg” file if a URL is provided. The RFP specific <MAC>.cfg is
requested if this is indicated in the common “ipdect.cfg” file. It is possible that all RFPs request
“ipdect.cfg” and only selected RFPs request the <MAC>.cfg to obtain a specific configuration on some
RFPs.
7.9.1 STANDARD IP SETTINGS
Standard IP settings (which are necessary for access to the RFP configuration files) are configured via
DHCP (see section 7.5) or OM Configurator (see section 7.6). These are:
DHCP (see section 7.5) or OM Configurator (see section 7.6). These are:
•
IP address
•
Net mask
•
Gateway (i.e. router)
•
Boot file name
•
TFTP server
•
Public option 224: “OpenMobility” or “OpenMobilitySIP-DECT” (to identify the relevant DHCP offer)
•
Domain Name Server
(optional)
•
Domain Name
(optional)
•
URL to the RFP configuration files
All other parameters can be set by using an RFP configuration file even if standard DHCP options or OM
Configurator parameters exist.
Configurator parameters exist.
7.9.2 CONFIGURATION FILE SOURCE
A TFTP / FTP(S) / HTTP(S) URL specifies the protocol, server and path to access the RFP configuration
files. The URL can include account data if appropriate.
files. The URL can include account data if appropriate.
Syntax:
{ftp|ftps|http|https}://[user:password@]server/[directory/]
or
tftp://server/[directory/]
The URL configuration is done via DHCP option code 223 (prio1) or DHCP option code 66, or the OM
Configurator.
Configurator.
•
“ipdect.cfg” is mandatory if an URL is given by DHCP option code 66 or local static configuration via
the OM Configurator.
•
“<MAC>.cfg” is mandatory if it is indicated in the “ipdect.cfg” that a “<MAC>.cfg” exists for the RFP.
(There is a key word to indicate that a “<MAC>.cfg” exists for every RFP.)
Mandatory means that if a file cannot be loaded, the RFP will not start. This is relevant for the following
scenarios:
scenarios:
•
RFP boot / startup (after power on, software update, etc)
•
a change of the URL