Configuring Allowed Audio Coder Groups - AudioCodes Mediant 500 E-SBC User Manual

Parameter
Rate
CLI: rate
[SBCAdmissionControl_Rate]
Maximum Burst
CLI: max-burst
[SBCAdmissionControl_MaxBurst
]
Reservation
CLI: reservation
[SBCAdmissionControl_Reservati
on]
28.3

Configuring Allowed Audio Coder Groups

The Allowed Audio Coders Group table lets you configure up to five Allowed Audio Coders
Groups. An Allowed Audio Coders Group defines a list of audio media coders that can be
used for a specific SIP entity. Each Allowed Audio Coders Group can be configured with up
to 10 coders. The coders can include pre-defined audio coders (according to the installed
Software License Key) and user-defined (string) coders for non-standard or unknown
coders.
Allowed Audio Coders Groups are assigned to SIP entities, using IP Profiles (see
''Configuring IP Profiles'' on page 300). Coders that are not listed in the Allowed Audio
Coders Group are removed from the SDP offer ('a=rtpmap' field) that is sent to the SIP
entity. Only coders that are common between the coders in the SDP offer and the coders
listed in the Allowed Audio Coders Group are used. Thus, Allowed Audio Coders Groups
enable you to enforce the use of only specified coders. For more information, see
''Restricting Coders'' on page 445.
The order of appearance of the coders listed in the Allowed Audio Coders Group
determines the priority (preference) of the coders in the SDP offer. The device arranges the
User's Manual
Defines the rate at which tokens are added to the token bucket
per second (i.e., token rate). One token is added to the bucket
every 1000 divided by the value of this parameter (in
milliseconds).
The default is 0 (i.e., unlimited rate).
Note: The token bucket feature is per IP Group, SRD, SIP
request type, and SIP request direction.
Defines the maximum number of tokens (SIP dialogs) that the
bucket can hold. The device only accepts a SIP dialog if a
token exists in the bucket. Once the SIP dialog is accepted, a
token is removed from the bucket. If a SIP dialog is received
by the device and the token bucket is empty, then the device
rejects the SIP dialog. Alternatively, if the bucket is full, for
example, 100 tokens, and 101 SIP dialogs arrive (before
another token is added to the bucket, i.e., faster than that
defined in the Rate field), then the device accepts the first 100
SIP dialogs and rejects the last one.
Dropped requests are replied with the SIP 486 "Busy Here"
response. Dropped requests are not counted in the bucket.
The default is 0 (i.e., unlimited SIP dialogs).
Note: The token bucket feature is per IP Group, SRD, SIP
request type, and SIP request direction.
Defines the guaranteed (minimum) call capacity.
Notes:

An IP Group ID or SRD ID must be specified when this
parameter is configured and the IP Group or SRD cannot
be set to all (-1).

Reserved call capacity is applicable only to INVITE and
SUBSCRIBE messages.

Reserved call capacity must be less than the maximum
capacity (limit) configured for the CAC rule.

The total reserved call capacity configured for all the CAC
rules must be within the device's total call capacity support.
468
Mediant 500 E-SBC
Description
Document #: LTRT-10427