User's Manual

OpenMobility SIP Installation, Administration and Maintenance
Aastra DeTeWe Doc-ID: pm-0504 28.11.2006 Page: 35 (52)
Restoring a previously saved configuration will lead to a reset of the OMM to
take effect.
3.3.4 RFP configuration
All configured RFPs are listed in tables grouped to clusters by its topographic
relations. The RFPs are sorted by their Ethernet 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 placing the RFPs
so close to each other, that every RFP recognizes at least one other RFP
through its radio interface.
There are conditions where this is not possible, for instance with RFPs at
remote locations. In this case the RFPs shall be grouped to 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.
When the RFPs are connecting the OMM they submit their HW type. This
type is displayed on the RFP list web page.
New RFPs can be added to the system by pressing the “New” button. A
popup window appears providing the configuration of a new RFP.
Each RFP is identified by its MAC address (6 bytes hex format, colon
separated). The Ethernet address is unique and can be found on the back of
the chassis.
For easier administration each RFP can be associated with a location string.
The location string can hold up to 20 characters.
The same popup window could be opened for an existing RFP by pressing
the tool icon of the appropriate RFP.
An RFP could be deleted by pressing the trash can icon . A similar popup
window asks for confirmation showing the current configuration of this RFP.