Mitel Deutschland GmbH 68635RFP36U-01 Manuale Utente
Configuration and Administration
273
•
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 Mitel
support must be connected).
But nevertheless the OM Configurator allows to reset the permanent memory of an RFP (the Mitel
support must be connected).
7.18 WLAN CONFIGURATION (RFP 42 WLAN / RFP 43 WLAN ONLY)
7.18.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
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 section 5.4.1.3).
WARNING:
Please note that selecting the incorrect regulatory domain may result in a violation
of applicable law in your country!
Select one of the two-letter country codes. 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.
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 section 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.
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.
The access point can be assigned to a VLAN that conforms to 802.1q. All the data that is received from
and that is to be forwarded to the WLAN clients is then carried by the configured VLAN. All other data,
such as VoIP packets, configuration data or authentication data (Radius), is given the VLAN tag
configured for the RFP. The switch port of the network component to which the access point is
connected must be configured as a trunk port.
and that is to be forwarded to the WLAN clients is then carried by the configured VLAN. All other data,
such as VoIP packets, configuration data or authentication data (Radius), is given the VLAN tag
configured for the RFP. The switch port of the network component to which the access point is
connected must be configured as a trunk port.
Note: The RFP 42 WLAN and RFP 43 WLAN must be connected at
least via a 100BaseT Ethernet link in order to activate the RFP’s
WLAN function.
WLAN function.