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

SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects
Aastra depl-1624/1.0 Page: 159 (241)
Sometimes RFPs do not need to be synchronized, e.g. if they are in different buildings.
These RFPs can be put into different clusters. RFPs in different clusters will not be
synchronized with each other. Different clusters start up at the same time independently.
9.2.1 Initial Synchronization Procedure
To avoid synchronization problems and to speed up the synchronization on system startup,
an initial synchronization procedure will be used. For every cluster the following
synchronization stages are defined.
•
Synchronization stage 0
- If at least one preferred RFP was configured, the synchronization process will wait up to
30 seconds for an incoming startup message of such a preferred RFP. Receiving a
message will finishing stage 0 and the synchronization process jumps to stage 1.
- If no message was received within the 30 seconds this stage will be terminated and the
next stage will be started.
- If no preferred RFP was configured, this stage will be ignored.
•
Synchronization stage 1
- If a preferred RFP was determined in stage 0, this one will be the synchronization
source for the next upcoming RFPs. Otherwise the first RFP which sends a startup
message will be the synchronization source for the next upcoming RFPs.
- In this stage only RFPs reporting an RSSI value better than -65 dBm will be permitted
to do a synchronization.
- If an RFP has done its synchronization, this RFP will be also a synchronization source
for other upcoming RFPs.
- The initial timeout for this stage is 30 seconds. Whenever an RFP has finished its
synchronization in this stage a new stage timeout value will be calculated.
- If no RFP comes up within the timeout time or if all the upcoming RFPs do not fit the
RSSI threshold, this stage will be terminated and the next stage will be started.
•
Synchronization stage 2
- The behavior of this stage is identical to stage 1, but an RSSI threshold value of
-70 dBm is significant.
•
Synchronization stage 3
- The behavior of this stage is identical to stage 1, but an RSSI threshold value of
-75 dBm is significant.
•
Synchronization finished
- No more RSSI threshold value is significant. All the RFPs which failed the stage
conditions above, are now permitted to do a synchronization.
The last level “synchronization finished” will be achieved either all registered RFPs of this
cluster are synchronized or the timer of stage 3 expires.
9.2.2 Checking the Synchronization of a Network
For every cluster a periodically check of the synchronization of the network is done. If the
network is split into at least two subnets, all the RFPs of the lesser subnet(s) will be
resynchronized. While doing initial synchronization procedure this check is deactivated. You