Engineering Guidelines
306
It is important that QoS be set up in the network end to end, not just in a few places. Internet
VPN connections (for example, IP Sec) are not under the control of the customer so QoS is
not end to end. VoIP is not controllable and quality is variable.
DEFINE THE IP ADDRESSING
The first step in planning a VoIP network is deciding upon the VoIP addressing scheme. Usually
a data network IP addressing scheme will already exist, so that will already be decided.
Choose an IP address range for the VoIP system that is not used elsewhere. Choose from one
of the private address spaces (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), such as
192.168.100.0/24.
If possible, do not use IP addressing that conflicts with the internal IP addresses of the 3300
ICP, 192.168.10.0/28 to 192.168.13.0/28. (For Rel. 7.0 and later, 169.254.10.0/28 to
169.254.30.0/28 are reserved.)
Devices that conflict with the internal addresses will NOT be able to communicate with the ICP
in any manner. Different networks must have different IP address ranges. There can’t be two
networks using the same IP addresses or the router can’t route traffic correctly. Each interface
(real or virtual) on a router is on a different network.
DEFINE THE VLAN
Most of the time, data will already exist and by default will be on VLAN 1. The next step in
planning a VoIP network is deciding on the voice VLAN, VLAN 100, for example.
To create a VLAN:
Switch# configure terminal
Switch(config)# vlan 100
Siwtch(config-vlan)# name VoiceVLAN
Switch(config-vlan)# end
The IP address ranges that were previously selected will be used on the voice VLANs.
Note:
MiVoice IP Phones set the 802.1q bits as they are using VLAN tagged traffic.
However the ICP controller does not send VLAN tagged traffic and so cannot set Ethernet
priority. The switch port the controller connects to should set the Ethernet priority. This
also applies to other non-VLAN aware VoIP devices, such as NuPoint Unified Messenger
Rel. 8.5.
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: ... ...