Engineering Guidelines
246
Unused options MUST be left blank. Conflict may arise where a number of different devices
exist within the same subnet or DHCP scope (e.g. it is known that Microsoft Server 2003 also
uses options 132 and 133). It may be necessary to redefine options, or place some equipment
in different scopes, or select options based on device MAC address. Otherwise phones will
read this information and may give unpredictable results.
IP PHONE BEHAVIOR
The IP Phone is very forgiving of information received through DHCP. It will allow for any of the
three possible methods mentioned for delivery of the configuration, and within the
vendor-specific methods will account for variability found in how 3rd Party DHCP servers deliver
option 43 or option 125 formats (see “Support of solution by external DHCP servers” on
page 248.)
The following behavior rules apply to the IP Phone for received DHCP parameters:
•
IP Phone will accept any one of the three methods; option 125, option 43, or options
128-135, in order of priority.
-
If more than one method is received in the same DHCP offer, the one with highest
priority will be applied.
•
Within option 43 or option 125 responses, the IP Phone will accept the following formats
from the DHCP server side:
-
Option 43 or 125, with no sub-options,
-
Option 43 or 125, containing a single sub-option, ID = 1
-
Within the sub-option method, the final sub-option may be ID 0xFF, the “end of
options” option (as per RFC 2132).
-
Within any of above, you may have to null-terminate with 0x00 character.
131
IP address
Remote IP Phone Analyzer IP address
132
long word
802.1Q Layer 2 VLAN ID
133
long word
802.1Q/D Layer 2 Priority
134
long word
Diffserv Code Point (DSCP)
135
string
HTTP Proxy for phone-specific applications
Note:
The “Encapsulated vendor-specific options” formatting as defined in RFC 2132
and RFC 3925 is not normally used in the Mitel-specific exchange, however it is
accommodated by the IP Phone in order to support 3rd party DHCP severs that require it.
Table 72: Mitel-Internal current DHCP Option Usage (continued)
DHCP
OPTION
FIELD TYPE
DESCRIPTION
Page 2 of 2
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: ... ...