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

SIP–DECT OM System Manual Release 3.0 3 Enhanced Feature Overview
Aastra depl-1624/1.0 Page: 27 (241)
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.
Please note: Be aware that the majority of the new enhanced features require at least the
following handset firmware releases
– 600d: firmware release 4.00
– 650c: firmware release 1.00
It is assumed that SIP–DECT installations are configured to perform an
automatic firmware update over the air.
Download over Air
The Aastra 600d handset family and the Aastra 650c handset are able to download and
upgrade its firmware via DECT over the air.
For the OMM running on an RFP the handset firmware packages are delivered in the
package file “aafon6xxd.dnld” for the Aastra 600d handset family and the Aastra 650c
handset. This package file must be put on the same server and path where the RFP gets a
software image file for update purposes (e.g. iprfp3G.dnld).
The handset firmware packages are included in the OMM installation package for Red Hat©
Linux for the Linux x86 server version of the OMM (e.g. SIP-DECT_3.0.bin).
Wideband (CAT-iq 1.0 / Aastra Hi-Q™ audio technology)
Together with the new RFP (L)35/36/37 IP and RFP (L) 43 WLAN, the Aastra 650c offers the
possibility to act as Aastra Hi-Q audio terminal. This feature is realized using wideband
speech according to CAT-iq.
Each Hi-Q connection uses, compared to conventional narrowband, the double capacity on
the DECT air interface. Due to this fact, 4 Hi-Q connections (instead of 8) can be established
via one RFP.
Aastra Hi-Q audio technology must be enabled or disabled per site (see chapters 7.5 and
8.6). This functionality must be homogeneously available among synchronous RFPs
(members of the same cluster). Each site with enabled Hi-Q audio must exclusively contain
new RFP (L)35/36/37 IP or RFP (L) 43 WLAN.
Typically one site is identical with one cluster, i.e. all RFPs belonging to a specific site
belonging to a specific cluster. However a site can have more than one cluster. The OMM
does not refuse to configure one cluster which contains multiple sites. Such configuration
could annul the rule that Hi-Q audio must be homogeneously available among synchronous
RFPs.
Please note: It is strongly recommended not to setup systems with multiple sites within one
cluster.