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

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 141 (196)
• 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.
• “.cfg” is mandatory if it is indicated in the “ipdect.cfg” that a “.cfg” exists for
the RFP. (There is a key word to indicated that a “.cfg” exists for every RFP.)‏
Mandatory means: if a file can not be loaded then the RFP will not start. This is relevant for
the following scenarios:
• RFP boot / startup (after power on, SW update, …)‏,
• a change of the URL.
Parameter settings priority
Some parameters can be set via DHCP / OM Configurator or by using the files “ipdect.cfg” or
“.cfg”. If a parameter is provided by more than one of the possible ways, the last
setting has priority. There is the following order:
• DHCP / OM Configurator
• ipdect.cfg
• .cfg
It is also possible to remove settings.
Times when RFP configuration times are read
The configuration files are read by the RFP application e.g. during startup as shown by the
following figure.