In this section:
Use this feature to define multi-level Call Admission Control (CAC) policy using IP hierarchal trunks. A hierarchy is created by linking trunks together in a pyramid-type structure. Regular IP trunks are at the base of the pyramid; above them in the pyramid are IP linked trunks or shared CAC-limits pools.
A shared CAC-limits pool is a global resource that constrains the resource usage of a set of trunks. Both the limit and current usage is maintained for each value. A shared CAC-limits pool is not tied to a specific zone or address context. There may be up to 2,000 shared CAC limits pools on
Unable to show "metadata-from": No such page "_space_variables"
.Validation rules:
- There can only be one parent for any object.
- An IP trunk group can be assigned as child to any CAC-limits pool (parent).
- A CAC-limits pool can be assigned as a parent to any other CAC-limits pool that does not have a parent of its own.
- A CAC-limits pool cannot be assigned to a parent if it already has a CAC-limits pool child.
- The children of a particular CAC-limits pool can be either CAC-limits pools or IP trunks.
Call processing rules when using shared CAC-limits pool involve:
- Applying the configured limits.
- Checking the limits of the parent above in the pyramid. If limits are met by all parents, the call is admitted.
The hierarchy has a maximum of three levels: two levels of shared CAC-limits pool and an IP trunk at the bottom. The hierarchy is built bottom up by assigning a parent to an existing trunk group or CAC-limits pool. The parents must exist before being assigned.
When deleting a parent and associated child CAC, be sure to first de-associate the child from the parent before deleting the parent CAC. Do not attempt to delete both in the same transaction. See examples below:
Deletion Scenario 1:
% delete addressContext AC1 zone ZONE_IAD sipTrunkGroup TG1 parentSharedCacLimitsPoolName % commit % delete global cac sharedCacLimitsPool CAC0 % commit
Deletion Scenario 2:
% delete global cac sharedCacLimitsPool CAC0 parentSharedCacLimitsPoolName % commit % delete global cac sharedCAcLimitsPool CAC1 % commit
Note
Unless annotated otherwise, the parameter values in this section apply to the SBC Core.
Command Syntax
Use the following CLI syntax to configure global CAC policy:
% set global cac sharedCacLimitsPool <pool_name>
bandwidthLimit <0-2000000000, unlimited>
bandwidthLimitThreshold <0-100>
bandwidthVideoThreshold <0-100>
callLimit <0-2000000000, unlimited>
callLimitThreshold <0-100>
egress
callBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
callRateMax <1-1000, unlimited> (SBC 7000 range is 1-3000, unlimited)
otherReqBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
otherReqRateMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
registerBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
registerRateMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
subscribeBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
subscribeRateMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
emergencyOversubscription <1-1000>
ingress
callBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
callRateMax <1-1000, unlimited> (SBC 7000 range is 1-3000, unlimited)
otherReqBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
otherReqRateMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
registerBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
registerRateMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
subscribeBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
subscribeRateMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
parentSharedCacLimitsPoolName <name>
registrationLimit <0-2000000000, unlimited>
subscriptionLimit <0-2000000000, unlimited>
Command Parameters
Global CAC Parameters
Global CAC Parameters
Parameter | Description |
|---|---|
| Use this object to specify shared CAC-limits pool name. |
|
|
Egress/Ingress Parameters
The default value for all of the CAC parameters below is 'unlimited'.
Egress/Ingress Parameters
| Parameter | Length/Range | Descriptions |
|---|---|---|
callBurstMax | SBC 5xx0/SWe: 1-2000, or unlimited SBC 7000: 1-6000, or unlimited | <value> – Maximum allowed burst (above the allowed sustained rate) for egress call attempts. |
callRateMax | SBC 5xx0/SWe: 1-1000, or unlimited SBC 7000: 1-3000, or unlimited |
NOTE: You can set both "callRateMax" and "callBurstMax" as "unlimited"; however, if you assign a value to one parameter, the other must also be assigned a value. |
otherReqBurstMax | SBC 5xx0/SWe: 1-2000, or unlimited SBC 7000: 1-6000, or unlimited) | <value> – Maximum allowed burst (above the allowed sustained rate) for all other egress out-of-dialog SIP request. |
otherReqRateMax | SBC 5xx0/SWe: 1-2000, or unlimited SBC 7000: 1-6000, or unlimited) |
|
registerBurstMax | SBC 5xx0/SWe: 1-2000, or unlimited SBC 7000: 1-6000, or unlimited) |
|
registerRateMax | SBC 5xx0/SWe: 1-2000, or unlimited SBC 7000: 1-6000, or unlimited) |
NOTE: You can set both "registerBurstMax" and "registerRateMax" as unlimited; however, if you assign a value to one parameter, the other must also have a value. |
subscribeBurstMax | SBC 5xx0/SWe: 1-2000, or unlimited SBC 7000: 1-6000, or unlimited) |
|
subscribeRateMax | SBC 5xx0/SWe: 1-2000, or unlimited SBC 7000: 1-6000, or unlimited) |
|
Command Example
% set global cac sharedCacLimitsPool POOL bandwidthLimit
1000 bandwidthLimitThreshold 1 callLimit 1000
callLimitThreshold 1 egress callBurstMax 50
% show global cac
sharedCacLimitsPool POOL {
callLimit 1000;
callLimitThreshold 1;
bandwidthLimit 1000;
bandwidthLimitThreshold 1;
egress {
callBurstMax 50;
}
}
Overview
Content Tools