Dinstar SBC1000, User Manual

Page: 46 / 71

3 Configurations on Web Interface
SBC1000 Session Border Controller
Copyright©2011-2018 Dinstar
40
Registration
When ‘Server IP Type’ is configured as ‘Static’, registration will be displayed.
If registration is enabled, the access IP trunk will be registered to the configured peer
address and port, and the status of the access SIP trunk will become ‘Ture’. Otherwise,
the status is ‘False’. For the status of access SIP trunk, please refer to 3.3.3 .
Keepalive
If ‘Keepalive’ is disabled, the system will not detect whether the access SIP trunk’s peer
device (generally it is the access network server) is reachable or not.
If it is enabled, option message will be sent to detect the access network server is
reachable. If response is received, it means the peer device is reachable, and the status
of the access SIP trunk is ‘True’. Otherwise, the status will be ‘False’. For the status of
access SIP trunk, please refer to 3.3.3 .
Times of No
Response
The maximum number of timeouts for receiving response from the peer device after
option messages are sent out.
Interval The interval to send option message to the peer device
SIP Session
Timer
Session timer is a mechanism to keep activating sessions.
If ‘Supported’ is selected, SBC1000 will send ‘reinvite’ messages to keep activating
sessions within the configured duration.
If no messages are detected within the configured duration, sessions will be considered
as ‘ended’, and then will be disconnected.
If ‘Require’ is selected, the callee side of a call passing through the access SIP trunk also
needs to support session timer.
Session Expires
Configure the duration of the session. During the duration, SBC1000 will send ‘reinvite’
messages to keep activating the session.
Min. Session
Timeout
Minimum session duration is used to negotiate with the session timer on the callee side
PRACK
PRACK (Provisional Response ACKnowledgement): provide reliable provisional
response messages.
Disable: INVITE request and 1xx response sent out by SBC1000 will not
include 100rel tag by default;
Support: INVITE
request and 1xx response sent out by SBC1000 will include
100rel tag in Supported header;
Require:
INVITE request and 1xx response sent out by SBC1000 will include
100rel tag in Require header; if the peer does not support 100rel, it will
automatically reject INVITE request with 420; if the peer supports 100rel. it
will send PRACK request to acknowledge the response.
From Header
It can be ‘Local Domain’ or ‘Peer Domain’.
‘Local Domain’ is the default value.
Peer Media Lock: when the peer device works at public network, media address carried in SDP