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

SIP–DECT OM System Manual Release 3.0 1 Overview
Aastra depl-1624/1.0 Page: 12 (241)
1.2.2 RFP only Mode
Within this mode the RFP converts IP protocol to DECT protocol and then transmits the
traffic to and from the handsets over a DECT time slot. On air the RFP has 12 available time
slots, 8 can have associated DSP/media resources for media streams. All DECT time slots
are used for control signaling, software download over air, messaging and bearer handover
independent of associated DSP/media resources.
2 control signaling channels are also used to carry bearer signals that signal the handset to
start the handover process. If the radio signal of another RFP is stronger than that of the
current RFP, then the handset starts the handover process to the RFP that has the stronger
signal as the user moves around the site.
Clusters
Groups of RFPs can be built which are named clusters. Within a cluster RFPs are
synchronized to enable a seamless handover when an user crosses from one RFP’s area of
coverage to another. For synchronization it is not necessary for an RFP to see directly all
other RFPs in the system. Each RFP only needs to be able to see the next RFP in the chain.
But it is preferable for an RFP to see more than one RFP to guarantee synchronization in the
event that one of the RFPs fails.
1.2.3 OpenMobility Manager (OMM) Mode
If the OMM shall not run on a dedicated Linux x86 server then one RFP within a SIP–DECT
installation must be declared to operate as the OpenMobility Manager (OMM). The RFP
acting as the OMM may also act as a regular RFP as well if it is included into a DECT
cluster.
In OMM mode an RFP functions as a regular RFP. Additionally it is responsible for SIP
signaling between the SIP–DECT system and the IP PBX/media server. Further on it takes
over the management part of the SIP–DECT solution. You designate an RFP as the OMM by
assigning an IP address to the RFP within the DHCP scope (see chapter 9.5) or by setting
the data via the OM Configurator (see 9.6). After an RFP is designated as the OMM, it starts
the extra services on board (for example, the web service that supports the management
interface). All RFPs download the same firmware, but only one RFP activates the OMM
services.
Note: It is possible to deactivate the DECT part of an RFP. If the DECT interface is
deactivated then all resources (CPU and memory) are available for the OMM.
1.3 About the OpenMobility Manager
With SIP–DECT 3.0 the OpenMobility Manager (OMM) requires to run on one of the new
RFP types (RFP (L) 35/36/37 IP resp. RFP (L) 43 WLAN) or on a dedicated Linux x86
server.