# Program Bandwidth Management

## Conditions/Dependencies

- Configuration data for Bandwidth Management applies to most MiVoice Business systems in the network. This information is shared at the Network level by default (see Programming below). Even though a MiVoice Business system could have more information than necessary, consistent configuration across a network of MiVoice Business systems is necessary for Bandwidth Management to function properly.

- Bandwidth Management information needs to be shared using SDS; otherwise, conflicting information may prevent the feature from working properly.

- It is recommended that you enter data into one network element and then enable SDS sharing with all other MiVoice Business systems. See the Bandwidth Management section in SDS Application Specific Guidelines and Limitations for recommendations on the forms that are shared.

- When the Bandwidth Management form is shared, the Network Zone Topology form and the Zone Access Point Assignment sub-form must be shared at the same sharing scope.

- 3300 ICP Release 8.0 supports a nodal version of bandwidth management only. It does not support a centralized view of bandwidth consumption within the network or the cluster. a MiVoice Business system managing a Zone Access Point (ZAP) monitors only the bandwidth consumed at that ZAP. For a call's bandwidth to be counted at the ZAP, the call must be routed through the MiVoice Business system managing that ZAP.

- When Call Admission Control is enabled it may take up to one minute for CAC to start blocking traffic.

- A hot desk user who is logged into a set uses the zone settings that are assigned to the physical set DN, not the zone settings that are assigned to the hot desk DN. If you change the zone settings for a set while a hot desk user is logged in on that set, the hot desk user must log out and log back in before the new zone settings are applied.

- Calls over SIP trunks to DISA answer points and Hot Desking access numbers require an extra 32K of bandwidth. The extra is needed because the call is actually completed in two stages, each requiring its own bandwidth. Bandwidth for the first stage (allocating a DTMF receiver and tone generator to the SIP trunk) is used temporarily while the controller sets up the resources for Stage 2 (establishing a voice path to the destination).

- The following rules and behaviors apply to zone IDs when data sharing in a mixed-release network
  A network of switches running different versions of call control software.:

- the default Zone ID value of 1 cannot be changed for any pre 3300 ICP Release 8.0 elements.

- zones IDs greater than 128 are not supported when data sharing between 3300 ICP Release 8.0 and older releases.

- elements sharing data via SDS should all be running software release with the same zone capacity. Thus, an MCD 5.0 SP1 element, which supports 999 zones, should only share with other MCD 5.0 SP1 or later elements. Otherwise, attempts to sync zone data will fail. To maintain synchronization until the entire sharing community is at same zone capacity, use zone IDs below 251.

- for resiliency, both the primary and secondary elements must be at the same zone capacity (250 zones with 250 zones or 999 zones with 999 zones). You cannot get around this requirement by using zone IDs under 251.

## Programming

To program bandwidth management

1. Collect site information

2. Network Elements form

3. Enable SDS Sharing.

4. Define Nodes in the network.

5. Based on your Zone Tree Diagram, assign Zone IDs to the nodes.

3. ICP/PBX Networking form

4. Assign the Local field for the PBX you are using, and assign the IP addresses for all the PBXs.

4. Station Attributes form

5. Assign the associated Zone IDs to all the DNs registered with a MiVoice Business system.

6. If Manual is the Zone Assignment Method, you must enter the Zone ID in the Zone ID field.

7. If Default is the Zone Assignment Method, the Zone ID doesn't have to be entered because the Zone ID of the MiVoice Business system to which the set is registered is used.

5. Network Zone Topology form

6. Assign the Parent Zone IDs for each zone.

7. Indicate whether the parent of the zone contains a device, such as a MiVoice Border Gateway, that anchors the media path.

8. Indicate if the zone represents a Perimeter Zone delineating the edge of the tree or monitored network.

9. In the Zone Access Point Assignment sub-form:

   - Enter Zone Access Point Label.

   - Enter the Bandwidth Limit.

   - Enter the Network Element that manages the ZAP.

6. Bandwidth Management form

7. Enable Call Admission Control, if required.

8. Enable Bandwidth Reporting and Statistics, if required.

9. If Bandwidth Reporting & Statistics are enabled:

   - Modify the rising and falling thresholds for the Bandwidth Alarm, as required.

   - Modify the maximum number of 15-minute and 24-hour intervals, if required.

7. ARS Routes form

8. Change the route compression to Auto.

8. SDS Form Sharing form

9. Ensure that the Network Zones form is shared at the same scope as the Bandwidth Management forms.

Related Topics

- Collect Site Information