In this section:
The SBC 5100, SBC 5110, SBC 5200, and SBC 5210 platforms are no longer supported beginning with the SBC Core 10.0.0R0 release. This release supports SBC 5400/7000/SWe platforms. Contact Ribbon Sales for upgrade information.
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 SBC.
Validation rules:
Call processing rules when using shared CAC-limits pool involve:
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.
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
Unless annotated otherwise, the parameter values in this section apply to the SBC Core.
SIP subscription CAC limits are not applied to SUBSCRIBE requests from registered users in access deployments.
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>
The default value for all of the CAC parameters below is 'unlimited'.
% 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; } }