Engineering Guidelines
182
The configuration table will look similar to that in Table 53.
Deployment boundaries
There are limitations that apply to the current configuration of nodes and paths within the Call
Admission Control tree. These are listed below.
•
Maximum 6 paths per pipe
•
Maximum 6 levels on the configuration tree. A “perimeter node” is considered an end point.
•
Maximum 999 zones within a configuration tree
6 paths per pipe
A common pipe between zones can carry multiple connections. One example is IP Trunks
between nodes and connections to remote terminals hosted from a remote controller. Each of
these would be considered a single path, and so this example has two paths in a common pipe.
6 levels on the tree
Typically, this would allow up to 6 levels of branching from the root node, including the root
node. A “perimeter node” is a termination point for the tree. This makes it possible to break a
complex configuration into smaller, localized trees and connect these through the overall
“perimeter nodes.”
Using the examples above
•
the meshed network is a single network with 2 levels
•
the non-meshed appears to have 4 levels, but is actually 3 networks, each with 2 levels
connected by a common set of perimeter nodes
999 zones within a Configuration Tree
This limits the number of zones that can be configured in a single configuration tree. A perimeter
node terminates the zone count. This allows configuration of more complex networks with more
zones.
Redundant WAN links and load sharing
The usable bandwidth to be counted on such links (by number of calls using the link) must be
considered and may be set according to business requirements. A standby link may provide
the same, or reduced, bandwidth as compared to the main link that has failed. In this case, the
Table 53: Non-meshed Configuration
ZONE
PARENT
PERIMETER
ANCHOR
MANAGER
BANDWIDTH
1
none
No
Yes
2
none
No
3
none
No
11
1
Yes
Unit A in Zone 1
1024 kbps
12
2
Yes
Unit B in Zone 2
256 kbps
13
3
Yes
Unit C in Zone 3
256 kbps
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: ... ...