Engineering Guidelines
18
TYPICAL INSTALLATION CONFIGURATIONS
The MiVoice Business platorm can be designed into different network configurations to suit the
organization of the enterprise. See the following examples for an illustration of how the
organization of the enterprise affects the overall network and unit configurations:
•
“Multiple Units System” on page 18
•
“Distributed System” on page 18
•
In the descriptions below, a unit is considered to be a 3300 ICP with a particular configuration
and is part of the overall telephony system.
MULTIPLE UNITS SYSTEM
In a multiple unit configuration, a number of units are clustered together, but each unit functions
independently. The units connect to each other through the network, using IP trunks or TDM
trunks. In the event of a unit failure, some of the overall system will fail. In the event of a network
failure, the units still maintain PSTN access. In a small- or medium-sized office, a number of
units could be installed together to make a larger system. Another scenario could be a small-
or medium-sized business with a number of branch offices (for example, an automobile
dealership), where local access is needed, but intershop traffic is also a requirement.
Figure 2: Example of a Multiple Units Configuration
DISTRIBUTED SYSTEM
In a distributed system, different telephony system functions are dedicated to individual units.
These are then distributed to different parts of the network, or business as required. This may
be a large and geographically dispersed enterprise. For example, a number of units could act
purely as TDM gateways providing central access, with other units acting as central voice mail
and others acting as the group controllers (a group controller is a 3300 ICP to which a group
of IP phones have been registered). An example is a university campus where each building
possesses the group controller and local phones, but the PSTN access is in a separate secure
building. A different scenario is a large enterprise with corporate headquarters in different cities.
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: ... ...