Mitel Deutschland GmbH 68635RFP36U-01 사용자 설명서
Configuration and Administration
241
RFP configuration data is loaded from the file and added to the OM Configurator database via the
Load
RFP config option. You must initiate the Send Configuration operation after executing the Load RFP
config operation for the configuration to take effect on the select RFPs.
Please note:
The data sequence has been changed from previous releases of the SIP-
DECT OM Configurator. Import of files based on the old data sequence format may result
in import errors or the incorrect assignment of parameter values.
in import errors or the incorrect assignment of parameter values.
7.7.10 REMOVING RFP ENTRIES
You can remove all RFP data records from the OM Configurator database through the
Clear List option
in the OM Configurator task.
You can remove one or more RFP records from the OM Configurator database by selecting one or more
entries in the table and clicking on the
entries in the table and clicking on the
Remove selected RFP option.
Ensure that you do not remove data records before configuration is sent to the RFP device (via the
Send
Configuration operation). Changes made to RFP configuration data but not sent to RFP device are lost
on the remove operation.
on the remove operation.
You can add RFP configuration data again through the operations described above.
7.7.11 COMPATIBILITY WITH OLDER SIP-DECT RELEASES
It is not recommended to use the SIP-DECT 6.1 OM Configurator for configuration of RFPs with software
from an earlier SIP-DECT release.
from an earlier SIP-DECT release.
Configured parameters of an RFP which are unknown to actual OM Configurator are shown in the “Other
parameter” panel with the name used at the protocol level. In most cases, this name will be different from
the display name known from previous versions of OM Configurator.
parameter” panel with the name used at the protocol level. In most cases, this name will be different from
the display name known from previous versions of OM Configurator.
You can edit or remove such parameters and new values will be transferred to the RFP when you
execute the
execute the
Send configuration operation.
7.8 OMM CONFIGURATION AND RESOURCE FILES
The OMM supports certain configuration files containing commands in AXI style, to support auto-
configuration of small and simple installations in provider environments. It is assumed that the
configuration files are automatically generated in a standardized way, to prevent configuration failures.
configuration of small and simple installations in provider environments. It is assumed that the
configuration files are automatically generated in a standardized way, to prevent configuration failures.
The following list summarizes all of the configuration and resource files related to the provisioning of a
SIP-DECT system:
SIP-DECT system:
•
ipdect.cfg / <MAC>.cfg / <PARK>.cfg
These files contain configuration parameters and are used to configure the OMM automatically. There
is one common file “ipdect.cfg” for all RFPs and one file “<MAC>.cfg” for every single IP-RFP. The
RFP specific <MAC>.cfg is requested if indicated in the common “ipdect.cfg” file. It is possible that all
RFPs request “ipdect.cfg” and only selected RFPs request the <MAC>.cfg (for specific configuration
on some RFPs).
is one common file “ipdect.cfg” for all RFPs and one file “<MAC>.cfg” for every single IP-RFP. The
RFP specific <MAC>.cfg is requested if indicated in the common “ipdect.cfg” file. It is possible that all
RFPs request “ipdect.cfg” and only selected RFPs request the <MAC>.cfg (for specific configuration
on some RFPs).
•
usr_common.cfg / <user>.cfg