VoIP Security
349
When a PC is connected to a port, it will be interrogated in the same manner as the phones,
and user input will be required. The same results will likely occur.
Typically, 802.1X will only allow a single device to be authenticated and connected to a port.
This restricts how devices can be connected into the network infrastructure. Where a network
port only supports a single connected device, then, for full authentication, only a phone or a
PC should be connected to this port. If it is required that both a phone and a PC must be
connected, then only the phone should provide authentication. If authentication is provided only
by the PC and the PC isn’t present, the phone may not work.
Not all network access devices place single device restrictions on connected devices. HP
switches allow multiple devices to be connected and authenticated on a single port. With Cisco
switches, where the IP Phone uses the Auxilliary_VLAN setting, both an IP Phone and a
connected PC can operate off the same port.
A PC connected behind a phone may need to authenticate access. Failure to do this correctly
may result in the network port being shut down. This may result in the IP Phone also being
disconnected. Ideally, the PC should be programmed with the necessary information for 802.1X
authentication through the “PC Network Properties.” If not, then it is possible that the PC could
fail the authentication time-out at the port or at subsequent authorization requests. It may also
be necessary to connect the PC to the phone after the phone has authenticated the connection.
An 802.1X port may be configured to request authentication only at startup of the network port
and this may include regular authentication retries.
Because authentication is based on a network port becoming active, it is possible, with some
network switches, that an unauthorized device could be connected behind an IP Phone once
the IP Phone has itself gained access to the port. Therefore, it is recommended that you enable
the re-authentication response to regularly check access to the port and identify such
connections. The default time is often of the order of 3600 seconds.
A phone that supports 802.1X will indicate, during power up, that it is attempting 802.1X
authentication. It is possible to disable 802.1X via a CONFIG application menu under Tools
and Features. This menu also allows you to delete any stored usernames and passwords.
For details on 802.1X, refer to the "802.1X EAP - MD5 Authentication Protocol Support"
Knowledge Base article on Mitel OnLine.
Note:
Some vendors, Hewlet Packard, for example, manufacture switches that support
multiple instances of 802.1X for devices that are connected to the same port. In this case,
you can enable support on both devices without risking access conflicts.
Note:
In some cases, network administrators may be running 802.1X to prevent
unauthorized users from accessing the network. As an example, Ethernet drops in
semi-public spaces such as reception areas would likely be protected with 802.1X.
Use caution if deploying phones that do not support 802.1X in these situations, because
the network administrator will not be able to enable 802.1X on this network port. If the
phone provides a secondary ethernet port, this port will also be unable to provide
authentication support
.
Содержание MiVOICE BUSINESS
Страница 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Страница 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Страница 16: ......
Страница 22: ...Engineering Guidelines 8 ...
Страница 23: ...Chapter 2 SYSTEM OVERVIEW ...
Страница 24: ......
Страница 28: ...Engineering Guidelines 14 ...
Страница 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Страница 30: ......
Страница 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Страница 74: ......
Страница 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Страница 100: ...Engineering Guidelines 86 ...
Страница 101: ...Chapter 5 POWER ...
Страница 102: ......
Страница 128: ...Engineering Guidelines 114 ...
Страница 129: ...Chapter 6 PERFORMANCE ...
Страница 130: ......
Страница 135: ...Chapter 7 APPLICATIONS ...
Страница 136: ......
Страница 142: ...Engineering Guidelines 128 ...
Страница 143: ...Chapter 8 EMERGENCY SERVICES ...
Страница 144: ......
Страница 151: ...Chapter 9 IP NETWORKING ...
Страница 152: ......
Страница 167: ...Chapter 10 LICENSING ...
Страница 168: ......
Страница 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Страница 184: ......
Страница 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Страница 210: ......
Страница 244: ...Engineering Guidelines 230 ...
Страница 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Страница 246: ......
Страница 309: ...Appendix A CAT 3 WIRING ...
Страница 310: ......
Страница 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Страница 316: ...Engineering Guidelines 302 ...
Страница 317: ...Appendix B INSTALLATION EXAMPLES ...
Страница 318: ......
Страница 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Страница 336: ......
Страница 347: ...Appendix D VOIP AND VLANS ...
Страница 348: ......
Страница 353: ...Appendix E VOIP SECURITY ...
Страница 354: ......
Страница 381: ... ...