Mitel Deutschland GmbH 68635RFP36U-01 Manuale Utente

Configuration and Administration

245

- When the OMM receives a SIP Notify message with the “

check-sync” event for a user, the OMM

reloads the configuration file <user>.cfg for that user.

- When the OMM receives a SIP Notify message with the “

prov-sync” or ”resync” event for any

user, the OMM reloads all configuration and resource files. The SIP Notify with ”prov-sync” or
”resync” can be also addressed to the OMM (without the user portion in the request URI).

7.8.4 AXI COMMANDS IN CONFIGURATION FILES

With SIP-DECT 6.0 or later, the OMM supports configuration files containing commands in AXI style, for
OMM configuration.

The OMM attempts to load the following files from the Configuration File URL, and processes them in
this order:
1  ipdect.cfg
2  <MAC>.cfg (RFP OMM only)
3  <PARK>.cfg (PARK in MAC address format: e.g. PARK: 1F11234001; MAC address format

001F11234001)

Note that the actual file name of the <MAC>.cfg depends on MAC address of the RFP where the OMM is
running.

The active OMM and the standby OMM request different files, even if they belong to one system. To
ensure that both OMMs can retrieve the same file independent of which one is active, each OMM
requests the <PARK>.cfg. The PARK identifies a SIP-DECT system in a unique way.

None of the files are mandatory and they can be empty. The AXI commands can be all in one file or split
up as needed.

Example configuration file
The following example shows how to include AXI commands in a configuration file.

### SIP-DECT OMM Config example – pls. be aware that some commands cannot be applied to
SIP-DECT with Cloud-ID e.g. request PARK from server, set regulatory domain etc. and some
commands depend on the actual use case/setup

### Confirm EULA

### Set full access account

### Set root account

### Set system name

### Tone scheme

### OMP web start #####

### Enable SSH ###