AudioCodes Mediant 500 E-SBC, User Manual

Page: 488 / 920

User's Manual 488 Document #: LTRT-10437
Mediant 500 E-SBC
28.5.3 Configuring SBC IP-to-IP Routing
The IP-to-IP Routing table lets you configure up to 500 SBC IP-to-IP routing rules. An IP-
to-IP routing rule routes received SIP dialog messages (e.g., INVITE) to an IP destination.
Configuration of IP-to-IP routing rules includes two areas:

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.
You can configure the IP-to-IP routing rule to send the call to any of the following IP
destinations:

According to registered user Contact listed in the device's database (only for User-
type IP Groups).

IP Group - the destination is the address configured for the Proxy Set associated with
the IP Group (allows redundancy/load balancing).

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.

According to result of an ENUM query.

Hunt Group - used for call survivability of call centers (see ''Call Survivability for Call
Centers'' on page
466 ).

IP address according to a specified Dial Plan index listed in the loaded Dial Plan file.

According to result of LDAP query (for more information on LDAP-based routing, see
''Routing Based on LDAP Active Directory Queries'' on page
197 ).
The IP-to-IP routing rule can also send the IP call to the Tel side (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.