IP Networking
141
IP-TRUNK CONNECTION LIMITATIONS
Prior to Release MCD 5.0 there were some IP-Trunk limitations to consider. These include:
•
The number of IP-Trunk channels per connection, or route - 200 per route
•
The total number of IP-Trunk channels on the node, gateway or controller is limited to a
total 2000 provisioned channels
•
The number of IP-XNet Trunk Groups (321)
Prior to Release MCD 5.0, all IP-Trunk connections, or routes, had to be associated with an
IP/XNet trunk group and this restricted the number of IP-Trunk connections to 321 on a particular
unit, or node. This provides an upper limit to a meshed IP-Trunk network of 322 nodes.
At Release MCD 5.0 the following changes were made:
•
The number of IP-Trunk channels per connection, or route, is increased up to 2000. The
number of channels in use can still be restricted in the IP/XNet trunk group configuration
•
The total number of IP-Trunk channels on the node, gateway or controller is limited to 2000
active channels, i.e. it is possible to overprovision
•
The number of IP/XNet trunk groups was increased to 999 at Release MCD 5.0 SP2 PR2
•
Provision for IP-Trunk connections, or routes, can now be made via "Direct-IP" rather than
through IP/XNet Trunk Groups
The use of "Direct IP" and IP/Xnet Trunk Groups are mutually exclusive for a connection from
a programming point of view, but usage of both methods can be intermixed on the same node.
Use of Direct-IP removes the channel provisioning limit, or requirement, and also the need to
program up an additional IP/XNet Trunk Groups form.
For existing systems that migrate to Release MCD 5.0, or later, IP-XNet Trunk Groups can still
be used. The IP/XNet Trunk Groups can also be expanded, if needed. MCD 5.0 SP2 PR2
increases the number of connections up to 999.
For new installations it is recommended to use the Direct-IP setting for simplification of
management. Bandwidth management with zones should be used to provide a more accurate
bandwidth consumption analysis for remotely connected units.
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: ... ...