Page History
...
| Panel |
|---|
...
...
Back to Call Admission Controls - CLI
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
| Spacevars | ||
|---|---|---|
|
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.
| Note |
|---|
| 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:
| Code Block | ||
|---|---|---|
| ||
% delete addressContext AC1 zone ZONE_IAD sipTrunkGroup TG1 parentSharedCacLimitsPoolName
% commit
% delete global cac sharedCacLimitsPool CAC0
% commit |
Deletion Scenario 2:
| Code Block | ||
|---|---|---|
| ||
% delete global cac sharedCacLimitsPool CAC0 parentSharedCacLimitsPoolName
% commit
% delete global cac sharedCAcLimitsPool CAC1
% commit |
| Include Page | ||||
|---|---|---|---|---|
|
Command Syntax
Use the following CLI syntax to configure global CAC policy:
| Code Block | ||
|---|---|---|
| ||
% 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)
subscriberBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
subscriberRateMax <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)
subscriberBurstMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
subscriberRateMax <1-2000, unlimited> (SBC 7000 range is 1-6000, unlimited)
parentSharedCacLimitsPoolName <name>
registrationLimit <0-2000000000, unlimited>
subscriptionLimit <0-2000000000, unlimited> |
Command Parameters
...
| class | pdf6pttext |
|---|
Global CAC Parameters
| Caption | ||||
|---|---|---|---|---|
| ||||
|
...
|
...
|
...
|
...
|
...
|
...
|
Egress/Ingress Parameters
| Info |
|---|
The default value for all of the CAC parameters below is 'unlimited'. |
| Caption | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
|
...
|
...
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
|
...
|
...
|
...
|
...
|
...
|
...
|
...
emergencyOversubscription– (Default = 100) The percentage over the configured allowed number of resources for an IP trunk group that Emergency calls can consume. Up to 10x can be allocated. (range: 1-1000)ingress– Ingress-specific CAC configuration. (seeegressdescription above for list of parameters)parentSharedCacLimitsPoolName– Name of an existing shared CAC-limits pool.registrationLimit– (Default is 'unlimited') The total number of concurrent SIP registrations allowed. (range: 0-2000000000, or unlimited)subscriptionLimit– (Default is 'unlimited') The total number of concurrent SIP subscriptions allowed. (range: 0-2000000000, or unlimited)
|
...
Command Example
| Code Block | ||
|---|---|---|
| ||
% 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