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

SIP–DECT OM System Manual Release 3.0 7 OMM Web Service
Aastra depl-1624/1.0 Page: 66 (241)
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.
SW Update available
The RFP is connected to the OMM. On the TFTP server has found a new software. The RFP
is waiting that the OMM initiates a reboot. In the meantime is the RFP full operational.
7.6.2 OMM / RFP SW Version Check
When the RFPs are connecting the OMM they submit their SW version. If this version differs
from the OMM SW version and the versions are incompatible the RFP connection attempt is
rejected. This could happen when using several TFTP servers with different OpenMobility
SW versions. In this case the RFP is marked with an error message. Moreover a global error
message is displayed on the RFP list web page if at least one version mismatch has been
found.