The congestion configuration objects described on this page together provide a facility for managing call congestion on the SBC. Specific configuration for each object is done on the subordinate windows for each object.

  • adaptive – Specifies the congestion level at which the adaptive congestion control algorithm activates. The adaptive algorithm iteratively adjusts the call acceptance rate up or down to maximize call throughput while maintaining target performance metrics throughout an overload event. The algorithm is self-tuning to automatically adjust to the SBC nominal capacity (and to non-call-rate related events consuming unpredictable amounts of CPU) and is independent of call scenario mix, signaling types, and user retry behavior. There is a single default configuration for all system configurations. Emergency calls may optionally be given preference over non-priority calls.

 The system congestion levels (machine congestion, or MC, levels) each provide an increasing level of response to higher levels of congestion within the SBC.

  • Level MC1 –  Specifies limited congestion level. By default, no calls are rejected due to congestion in this level.
  • Level MC2 – Specifies moderate congestion level. By default, the adaptive congestion controls activate when this level of congestion is reached.
  • Level MC3 – Specifies critical congestion level. By default, this level is disabled (out of service) since the adaptive congestion controls (which activate at level MC2) prevent the box from reaching this level.

In levels MC1 and MC2, the SBC software will attempt to balance traffic by assigning H.323 and SIP calls to non-congested modules. In levels MC1, MC2, and MC3, all INFO event log messages are suppressed. These congestion levels only apply to the packet calls. You define the threshold at which these congestion levels are triggered by associating each level with an Overload Profile. Default Overload Profiles are provided for each MC level:

    • defaultMC1
    • defaultMC2
    • defaultMC3
Note:

For SBC SWe deployments, the preceding three default profiles are assigned automatically to MC1, MC2, and MC3 when a standard or custom traffic profile is activated. For SWe deployments in which the default traffic profile is activated, a separate set of overload profiles is provided and mapped to MC1, MC2, and MC3 automatically:

  • sweOverloadProfileMC1
  • sweOverloadProfileMC2
  • sweOverloadProfileMC3

    Modified: for 6.2.1

 
  • Policer – Specifies the system congestion Call Rate Policer configuration. 

During a sustained system load, the SBC accepts calls at a smooth rate, avoiding behavior such as accepting all calls for a short period of time, and then rejecting all calls for the remaining sampling period. This is accomplished with system-level policers. Unlike IP Traffic Policers--which control the allowed rate of incoming IP packets, congestion policers control the allowed rate of incoming calls in a system. Individually configurable bucket sizes (POLICER BUCKETSIZE) control the call burst handling capability. The policer fill rate controls the sustained rate (the rate at which tokens are added to the bucket). In this case, the fill rate is the sustained call rate allowed at calls per second (CPS). Fill rates are not configurable when using congestion policers; instead, they are dynamically adjusted based on resource usage, to maximize those resources.

On the SBC main screen, go to All > System > Congestion.

The Congestion window is displayed.

The adaptive mode for system congestion control is enabled by default.

System - Congestion

 

 

Additional topics in this section: