AudioCodes Mediant 800B User Manual page 574

with the lowest cost. Thus, even if the call can successfully be routed to the main
routing rule, a different routing rule can be chosen (even an alternative route, if
configured) based on LCR. If routing to one Forking group fails, the device tries to
route the call to the Forking group with the next lowest cost (main or alternative route),
and so on. The prerequisite for this functionality is that the incoming call must
successfully match the input characteristics of the main routing rule.

Dial Plan Prefix Tags for Representing Source / Destination Numbers: If your
deployment includes calls of many different called (source URI user name) and/or
calling (destination URI user name) numbers that need to be routed to the same
destination, you can employ user-defined prefix tags to represent these numbers.
Thus, instead of configuring many routing rules, you need to configure only one
routing rule using the prefix tag as the source and destination number matching
characteristics, and a destination for the calls. For more information on prefix tags, see
''Dial Plan Prefix Tags for SBC IP-to-IP Routing'' on page 650.
Note: Call forking is not applicable to LDAP-based IP-to-IP routing rules.
The following procedure describes how to configure IP-to-IP routing rules in the Web
interface. You can also configure IP-to-IP routing rules using the table ini file parameter,
IP2IPRouting or CLI command, configure voip > sbc routing ip2ip-routing.

To configure an IP-to-IP routing rule:
1. Open the IP-to-IP Routing Table page (Configuration tab > VoIP menu > SBC >
Routing SBC > IP-to-IP Routing Table).
2. Click Add; the following dialog box appears:
Figure 29-9: IP-to-IP Routing Table - Add Record Dialog Box
3. Configure an IP-to-IP routing rule according to the parameters described in the table
below.
4. Click Submit, and then save ("burn") your settings to flash memory.
User's Manual
Mediant 800B Gateway and E-SBC
574 Document #: LTRT-10620