States of an rfp, Cted to the omm (see chapter 5.6.1), Ve (see chapter 5.6.1) – AASTRA SIP-DECT (Release 2.1)- OM System Manual - Installation, Administration and Maintenance EN User Manual
Page 51: 1 states of an rfp
SIP – DECT OM System Manual Release 2.1
5 OMM Web Service
depl-1230/1.3
Page: 51 (196)
5.6.1
States of an RFP
For each RFP the state of the DECT subsystem is displayed. These states are:
Synchronous
The RFP is up and running. The RFP recognizes and is recognized by other RFPs in its
cluster through its air interface and delivers a synchronous clock signal to the PPs.
Asynchronous
The RFP has not been able to synchronize to its neighbors yet. No DECT communication is
possible. But nevertheless the RFP has already been able to connect to the OMM. This
phase should usually last only for a few seconds after starting up the RFP or the OMM. If this
state lasts longer this is an indication for a hardware or network failure.
Searching
The RFP has lost synchronization to its neighbors. No DECT communication is possible.
This phase should usually last only for a few seconds after starting up the RFP or the OMM.
If this state lasts longer or is re-entered after being in a synchronous state this is an
indication for a bad location of the RFP.
Inactive
The RFP has connected to the OMM but the air interface has not been switched on yet. For
any RFP with activated DECT functionality this phase should last only for a few seconds after
starting up the RFP. If this state lasts longer this may indicate a hardware failure.
Not connected
The RFP was configured but has not connected to the OMM yet. Therefore the IP address
column is empty.