Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86820e56901685f374974002d, userName='null'}
JIRAIDAUTHSBX-101917
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86c120d6f016c28d6d3610012, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbfd06fa, userName='null'}

Include Page
_SLB_Supported_Platforms_SBC_SWe
_SLB_Supported_Platforms_SBC_SWe

Overview

The SIP-aware Load Balancer (SLB) load balances the SIP traffic to the registered SBCs . The SLB provides a using Peer Overload Control functionality. Based on the on the overload state of the SBC, the traffic is adjusted adjusts when the SBC is in a experiences an overload state.

The SLB supports Access deployments.  The The SLB installs the necessary ACL rules that are required to allow the traffic from the successfully registered UE/IP-PBX.


On the SBC main screen go to All System > Slb. The Slb configuration screen displays.


Image Added


ParameterLength/RangeDefaultDescription
Invite Req Timeout1-18090INVITE transaction timeout on the SLB.
Non Invite Req Timeout1-6432Non INVITE transaction timeout on the SLB. 
Register Req Timeout1-18090REGISTER transaction timeout on the SLB. 
Global Utilization1-100100

The SLB provides an option to set the Global Utilization threshold on the SLB and generates a trap when the Global Utilization exceeds the configured threshold. During overload conditions, the SLB calculates the Global Utilization based on utilizations reported from the registered SBCs, which is the average of the utilizations. The SLB uses Global Utilization to decrease the load on the SBC reporting higher Utilization.