62
SBC session border controllers
opposite device for the duration of the timeout and the last packet was not a silence suppression packet,
the call will be rejected;
–
RTP-loss timeout after Silence-Suppression indication (multiplier) —
RTP packet timeout for the silence
suppression option utilization. Permitted value range is from 1 to 30. Coefficient is a multiplier and
determines how many times the value of this timeout is greater than the "
RTP-loss timeout"
. If there are no
RTP packets coming from the opposite device for the duration of the timeout and the last packet was a
silence suppression packet, the call will be rejected;
–
RTP-loss timeout on hold (sendonly, inactive) (multiplier) —
RTP packets timeout for SBC communicating
with the SIP server in modes where the voice frequency path is transmitting only or is inactive. Permitted
value range is from 1 to 30. Coefficient is a multiplier and determines how many times the value of this
timeout is greater than the "
RTP-loss timeout"
. If there are no RTP packets coming from the opposite device
for the duration of the timeout and the voice frequency path is transmitting only or inactive, the call will be
rejected;
–
RTCP control timeout, s —
the voice frequency path monitor function, takes on values from 10-300 c. Defines
the period of time, during which the opposite side will wait for RTCP protocol packets. If no packets are
received within a given time period, if at least one RTCP packet has previously been sent by the opposite
party, the established connection is terminated;
–
Verify IP:Port for RTP source —
when enabled, SBC ensures that a media stream from the opposite side is
routed exactly from the IP and port specified in SDP. Otherwise the media stream will be rejected;
–
Requested Session Expires value (RFC 4028), s
— when checked, SIP session timers are supported (RFC 4028).
Session update is supported by transmitting re-INVITE requests during the session. This parameter defines
the time period, in seconds, after which a session will be forcibly terminated if the session is not updated in
time (from 90 to 64800 s, the recommended value is 1800 s);
The RTP, RTCP packet waiting control and the use of RFC 4028 are designed to ensure that
conversational sessions established via an SBC do not hang up if there are problems with packet
transmission on the operator's network. All inactive sessions will be closed after appropriate
timeouts.
–
SIP domain
— the domain name with which the SBC trunk is registered to the registration server (for UAC
registration type), or the domain name with which the opposite device is authenticated to SBC via the trunk
(for UAS registration type);
–
NAT subscribers —
set a flag if it is necessary to connect subscribers who are in a private network (behind
NAT). This setting also allows SIP messages to be sent symmetrically (to the port from which the request
was received) if the client did not use the RPORT parameter in the initiating request;
–
NAT keep-alive timeout, sec —
storage time of port matching for signalling traffic. Also limits the 'expires'
parameter for SIP subscribers registration;
–
Disable SDP mode change to pin NAT for Ringback
—
by default, starting from software version 1.9.2, SBC
will declare sendrecv mode in SDP, even if the opposite side has accepted sendonly or recvonly, to ensure
correct preanswering media connection (PDA, voice messages) for clients behind NAT. The option allows
disabling this behaviour and announce to the SDP what the opposite side has stated;
–
Minimal registration interval, sec
— the minimum registration time allowed for the subscriber. Can take
values from 60 to 65535 seconds. Note that values less than 120s can affect performance.
