In some network configurations, you may need to balance the bandwidth between multiple 3300 ICPs located in one zone, going to another destination zone. This would be useful for sets being registered on different ICPs within a headquarters zone environment. You can create mulitple-zone access points between the two zones so the bandwidth limit leaving the zone can be shared between different 3300 ICPs. See the example below for an example:
Load Sharing Between ICPs
In this configuration, the total bandwidth leaving Zone 4 can be split between ICP 1 and ICP 2 in appropriate portions. Each system will manage its own bandwidth across the zone access point.
Your IT Administrator has identified the potential bottlenecks in the data pipe where the Zone Access Points (ZAPs) should be located. The IT Administrator has assigned the following bandwidth limits for the voice media streams through the ZAPs as follows:
ZAP Label and ID |
Bandwidth Limit |
Toronto-Ottawa (1) |
500 kBits/s |
Toronto-Ottawa (2) |
500 kBits/s |
If the bandwidth is blocked across one of the Zone Access Points, the call could then be routed through the other ICP that may have bandwidth available to allow the call to be connected across the network.
Call Routing Through Non-Blocked ICP
The following network Zone Configuration is simplified for such a configuration:
Multi-ZAP Zone Tree Configuration
You would complete the following programming from the aspect of ICP 2.
Network Elements |
|
Zone Tree Assignment |
|||
Name |
Zone |
|
Zone |
Parent Zone |
Perimeter |
Ottawa ICP 2 (Local) |
4 |
|
2 |
4 |
No |
Ottawa ICP 1 |
4 |
|
|
|
|
Toronto |
2 |
|
|
|
|
Zone Access Point Assignment (Summary) |
||||
Zone |
Zone Access Point ID |
Zone Access Point Label |
Bandwidth Limit |
Network Element |
2 |
1 |
Toronto-Ottawa (1) |
500 |
Ottawa ICP 1 |
2 |
2 |
Toronto-Ottawa (2) |
500 |
Ottawa ICP 2 |