Mitel Deutschland GmbH 68635RFP36U-01 ユーザーズマニュアル
SIP-DECT OM System Manual
270
7.16.2.2 Configuring links to the the central OMM
Each peripheral OMM in the system must connect to the AXI interface of the central OMM for user data
synchronization. If a standby configuration is used for the central system, both OMMs must be
configured in the peripheral OMMs. You configure the connection to the central OMM via the OMP
System -> Data management -> DECT phones synchronization tab (see section 6.5.7.3 for
configuration details).
Before you link a peripheral OMM to the central OMM, you must delete all user and device data, and
CoA profiles from the local OMM. After the connection is established, verify that the user and device
data from the central OMM have been received, then reconfigure the deleted users and devices.
Each peripheral OMM in the system must connect to the AXI interface of the central OMM for user data
synchronization. If a standby configuration is used for the central system, both OMMs must be
configured in the peripheral OMMs. You configure the connection to the central OMM via the OMP
System -> Data management -> DECT phones synchronization tab (see section 6.5.7.3 for
configuration details).
Before you link a peripheral OMM to the central OMM, you must delete all user and device data, and
CoA profiles from the local OMM. After the connection is established, verify that the user and device
data from the central OMM have been received, then reconfigure the deleted users and devices.
Please note:
Concurrent configuration of user and device data may cause conficts. This
can happen if one or more OMMs are not visible due to network issues. If conflicts are
detect for user or devices with the same key Id, those with the most recent timestamp are
kept.
detect for user or devices with the same key Id, those with the most recent timestamp are
kept.
SIP-DECT provisioning mechanisms ensure that there are no conflicts with user data synchronization.
However, the system cannot regulate operations such as "auto-create on subscription". Under rare
circumstances, conflicts can arise with the result that a user action may be ignored. Repeat the action to
ensure it is registered by the system.
However, the system cannot regulate operations such as "auto-create on subscription". Under rare
circumstances, conflicts can arise with the result that a user action may be ignored. Repeat the action to
ensure it is registered by the system.
You must also ensure that the calling party numbers do not conflict with any conference room, FAC
prefix or alarm trigger number across all OMMs in the system.
prefix or alarm trigger number across all OMMs in the system.
Please note:
The user data synchronisation mechanism does not validate conference room,
FAC prefix or alarm trigger numbers. If such numbers conflict with a user's calling number,
synchronisation terminates immediately.
synchronisation terminates immediately.
7.16.2.3 Creating a user account for standby visibility checks
If the active or standby OMM loses connectivity, each OMM checks connectivity to the SIP proxy. By
default, a real SIP user account is used to check the availability of the OMM (via a SIP registration to the
SIP proxy). In a dual homing environment, this may impact the user’s telephony services due to the data
synchronization.
If the active or standby OMM loses connectivity, each OMM checks connectivity to the SIP proxy. By
default, a real SIP user account is used to check the availability of the OMM (via a SIP registration to the
SIP proxy). In a dual homing environment, this may impact the user’s telephony services due to the data
synchronization.
To avoid this issue, you must create a virtual SIP user to be used exclusively for checking OMM
availability (one account for the entire system). See 7.20.7 for more information on this feature.
availability (one account for the entire system). See 7.20.7 for more information on this feature.
7.16.3 USER DATA SYNCHRONIZATION MODES
The user/device synchronization runs on every peripheral OMM with a configured link to the central
OMM. The synchronization function requires an internal AXI connection and an external AXI connection
to the central OMM.
OMM. The synchronization function requires an internal AXI connection and an external AXI connection
to the central OMM.
There are two synchronization modes: system startup or reconnection to resolve conflicts and copy new
or changed datasets, and dynamic synchronization mode.
or changed datasets, and dynamic synchronization mode.
7.16.3.1 Start-up / reconnection mode
In start-up/reconnection mode, the user data synchronization service reconciles the data in the
peripheral OMMs and central OMM. The steps in the user data synchronization mechanism are:
In start-up/reconnection mode, the user data synchronization service reconciles the data in the
peripheral OMMs and central OMM. The steps in the user data synchronization mechanism are: