Mitel MiVOICE BUSINESS, Engineering Manualline

Page: 153 / 381

IP Networking
139
IP NETWORKING CONSIDERATIONS
This chapter discusses how IP networking and IP trunks affect the 3300 ICP. The terms “IP
networking” and “IP trunks” have become synonymous. However, “IP networking” covers the
whole picture, while “IP trunks” refers to the individual call connections. See the following topics
for more information:
• “IP Networking Node Restrictions” on page 139
• “Clustering” on page 140
• “Call Handling, Routing, and Bandwidth” on page 143
• “Route Optimization” on page 146
• “Automatic Route Selection” on page 147
• “Number Planning and Restrictions” on page 147
• “IP Networking and Product Release Compatibility” on page 147
• “SIP Trunking” on page 148
IP NETWORKING NODE RESTRICTIONS
A 3300 ICP is considered a node for IP networking. A node is defined through the numbering
plan and must be unique among networked devices. A single controller has the following
limitations:
• If no loop-back is set up, no more than 249 nodes can be connected to a single node.
• If a loop-back is set up, no more than 248 nodes can be connected to a single node.
• No more than 2000 (200 prior to Release MCD 5.0) calls can be made across IP trunks
between any two nodes, and no more than 2000 IP trunk calls can be made from one
controller at any one time.
MULTI-NODE MANAGEMENT RESTRICTIONS
Multi-Node Management provides a number of installer functions that simplify provisioning and
management of a sub-group of controllers or gateways. Because of the performance impact
of distributing data to a large number of nodes simultaneously, the maximum size of an
Administrative Group with Multi-Node Management enabled is 20 nodes. In releases MCD 4.0
and MCD 4.1 this is recommended but not strongly enforced. In MCD Release 4.2 if the size
of the Administrative Group is larger than 20 nodes, Multi-Node Management is automatically
disabled. Refer to Clustering for Multi-Node Management under Administrative Groups for more
details on this limitation.