AudioCodes Mediant 3000, User Manual

Page: 232 / 872

User's Manual 232 Document #: LTRT-89729
Mediant 3000
Parameter Description
end) users.
Typically, this IP Group is configured with a Serving IP Group that
represents an IP-PBX, Application or Proxy server that serves this
User-type IP Group. Each SIP request sent by a user of this IP Group
is proxied to the Serving IP Group. For registrations, the device
updates its internal database with the AOR and contacts of the users.
Digest authentication using SIP 401/407 responses (if needed) is
performed by the Serving IP Group. The device forwards these
responses directly to the SIP users.
To route a call to a registered user, a rule must be configured in the
Outbound IP Routing Table or SBC IP-to-IP Routing table. The device
searches the dynamic database (by using the request URI) for an
entry that matches a registered AOR or Contact. Once an entry is
found, the IP destination is obtained from this entry, and a SIP
request is sent to the destination.
The device also supports NAT traversal for the SIP clients located
behind NAT. In this case, the device must be defined with a global IP
address.

[2] Gateway = This is applicable only to the SBC application in
scenarios where the device receives requests to and from a gateway
representing multiple users. This IP Group type is necessary as the
other IP Group types are not suitable:

The IP Group cannot be defined as a Server since its destination
address is unknown during configuration.

The IP Group cannot be defined as a User since the SIP Contact
header of the incoming REGISTER does not represent a specific
user. The Request-URI user part can change and therefore, the
device is unable to identify an already registered user and
therefore, adds an additional record to the database.
The IP address of the Gateway IP Group is obtained dynamically from
the host part of the Contact header in the REGISTER request
received from the IP Group. Therefore, routing to this IP Group is
possible only once a REGISTER request is received. If a REGISTER
refresh request arrives, the device updates the new location (i.e., IP
address) of the IP Group. If the REGISTER fails, no update is
performed. If an UN-REGISTER request arrives, the IP address
associated with the IP Group is deleted and therefore, no routing to
the IP Group is done.
Note: This field is applicable only to the SBC or IP-to-IP application.
Description
[IPGroup_Description]
Defines a brief description for the IP Group.
The valid value is a string of up to 29 characters. The default is an empty
field.
Proxy Set ID
[IPGroup_ProxySetId]
Assigns a Proxy Set ID to the IP Group. All INVITE messages destined
to this IP Group are sent to the IP address configured for the Proxy Set.
Notes:

Proxy Set ID 0 must not be used; this is the device's default Proxy.

The Proxy Set is applicable only to Server-type IP Groups.

The SRD configured for this Proxy Set in the Proxy Set table is
automatically assigned to this IP Group (see the 'SRD' field below).

To configure Proxy Sets, see 'Configuring Proxy Sets Table' on page
238 .
SIP Group Name
[IPGroup_SIPGroupNa
Defines the SIP Request-URI host name used in INVITE and REGISTER
messages sent to this IP Group, or the host name in the From header of