AudioCodes Mediant 500 E-SBC User Manual page 323

User's Manual
Parameter
Web: Jitter Compensation
CLI: sbc-jitter-compensation
[IpProfile_SBCJitterCompensation]
Version 6.8
necessary when incoming RTCP is not compatible with the
destination SIP entity's (this IP Profile) RTCP support. In
such a scenario, the device can generate the RTCP and
send it to the SIP entity.

[0] Transparent (default) = RTCP is forwarded as is
(unless transcoding is done, in which case, the device
generates RTCP on both legs).

[1] Generate Always = Generates RTCP packets during
active and inactive (e.g., during call hold) RTP periods
(i.e., media is 'a=recvonly' or 'a=inactive' in the INVITE
SDP).

[2] Generate only if RTP Active = Generates RTCP
packets only during active RTP periods. In other words,
the device does not generate RTCP when there is no
RTP traffic (such as when a call is on hold).
Note: The corresponding global parameter is
SBCRTCPMode.
Enables the on-demand jitter buffer for SBC calls. This jitter
buffer can be used when other functionality such as voice
transcoding are not done on the call. This jitter buffer is
useful when incoming packets are received at inconsistent
intervals (i.e., packet delay variation). The jitter buffer stores
the packets and sends them out at a constant rate
(according to the coder's settings).

[0] Disable (default)

[1] Enable
Notes:

The jitter buffer parameters, 'Dynamic Jitter Buffer
Minimum Delay' (DJBufMinDelay) and 'Dynamic Jitter
Buffer Optimization Factor' (DJBufOptFactor) can be
used to configure minimum packet delay only when
transcoding is employed.

This functionality may require DSP resources. For more
information, contact your AudioCodes sales
representative.
323
19. Coders and Profiles
Description
Mediant 500 E-SBC