Engineering Guidelines
238
Since these values are non-user programmable they cannot be changed by the system
administrator. These values do not provide the correct priority levels for voice media at either
L2 or L3, therefore the use of these values will potentially cause severe voice quality issues.
The Solutions:
1.
If it is a requirement to keep LLDP-MED running on the Cisco switches:
•
Leave LLDP-MED running on the Cisco switches.
•
Use DHCP to provide the phones with the correct L2 and L3 priority settings.
DHCP learnt values have a higher priority and will override the LLDP-MED learnt values.
2.
In situations where there is no requirement to have LLDP-MED and CDP running on the
Cisco switches:
•
Disable LLDP-MED on the Cisco switches.
•
Disable CDP on the Cisco switches.
•
Use DHCP with double fetches to provide the phones with the correct L2 and L3 priority
settings. Information on DHCP double fetches can be found under “DHCP and IP Phone
network policy” on page 239“.
3.
If there is no requirement to keep LLDP-MED running on the Cisco switches:
•
Disable LLDP-MED on the Cisco switches.
•
Enable CDP to provide the phones with VLAN information.
•
When the phones detect that CDP is present on the LAN they will infer that the ‘default
Cisco values’ for L2 and L3 priority should be used.
The Cisco default values for priority are:
•
L2 (802.1p) = 5
•
L3 (DSCP) = 46
LAN POLICY VALUES FOR MEDIA, SIGNALLING AND OTHER
The System Administrator has a high degree of flexibility when deciding on how to program
LAN Policy.
LAN Policy values for signalling and voice can be programmed independently, or signalling and
voice can both be programmed with the same set of values.
Other data that might exist on the same network, or VLAN, as voice include management data
and downloads. This data is classified as ‘other’, as it is part of the solution, but not immediately
needed for real-time call handling.
For backwards compatibly with controllers running earlier software, both voice and signalling
should use a DSCP value of 46 and an IEEE 802.1p value of 6.
Note:
The inferred Cisco L2 and L3 values used by the phone are not permanent, these
values can be overwritten with installer defined DHCP values.
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: ... ...