56 SBC session border controllers
– 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 the media stream from the opposite side is
routed exactly from the IP and the port specified in the 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.
– Keep-alive timeout for alive server, sec (after previous OPTIONS-transaction finished) — the time interval after
which an OPTIONS control request will be sent to the SIP server if the previous OPTIONS request was con-
firmed;
– Keep-alive timeout for dead server, sec (after previous OPTIONS-transaction finished) — the time interval after
which an OPTIONS control request will be sent to the SIP server if the previous OPTIONS request was not con-
firmed;
– Input max CPS value — the number of calls per second that can be received by SIP Destination. The permissible
value range is from 0 to 100, 0 — option deactivation;
– Output max CPS value — the number of calls per second that can be sent by SIP Destination. The permissible
value range is from 0 to 100, 0 — option deactivation.
Ingress calls
– Rule set— apply the rule set created in the "Rule set" menu to the incoming signalling (more information in
section 4.1.3.5 Rule set);
– Respond to OPTIONS — when enabled, SBC will respond to OPTIONS on its own if the Rule in not present in the
Rule set responsible for sending OPTIONS.
Egress calls
– Convert RFC2833 Flash into SIP INFO — converts the Flash signal received using RFC 2833 method to a SIP INFO
application/hook-flash request and transmits it to the communicating channel;
– Allow redirection — allows 302 responses processing. When disabled, SBC will end the call when 302 response
is received from B. When enabled, SBC will process 302 responses as follows: after receiving a subscriber C
contact, SBC will try to send the call to him, notifying side A that the call has been redirected by 181 response.
If the contact contains the address of SBC itself, it will transparently route the 302 message to side A by
specifying the address of side A in the Contact field;
To Next Page
Loading...