AudioCodes Mediant 3000 User Manual page 604


Rule: Defines the characteristics of the incoming SIP dialog message (e.g., IP Group
from which the message is received).

Action: Defines the action that is done if the incoming call matches the characteristics
of the rule (i.e., routes the call to the specified destination).
The device searches the table from top to bottom for the first rule that matches the
characteristics of the incoming call. If it finds a matching rule, it sends the call to the
destination configured for that rule. If it doesn't find a matching rule, it rejects the call.
An IP-to-IP routing rule routes received SIP dialog messages (e.g., INVITE) to any of the
following configurable IP destinations:

According to registered user Contact listed in the device's registration database (only
for User-type IP Groups).

IP Group - the destination is the address configured for the Proxy Set associated with
the IP Group.

IP address in dotted-decimal notation or FQDN. Routing to a host name can be
resolved using NAPTR/SRV/A-Record.

Request-URI of incoming SIP dialog-initiating requests.

Any registered user in the registration database. If the Request-URI of the incoming
INVITE exists in the database, the call is sent to the corresponding contact address
specified in the database.

According to result of an ENUM query.

Hunt Group - used for call survivability of call centers (see ''Call Survivability for Call
Centers'' on page 649).

According to result of LDAP query (for more information on LDAP-based routing, see
''Routing Based on LDAP Active Directory Queries'' on page 246).

Third-party routing server, which determines the destination (next hop) of the call (IP
Group). The IP Group represents the next device in the routing path to the final
destination. For more information, see ''Centralized Third-Party Routing Server'' on
page 284.

Tel destination (i.e., Gateway call). The rule redirects the call to the Inbound IP
Routing table where the device searches for a matching IP-to-Tel routing rule. This
feature can also be done for alternative routing. If an IP-to-IP routing rule fails and it is
configured with a "Gateway" routing rule as an alternative route, the device uses the
Inbound IP Routing table to send the call to the Tel. The device identifies (internally)
calls re-directed for alternative Gateway routing, by appending a user-defined string to
the prefix destination Request-URI user part (by default, "acgateway-<prefix
destination>", for example, acgateway-200). The device removes this prefix before
sending it to the Tel side. To configure this prefix string, use the GWDirectRoutePrefix
ini file parameter.
User's Manual 604
Mediant 3000
Document #: LTRT-89730