Mitel Deutschland GmbH 68635RFP36U-01 Manuale Utente
Enhanced Feature Overview
35
3.15.4 USER DATA SYNCHRONIZATION (MIVOICE 5000 DUAL HOMING SUPPORT)
SIP-DECT 6.1 introduces support for MiVoice 5000 dual homing, to ensure that SIP-DECT telephony
services survive if the network connection to the OMM goes down. Dual homing is achieved through
user data synchronization across all OMMs in the system. Every peripheral OMM propagates changes in
user, device, Configuration over Air (CoA) profiles or SARI configuration to a central OMM. Every OMM
in the installation (including the central OMM) can use a standby OMM. AXI is used to distribute
configuration changes between the central and peripheral OMMs.
services survive if the network connection to the OMM goes down. Dual homing is achieved through
user data synchronization across all OMMs in the system. Every peripheral OMM propagates changes in
user, device, Configuration over Air (CoA) profiles or SARI configuration to a central OMM. Every OMM
in the installation (including the central OMM) can use a standby OMM. AXI is used to distribute
configuration changes between the central and peripheral OMMs.
For more information on this feature, see section 7.16.
3.16 DECT BASE STATION SYNCHRONIZATION
To ensure a seamless communication experience, the SIP-DECT system switches an ongoing DECT
phone call from one DECT base station to another if the radio communication quality drops below a
certain threshold. The seamless handover is possible only if the participating DECT base stations are
synchronized. DECT base station synchronization is performed via radio communication between DECT
base stations, which in turn requires a decent radio coverage planning (see section 7.2).
phone call from one DECT base station to another if the radio communication quality drops below a
certain threshold. The seamless handover is possible only if the participating DECT base stations are
synchronized. DECT base station synchronization is performed via radio communication between DECT
base stations, which in turn requires a decent radio coverage planning (see section 7.2).
3.16.1 CLUSTERING AND PAGING AREAS
Your SIP-DECT system may include different locations, where the distances between the locations
prevent the RFPs from performing the over-the-air synchronization. In this case, you must split your
network into clusters (or “synchronization domains”). You assign DECT base stations to cluster numbers
for this purpose (see section 5.6.3 “DECT settings” or section 6.7.1.2, “DECT tab”). Note that overlap
between different clusters on one campus or site must be avoided.
prevent the RFPs from performing the over-the-air synchronization. In this case, you must split your
network into clusters (or “synchronization domains”). You assign DECT base stations to cluster numbers
for this purpose (see section 5.6.3 “DECT settings” or section 6.7.1.2, “DECT tab”). Note that overlap
between different clusters on one campus or site must be avoided.
If your SIP-DECT system consists of a very large number of DECT base stations, you should configure
the paging area size to optimize the signaling necessary for paging a DECT phone in throughout the
SIP-DECT system (see 6.7.2).
the paging area size to optimize the signaling necessary for paging a DECT phone in throughout the
SIP-DECT system (see 6.7.2).
A separate cluster number is also required for a remote site (e.g., for a single DECT base station
servicing an office abroad). Also, if the VPN network connection to the isolated site’s DECT base station
cannot transport DHCP, you may use static IP address configuration for the single DECT base station
(see section 7.6).
servicing an office abroad). Also, if the VPN network connection to the isolated site’s DECT base station
cannot transport DHCP, you may use static IP address configuration for the single DECT base station
(see section 7.6).
3.17 WIRELESS LAN (WLAN)
If you have a number of WLAN RFPs (RFP 42 WLAN or RFP 43 WLAN), the SIP-DECT system also
provides access to your company LAN via Wireless LAN. The RFP 43 WLAN also supports 802.11n.
The WLAN configuration of a group of WLAN RFPs is managed by WLAN profiles (see section 5.8).
provides access to your company LAN via Wireless LAN. The RFP 43 WLAN also supports 802.11n.
The WLAN configuration of a group of WLAN RFPs is managed by WLAN profiles (see section 5.8).
3.17.1 802.11I: WPA2-ENTERPRISE PRE-AUTHENTICATION FOR FAST ROAMING
WLAN stations (e.g. laptop) which decide to roam to another WLAN access point (AP) must perform the
full authentication process with the new AP. In 802.1X (RADIUS) networks this can take a long time
resulting in network dropouts during the roam.
full authentication process with the new AP. In 802.1X (RADIUS) networks this can take a long time
resulting in network dropouts during the roam.
The AP share authentication information with other APs, so the station can authenticate faster (pre-auth)
when roaming to a new AP. This method reduces network dropouts significantly.
when roaming to a new AP. This method reduces network dropouts significantly.