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

SIP – DECT OM System Manual Release 2.1 3 Enhanced Feature Overview
depl-1230/1.3 Page: 21 (196)
3 Enhanced Feature Overview
An SIP – DECT system scale from a single licensed RFP up to a larger SIP – DECT system
that may include hundreds of RFPs. Some of the more advanced features target larger
DECT systems. You may browse the following list of features in order to get an overview and
to decide if it’s relevant for your requirements. You find in-depth explanations in the
referenced chapters.
Download over Air
The Aastra 610d / 620d / 630d devices are able to download and upgrade their firmware via
DECT. The firmware file that has to be provided by a TFTP server is automatically distributed
to all subscribed DECT portable parts by the OMM (see chapter 7.15).
OMM standby
The OMM is the central management entity in a SIP – DECT system and forms thereby
single point of failure. It is possible to automatically transfer the OMM function to a second
RFP device in case of failure or loss of network connection (see chapter 7.11).
DECT XQ
The DECT radio communication generally suffers from attenuation and radio wave reflection.
Especially if a building’s walls and ceilings contain a higher portion of metal-based material
or if larger metal surfaces are present, the DECT XQ improves the radio communication
between an RFP and an Aastra 610d/620d/630d portable parts at the expense of DECT
channel capacity (see 7.3). Enable this feature for some or all of your RFPs (see chapter
5.6.3, “DECT settings” or chapter 6.7.1.2, “DECT tab”).
RFP synchronization / radio coverage planning
To ensure a seamless communication experience, the SIP – DECT system switches an
ongoing DECT phone call from one RFP to another if the radio communication quality drops
below a certain threshold. The seamless handover is possible only if the participating RFPs
are synchronized. RFP synchronization is performed via radio communication between
RFPs, which in turn requires a decent radio coverage planning (see chapter 7.2).
Clustering / 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 need to split your network into clusters (or “synchronization domains”). Assign RFPs to
cluster numbers for this (see chapter 5.6.3, “DECT settings” or chapter 6.7.1.2, “DECT tab”).
If your SIP – DECT system consists of a very large number of RFPs, you should configure
the paging area size to optimize the signaling necessary for paging a DECT portable part in
throughout the SIP – DECT system (see 6.7.2).
Isolated sites
A separate cluster number is also required, e.g. for a single RFP servicing an office abroad.
Also, if the VPN network connection to the isolated site’s RFP cannot transport DHCP, you
may use static IP address configuration for the single RFP (see chapter 7.6).