Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

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

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb41059c, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7f046c, userName='null'}
JIRAIDAUTHSBX-88903
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8c30172, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8c30172, userName='null'}


Panel

In this section:

Table of Contents
maxLevel3
minLevel2



Info
iconfalse

Related articles:


HPC Throttling (CAC)

The SBC supports a throttling mechanism that controls the number of GETS call requests for an IP Peer. The SBC invokes throttling when at least one of the following exceeds for the IP Peer:

  • The configured maximum rate of GETS call requests processed during a particular interval.
  • The configured maximum number of concurrent GETS calls.

Include Page
SBXDOC120:_GETS_Use_NoteSBXDOC120:
_GETS_Use_Note

If the SBC classifies a call as GETS and rejects the call due to Call Admission Controls (CAC), the SBC sends a SIP 403 (Forbidden) response with a Q.850 cause value of 21 (call rejected) in the Reason header field. The RPH of the response does not contain any ets or wps namespaces.

When the SBC hits the GETS CAC rate and call limit thresholds, the SBC logs events that indicate the peer entity that sent the request and the time the request sent. 


Info
titleNote

For more information, refer to:


Pagebreak