Specifications

Engineering Guidelines
178
The configuration table will look similar to that in Table 54.
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.
Table 54: 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