Engineering Guidelines
348
AUTHENTICATION PROTOCOL SUPPORT
A number of networks now support a level of access restriction to the network ports. A device
that connects to one of these ports needs to be authenticated as valid before connections can
be established. There are a number of protocols that can do this, including:
•
Cisco VMPS
•
802.1X
The Cisco VMPS is described in “VMPS, CDP, and Location Change Indication (E911)” on
page 251.
Mitel implements phone authentication that requires a unique association of MAC addresses
and IP and user-entered PIN registration numbers. Additionally, desktop software downloads
are encrypted. Mitel also provides 802.1X authentication for desktops, and that supports the
Extensible Authentication Protocol (EAP) using EAP-MD5 challenge authentication to a
RADIUS Server. Users authenticate through the phone interface by entering a username and
password.
DUAL PORT PHONES
A number of Mitel's IP phones are dual port, meaning that there are two ethernet ports on the
phone. One ethernet port is used to connect to the LAN. The other ethernet port can be used
to connect a PC to the network via the phone, this capability is useful in environments where
the phone and the PC need to share a single ethernet connection.
As of MCD 4.1 a COS option is provided that can be used by the System Administrator to
disable the second ethernet port on dual port phones, which in turn will bar unauthorized access
at the second ethernet port. The default condition is for all second ethernet ports to be enabled;
for details on how to set a COS option to disable secondary ethernet ports on IP phones, refer
to the
System Administration Tool Help
for MiVoice Business.
IEEE 802.1X
The IEEE 802.1X standard is similar in operation to VMPS, but uses a RADIUS Server for
authentication. Devices that authenticate through 802.1X require an identification name and
password before being allowed access.
There are a number of protocols that are used to establish the initial connection. Mitel end
devices ("supplicants") support the EAP-MD5 protocol.
If the administrator configures the L2 Switch for port access control, the connected IP Phone
will prompt the user for an account name and password if one has not already been entered
or if the information saved in the phone is invalid. Based on the response,
•
the port may be opened for access
•
the VLAN settings may change
•
the port could be opened to a guest VLAN
•
the port could be shut down.
Summary of Contents for MiVOICE BUSINESS
Page 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Page 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Page 16: ......
Page 22: ...Engineering Guidelines 8 ...
Page 23: ...Chapter 2 SYSTEM OVERVIEW ...
Page 24: ......
Page 28: ...Engineering Guidelines 14 ...
Page 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Page 30: ......
Page 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Page 74: ......
Page 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Page 100: ...Engineering Guidelines 86 ...
Page 101: ...Chapter 5 POWER ...
Page 102: ......
Page 128: ...Engineering Guidelines 114 ...
Page 129: ...Chapter 6 PERFORMANCE ...
Page 130: ......
Page 135: ...Chapter 7 APPLICATIONS ...
Page 136: ......
Page 142: ...Engineering Guidelines 128 ...
Page 143: ...Chapter 8 EMERGENCY SERVICES ...
Page 144: ......
Page 151: ...Chapter 9 IP NETWORKING ...
Page 152: ......
Page 167: ...Chapter 10 LICENSING ...
Page 168: ......
Page 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Page 184: ......
Page 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Page 210: ......
Page 244: ...Engineering Guidelines 230 ...
Page 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Page 246: ......
Page 309: ...Appendix A CAT 3 WIRING ...
Page 310: ......
Page 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Page 316: ...Engineering Guidelines 302 ...
Page 317: ...Appendix B INSTALLATION EXAMPLES ...
Page 318: ......
Page 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Page 336: ......
Page 347: ...Appendix D VOIP AND VLANS ...
Page 348: ......
Page 353: ...Appendix E VOIP SECURITY ...
Page 354: ......
Page 381: ... ...