1531-DBC 422 02 Uen B3 2013-12-02
54
I
NSTALLATION
At installation (and hardware reboot) the phone asks for an IP address
from DHCP by initiating the DHCP negotiation with untagged messages
(native LAN). DHCP provides the IP address but no VLAN identity list.
The phone reads the configuration file, but in this case when no VLAN
identity list is received from DHCP, a software reboot is done automati-
cally in the phone to get the IP address valid for the tagged VLAN
defined in the configuration file.
The configuration file is read from the VLAN
At installation (and hardware reboot) and the configuration file is avail-
able in the VLAN but not in the native LAN, the VLAN identity must be
set manually in the boot menu.
7.20.3 Manual
setting
of the VLAN identity
Set the VLAN identity from the menu in the boot sequence. To use the
manual entered VLAN identity all the time, disable the VLAN settings in
the configuration file.
7.21 Security
There are two security features:
•
LAN access control, see 7.22 LAN access control (according to
IEEE802.1x) on page 58.
•
VoIP signalling with TLS and media encryption with SRTP. This is
described in this section.
The TLS and SRTP support can be enabled/disabled from the configu-
ration file, see the description for
CONFIGURATION FILE FOR DBC
42X
section SECURITY.
In addition there is a security policy in the telephony system which also
affects the behavior of the IP phones. For MX-ONE Telephony Server,
see the description for
SECURITY
.
The security policy is checked at the registration time. Once the phone
is registered, all kinds of calls can be established from a security
perspective.
When a secure IP to IP call is established, with TLS and SRTP, a secure
icon (a padlock) is shown in the display. For all gateway calls the secure
icon is not shown because the other party can have an un-secure
connection. When there is a secure IP to IP call and IP voice recording
is active the secure icon is not shown.
