AASTRA SIP-DECT (Release 1.8)-Installation- and Administration Guide EN - Manual (Page 48)

Installation, Administration and Maintenance
Aastra depl-0900/0.4 Page: 48 (104)
The OMM writes the database into a file on the external server with following
name convention:
<yymmdd>_<system_name>_<PARK>_omm_conf.gz
WARNING: For an automatic database export is a time synchronisation with
a NTP server mandatory. For NTP server configuration see chapter 3.1.4 and
chapter 3.2.
3.3.3 RFP configuration
All configured RFPs’ are listed in tables grouped to clusters by its
topographic relations. The RFPs’ are sorted by their Ethernet (MAC)
addresses.
To ensure correct handover of a PP during a call, all involved RFPs’ must
deliver the same clock signal to the PP. This is achieved by having the RFPs’
synchronized. The synchronization is achieved by placing the RFPs’ so close
to each other, that every RFP recognizes at least one other RFP through its
air interface.
There are conditions where synchronization is not possible, for instance with
RFPs’ at remote locations. In this case the RFPs’ shall be grouped in
different clusters. The OpenMobility Manager will not try to synchronize
RFPs’ over cluster borders.
All used clusters are displayed in the navigation bar on the left side and the
OMM RFP is marked with a bold font.