SBC session border controllers
57
Authentication settings
–
Login
— login to authenticate to the
upstream SIP server;
–
Password
— password to authenti-
cate to the upstream SIP server. Authentication data is only used to authorise requests generated by SBC itself,
e.g. re-INVITE requests generated by SBC when using RFC 4028 timer function, authentication on the interact-
ing server, registration on the interacting server (with UAC registration type), authentication of requests from
the interacting server (with UAS registration type).
SIP trunk Registration
–
Registration type
— this setting
specifies the direction of registration:
UAC —
in this case, SBC will
register on the cooperating
registration server via a trunk. If
there is no registration, the
destination will be considered unavailable and no calls will be sent to it (but they will always be
received);
UAS —
in this case, the device interacting over the trunk will register on SBC, provided that the
registration confirmation is received from the selected by
Rule set
server. SBC will also authenticate all
requests from the interacting server. The setting in the
Remote Address
field does not apply, the address
obtained in the contact during registration is used.
If there is no registration, the destination will be considered unavailable and no calls will be sent
from it (but they will always be received);
–
Expires, s
— update period for registration on the server (used for UAC registration type);
–
Username/Number
— name/number with which SBC trunk registers on the registration server (for UAC
registration type);
–
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 the SBC via the
trunk (for UAS registration type);
When enabled, the setting will disable built-in firewall rules for the SIP transport bound to the SIP
destination on which the option is enabled to ensure that redirects work correctly! If the transport
is used on other SIP destinations, built-in Firewall rules will also be disabled for them. It is
recommended to allocate a separate SIP transport for those SIP destinations from which redirects
are allowed to be processed, or restrict access manually if necessary (more details in section 4.1.8.5).