AudioCodes MediaPack MP-11 Series User Manual

Version 7.2 657 Mediant 1000B Gateway & E-SBC
User's Manual 33. Routing SBC
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.
Note: Configure stricter rules higher up in the table than less strict rules to ensure the
desired rule is used to route the call. Strict
refers to the number of matching
characteristics configured for the rule. For example, a rule configured with source host
name and source IP Group as matching characteristics is stricter than a rule
configured with only source host name. If the rule configured with only source host
name appears higher up in the table, the device ("erroneously") uses the rule to route
calls matching this source host name (even if they also match the rule appearing
lower down in the table configured with the source IP Group as well).
You can route incoming SIP dialog messages (e.g., INVITE) to any of the following 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 ''Configuring Call
Survivability for Call Centers'' on page
711).

According to result of LDAP query (for more information on LDAP-based routing, see
''Routing Based on LDAP Active Directory Queries'' on page
229).

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
269.

Tel destination (i.e., Gateway call). The rule redirects the call to the IP-to-Tel 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 IP-to-Tel
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.

AudioCodes MediaPack MP-11 Series Specifications

General

Brand	AudioCodes
Model	MediaPack MP-11 Series
Category	Gateway
Language	English