[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Configuring Call Admission Control (CAC)

CAC prevents bottlenecks by limiting new and active dialogs and transactions. You configure CAC criteria in objects called controllers. You then assign the controllers to actions in new transaction policies.

Configuring Controllers

You can define up to 100 controllers for a BSG.

To cause the software to block all new dialogs or out-of-dialog transactions and to send 403 (Forbidden) messages, set the relevant committed-attempts-rate to 0 and the maximum-burst-size to 0.

Step-by-Step Procedure

To configure a controller for CAC:

  1. Create a controller.
    [edit services border-signaling-gateway gateway bsg-1]
    user@host#edit admission-control controller1
  2. Access the dialog configuration for this CAC controller.
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1]
    user@host#edit dialogs
  3. Configure the maximum number of concurrent dialogs.
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1 dialogs]
    user@host#set maximum-concurrent 50000
  4. Configure the maximum number of new dialog attempts per second.
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1 dialogs]
    user@host#set committed-attempts-rate 50
  5. Configure the maximum burst size (number of dialog attempts).
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1 dialogs]
    user@host#set committed-burst-size 100
  6. Access the transaction configuration level for this CAC controller.
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1 dialogs]
    user@host#up 1
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1]
    user@host#edit transactions
  7. Configure the maximum number of concurrent transactions.
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1 transactions]
    user@host#set maximum-concurrent 50000
  8. Configure the maximum number of new transaction attempts per second.
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1 transactions]
    user@host#set committed-attempts-rate 50
  9. Configure the maximum burst size (number of transaction attempts).
    [edit services border-signaling-gateway gateway bsg-1 admission-control controller1 transactions]
    user@host#set committed-burst-size 100

Assigning Controllers to New Transaction Policies

To assign a controller, you add the name of a controller to the then action in a new transaction policy.

Step-by-Step Procedure

To assign a controller to a new transaction policy:

  1. Access the configuration of the new transaction policy.
    [edit]
    user@host#edit services border-signaling-gateway gateway bsg–1 sip new-transaction-policy policy10 term peer-to-peer then
  2. Assign the controller to the new transaction policy.
    [edit services border-signaling-gateway gateway bsg–1 sip new-transaction-policy policy10 term peer-to-peer then]
    user@host#set admission-control controller1

Related Topics

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]