![Dinstar SBC1000 Скачать руководство пользователя страница 51](http://html1.mh-extra.com/html/dinstar/sbc1000/sbc1000_user-manual_2505876051.webp)
3 Configurations on Web Interface
SBC1000 Session Border Controller
Copyright©2011-2018 Dinstar
45
as ‘ended’, and then will be disconnected.
If ‘Require’ is selected, the callee side of a call passing through the core 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.
Mini
Session
Expires
The minimum session duration which 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 device does not support 100rel, it
will automatically reject the INVITE request with 420; if the peer device
supports 100rel, it will send the
PRACK
request to acknowledge the response.
From Header
It can be ‘Local Domain’ or ‘Peer Domain’.
‘Local Domain’ is the default value.
Remote
media
send addresses
Lock: when the peer device works at public network, media address carried in SDP
(Session Description Protocol) message is locked; when the peer device works at private
network, the address that sends 30 messages continuously are locked.
Unlock: remote address sending media messages is not locked.
Remote
media
receive address
refresh
If this parameter is enabled, the remote address receiving media messages will be
refreshed.
Peer Signaling
IP
Lock: when a calling account is successfully registered, the core SIP trunk only receives
those calls from the registered address of the caller.
Caller Number
Field
User: the USER field of FROM header of INVITE message is extracted as caller
number
Display: the DISPLAY field of FROM header of INVITE message is extracted as caller
number
Callee Number
Field
User: the USER field of TO header of INVITE message is extracted as callee number
;
Display: the DISPLAY field of TO header of INVITE message is extracted as callee
number
;
Request-uri: the USER NUMBER in REQUEST-URI of INVITE message is extracted