Two dect air interfaces, Managing account data for system access, 12 m – AASTRA SIP-DECT (Release 2.1)- OM System Manual - Installation, Administration and Maintenance EN User Manual
Page 153: Anaging, Ccount, Ata for, Ystem, Ccess, 3 two dect air interfaces, 12 managing account data for system access
SIP – DECT OM System Manual Release 2.1
7 Configuration und Administration Aspects
depl-1230/1.3
Page: 153 (196)
In any case, when both OMMs get in contact again with each other, the longer running one
becomes the active one and that will overwrite the database file in the standby OMM.
Configurations made in this becoming standby OMM would be lost!
7.11.4.3 Two DECT Air Interfaces
In case of both OMMs are in an unsynchronized and active state they are fully working.
RFPs which lose connection to the OMM because of the network break down might connect
to the other OMM. Two DECT air interfaces will be present but are working parallel.
Note: Both air interfaces are using the same PARK. So it can not determined to which
OMM a location registration succeeds.
For PPs different situations are possible:
•
They do not notice this situation:
- active calls stay established, depending on network conditions;
- PPs can make and receive new calls, depending on an available PBX connection;
- PPs can do handover to RFPs connected to the same OMM;
- PPs can call PPs that are registered to the other OMM
•
They lose their RFP base station and perform a new location registration:
- active calls are broken;
- PPs can make and receive new calls, depending on an available PBX connection;
- PPs can do handover to RFPs connected to the same OMM;
- PPs can call PPs that are registered to the other OMM;
•
They lose their RFP base station and search the DECT network without finding another
one:
- active calls are broken;
- PPs stay in searching for network until an air interface is available again.
Note: Handover between PPs located to RFPs which are controlled by different OMMs is
not possible.
When the OMMs get in contact again with each other this inconsistent OpenMobility system
situation will end.
7.12
Managing Account Data for System Access
Each RFP provides different independent access types:
•
the OMM Web service/HTTPS interface (see chapter 5);
•
the OMP (see chapter 6);
The OMM Web service and the OMP are mainly used for configuration and administration.
•
the OM Configurator (see chapter 7.6);
The OM Configurator is mainly used for static local configuration of an RFP.
•
the ssh user shell (see chapter 8.3.5).
The ssh user shell is mainly used from experts for diagnosis.
Each of this these access types uses the same account data.