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

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 155 (196)
7.12.2 Potential Pitfalls
When an RFP is configured via the OM Configurator and is taken out of an installation, the
RFP may become unusable:
• When this RFP comes up, it finds a valid configuration in its permanent memory. It will
hence skip DHCP for booting.
• But when this configuration is not valid anymore (e.g. the TFTP server has a new IP
address meanwhile), the RFP isn't able to complete the boot and is hence not able to
connect to the OMM.
• The RFP will not get newer passwords from the OMM.
It is therefore recommended to switch of the OM Configurator before taking an RFP out of an
installation. But nevertheless the OM Configurator allows to reset the permanent memory of
an RFP (the Aastra support must be connected).
7.13 WLAN Configuration (RFP 42 / L42 only)
7.13.1 WLAN configuration steps
The correct configuration of an RFP with a WLAN interface requires the correct configuration
of the DECT part. The second step is to specify the regulatory domain of the WLAN network
at the
System settings page of the OMM web service (see chapter 5.4.1).
Regulatory Domain Country
0x10: FCC USA, Australia
0x20: IC Canada
0x30: ETSI Europe (excluding Spain, France)
0x31: SPAIN Spain
0x32: FRANCE France
0x40: MKK Japan
0x41: MKK1 Japan (MKK1)
This setting depends on the country and is prescribed by the laws of that country. Only the
setting prescribed for that country must be used.
The third step is to specify the WLAN parameters in a profile (see chapter 5.8.1). The WLAN
profile determines the name (SSID) of the WLAN network and other parameters. The
encryption and authentication procedures are especially important and must be planned
carefully beforehand.