AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 346 / 1248

User's Manual 346 Document #: LTRT-10375
Mediant 500 MSBR
REGISTER request and the response’s code appears in the
Alternative Routing Reasons table (see Configuring SIP Response
Codes for Alternative Routing Reasons onn page 690), "hot-swap" to
the other IP addresses of the Proxy Set is done until a success
response is received from one of the addresses. In the case of failed
REGISTER refresh requests from users that are already bound to a
registrar, no "hot-swap" occurs for that request; only for subsequent
refresh requests.

When using the User Info table (see SBC User Information for SBC
User Database on page 792), registrar "stickiness" is supported only
when the user initiates the REGISTER request. Therefore, you must
configure the 'Registration Mode' parameter of the IP Group (User-
type) to which the user belongs, to
User Initiates Registration .
Authentication Mode
authentication-mode
[IPGroup_AuthenticationM
ode]
Defines the authentication mode.

[0] User Authenticates = (Default) The device does not handle the
authentication, but simply forwards 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.,
username and password) according to one of the following:
1)Account configured in the Accounts 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). For more information on
Accounts, see Configuring Registration Accounts on page 363.

[2] SBC as Server = The device acts as an Authentication server:

Authenticates SIP clients, using the usernames and passwords in
the User Information table (see SBC User Information for SBC
User Database on page 792). This is applicable only to User-type
IP Groups.

Authenticates SIP servers. This is applicable only to Server-type
IP Groups.
Authentication Method List
authentication-method-list
[IPGroup_MethodList]
Defines SIP methods received from the IP Group that must be
challenged by the device when the device acts as an Authentication
server. If no methods are configured, the device doesn't challenge any
methods.
By default, no value is defined. To define multiple SIP methods, use the
backslash ( \ ) to separate each method (e.g., INVITE\REGISTER).
Note: The parameter is applicable only if the 'Authentication Mode'
parameter is set to SBC as Server [2].
Username
username
[IPGroup_Username]
Defines the shared username for authenticating the IP Group, when the
device acts as an Authentication server.
The valid value is a string of up to 51 characters. By default, no
username is defined.
Note:

The parameter is applicable only to Server-type IP Groups and when
the 'Authentication Mode' parameter is set to SBC as Server (i.e.,
authentication of servers).

To specify the SIP request types (e.g., INVITE) that must be
challenged by the device, use the 'Authentication Method List'
parameter.