AudioCodes Mediant 3000, User Manual

Page: 238 / 872

User's Manual 238 Document #: LTRT-89729
Mediant 3000
Parameter Description
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].
SBC Client Forking
Mode
CLI: enable-sbc-client-
forking
[IPGroup_EnableSBCCl
ientForking]
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.
16.4 Configuring Proxy Sets Table
The Proxy Sets Table page allows you to define Proxy Sets . A Proxy Set is a group of
Proxy servers defined by IP address or fully qualified domain name (FQDN). You can
define up to 32 Proxy Sets, each with up to five Proxy server addresses. For each Proxy
server address you can define the transport type (i.e., UDP, TCP, or TLS). In addition,
Proxy load balancing and redundancy mechanisms can be applied per Proxy Set if it
contains more than one Proxy address.
Proxy Sets can later be assigned to Server-type IP Groups (see 'Configuring IP Groups' on
page
230 ). When the device sends an INVITE message to an IP Group, it is sent to the IP
address or domain name defined for the Proxy Set that is associated with the IP Group. In
other words, the Proxy Set represents the
destination of the call. Typically, for IP-to-IP call
routing, at least two Proxy Sets are defined for call destination – one for each leg (IP
Group) of the call (i.e., both directions). For example, one Proxy Set for the Internet
Telephony Service provider (ITSP) interfacing with one 'leg' of the device and another
Proxy Set for the second SIP entity (e.g., ITSP) interfacing with the other 'leg' of the device.
Notes:
•
Proxy Sets can be assigned only to Server-type IP Groups.
•
To enable classification of IP Groups according to Proxy Set ID, in the IP
Group table, set the 'Classify By Proxy Set' parameter to Enable.
•
The Proxy Set table can also be configured using two complementary
tables:
- Proxy Set ID with IP addresses: Table ini file parameter, ProxyIP.
- Attributes for the Proxy Set: Table ini file parameter, ProxySet.