AudioCodes Mediant 500L MSBR

User's Manual 20. Control Network
Version 6.8 295 Mediant 500L MSBR
Parameter Description
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 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
634). This is
applicable only to User-type IP Groups.

Authenticates SIP severs. This is applicable only to Server-
type IP Groups.
Authentication Method List
CLI: 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 this parameter is not defined (i.e., empty
value), no methods are challenged.
The default value is null. Multiple entries are separated by a
backslash "\", for example, INVITE\REGISTER.
Note: This parameter is applicable only if the 'Authentication Mode'
parameter is set to SBC as Server [2].
SBC Client Forking Mode
CLI: enable-sbc-client-forking
[IPGroup_EnableSBCClientFork
ing]
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 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.
 [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.
Source URI Input
CLI: src-uri-input
[IPGroup_SourceUriInput]
Defines the SIP header in the incoming INVITE that is used for call
matching characteristics based on source URIs.
 [-1] Not Configured (default)
 [0] From
 [1] To
 [2] Request-URI
 [3] P-Asserted - First Header
 [4] P-Asserted - Second Header
 [5] P-Preferred