Page
19
01/2007
AMT/PTD/PBX/0062/1/2EN
RFP ONLY MODE
In this mode, the RFP converts the data to be transmitted from IP format to DECT format (or vice-
versa).
Exchanges between the RFP and the PP take place on the air interface via the 12 available
DECT time slots:
♦
♦
♦
♦
8 for voice call in the real sense of it
4 for signalling
In a cluster, RFPs are synchronized to enable a seamless handover when a user moves from
one coverage area to another.
For synchronization, it is not necessary for an RFP to communicate directly with all other RFPs in
the system.
Each RFP only needs to be able to communicate with 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.
The 4 control signalling channels are also used to carry handover start signals. If the radio signal
of another RFP is stronger than that of the current RFP, then the handset starts the handover
process with the RFP that has the stronger signal as the user moves around the site.
OPENMOBILITY MANAGER MODE:
In this mode, the RFP functions as a regular RFP and manages the IP DECT service.
An IP address must be defined for this RFP.
This RFP thus declared on the DHCP server enables you to start the management web interface
of the IP DECT service.
3.8.2 RFP
SYNCHRONIZATION
The RFPs are synchronized over the air interface.
For the RFP to synchronize with another RFP, the signal strength should not drop below
–70 dBm.
To avoid communication failure, the radio signal received by the PP must not fall below – 60
dBm.
3.8.3 RFP
INSTALLATIONS
The following rules must be observed:
Horizontally, the RFPs must be located 2.50 m away from each other, and 0.25 m
vertically.
The RFPs must be fixed at a height of 1.80 m to 2.30 m, with a ceiling height of 0.50 m.
To guarantee a handover if a caller moves from one RFP coverage area to another, an accurate
synchronization of the RFPs is necessary.
