Configuring Sbc Ip-To-Ip Routing - AudioCodes Mediant 4000 SBC User Manual

User's Manual
Index
2
In the example, a match exists only for Classification Rule #1. This is because the source
(1111) and destination (2000) username prefixes match those in the INVITE's P-Called-
Party-ID
"<sip:2000@10.10.10.10.10>"), respectively. These SIP headers were determined in IP
Group 2.
25.2

Configuring SBC IP-to-IP Routing

The IP-to-IP Routing table lets you configure up to 3,750 SBC IP-to-IP routing rules.
Configuration of IP-to-IP routing rules includes two areas:

Match: 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.
Note:
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 Group Set - the destination can be based on multiple IP Groups for load balancing,
where each call may be sent to a different IP Group within the IP Group Set
depending on the IP Group Set's definition.

Routing tag - the device sends the call to an IP Group (or IP Group Set) based on a
destination Dial Plan tag that corresponds to the destination (called) prefix number.

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.
Version 7.2
Source URI Input
P-Called-Party-ID
header (i..e., "<sip:1111@10.33.38.1>")
Configure stricter rules higher up in the table than less strict rules to ensure the
499
25. Routing SBC
Destination URI Input
Route
and Route header
Mediant 4000 SBC
(i.e.,