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

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 140 (196)
Use the Run configs button to start the iterative configuration of multiple RFPs using the
prepared and loaded configuration file. The LEDs will display whether the configuration has
succeeded or failed. See the log file content for further information. If the configuration has
failed for an RFP, the configuration could be repeated using the update button beside the
LEDs.
Note: Note that the login and proxy data will be used for the whole configuration file!
7.7 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 “.cfg” for every single IP-RFP. The RFP requests the “ipdect.cfg” file if an
URL is given. The RFP specific .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 .cfg to have a specific configuration on some RFPs.
Standard IP settings
Standard IP settings which are necessary to have access to the RFP configuration files are
configured via DHCP (see chapter 7.5) or OM Configurator (see chapter 7.6). These are:
• IP address
• Net mask
• Gateway (i.e. router)‏
• Boot file name
• TFTP server
• Public option 224: “OpenMobility” (to identify the relevant DHCP offer)‏