8 rfp configuration files, Onfiguration, Iles – AASTRA SIP-DECT (Release 3.0)- OM System Manual - Installation, Administration and Maintenance EN User Manual
Page 181

SIP–DECT OM System Manual Release 3.0
9 Configuration und Administration Aspects
Aastra
depl-1624/1.0
Page: 181 (241)
9.8
RFP Configuration Files
Configuration files
IP-RFPs support two RFP configuration files which are downloaded from a server to get
configuration settings. There is one common file “ipdect.cfg” for all RFPs and there is one file
specific file “
URL is given. The RFP specific
“ipdect.cfg” file. It is possible that all RFPs request “ipdect.cfg” and only selected RFPs
request the
Standard IP settings
Standard IP settings which are necessary to have access to the RFP configuration files are
configured via DHCP (see chapter 9.5) or OM Configurator (see chapter 9.6). These are:
•
IP address
•
Net mask
•
•
Boot file name
•
TFTP server
•
Public option 224: “OpenMobility” or “OpenMobilitySIP-DECT”
(to identify the relevant DH
•
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.
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.
Syntax:
{ftp|ftps|http|https}://[user:password@]server/[directory/]
or
tftp://server/[directory/]
The URL configuration is done via DHCP option code 66 or the OM Configurator.
•
“ipdect.cfg” is mandatory if an URL is given by DHCP option code 66 or local static
configuration via the OM Configurator.
•
“
Mandatory means: if a file can not be loaded then the RFP will not start. This is relevant for
the following scenarios:
•
RFP boo
,
•
a change of the URL.