Parameter Description
Registration Mode
CLI: registration-mode
[IPGroup_RegistrationM
ode]
Defines the registration mode for the IP Group:
[0] User initiates registrations (default)
[1] SBC initiate registrations = Used when the device serves as a
client (e.g., with an IP PBX). This functions only with User Info file.
[2] No registrations needed = The device adds users to its database
in active state.
Authentication Mode
CLI: authentication-mode
[IPGroup_Authentication
Mode]
Defines the authentication mode.
[0] User Authenticates = (Default) The device does not handle the
authentication, but simply passes the authentication messages
between the SIP user agents.
[1] SBC as client = The device authenticates as a client. It receives
the 401/407 response from the proxy requesting for authentication.
The device sends the proxy the authorization credentials (i.e., user
name and password) according to one of the following: 1) account
defined in the Account table (only if authenticating Server-type IP
Group), 2) global username and password parameters (only if
authenticating Server-type IP Group), 3) User Information file, or 4)
sends request to users requesting credentials (only if authenticating
User-type IP Group).
[2] SBC as Server = The device authenticates as a server (using the
User Information file).
Authentication Method
List
CLI: authentication-
method-list
[IPGroup_MethodList]
Defines SIP methods that the device must challenge. Multiple entries are
separated by the backslash "\". If you set this parameter to an empty
value, no methods are challenged.
The default value is "INVITE\REGISTER".
Note: This parameter is applicable only if the 'Authentication Mode'
parameter is set to SBC as Server [2].
Enable SBC Client
Forking Mode
CLI: enable-sbc-client-
forking
[IPGroup_EnableSBCCli
entForking]
Defines call forking of INVITE messages to up to five separate SIP
outgoing legs for User-type IP Groups. This occurs if multiple contacts
are registered under the same AoR in the device's registration database.
[0] Sequential = (Default) Sequentially sends the INVITE to each
contact. If there is no answer from the first contact, it sends the
contact answers, the call fails or is routed to an alternative
destination, if configured.
[1] Parallel = Sends the INVITE simultaneously to all contacts. The
call is established with the first contact that answers.
[2] Sequential Available Only = Sequentially sends the INVITE only to
available contacts (i.e., not busy). If there is no answer from the first
available contact, it sends the INVITE to the second contact, and so
on until a contact answers. If no contact answers, the call fails or is
routed to an alternative destination, if configured.
Note: The device can also fork INVITE messages received for a
Request-URI of a specific contact (user) registered in the database to all
other users located under the same AoR as the specific contact. This is
configured using the SBCSendInviteToAllContacts parameter..
To Next Page
Loading...
