AudioCodes Mediant 1000B User Manual page 647

User's Manual
The LCR feature can also be employed with call forking. The device calculates a
maximum call cost for each Forking group and routes the call to the Forking group
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 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 tags to represent these numbers. Thus,
instead of configuring many routing rules, you need to configure only one routing rule
using the tag as the source and destination number matching characteristics, and a
destination for the calls. For more information on prefix tags, see Configuring Dial
Plans on page 673.
Note:
The following procedure describes how to configure IP-to-IP routing rules through the Web
interface. You can also configure it through ini file (IP2IPRouting) or CLI (configure voip >
sbc routing ip2ip-routing).

To configure an IP-to-IP routing rule:
1. Open the IP-to-IP Routing table (Configuration tab > VoIP menu > SBC > Routing
SBC > IP-to-IP Routing Table).
Version 7.0
Call forking is not applicable to LDAP-based IP-to-IP routing rules.
647 Mediant 1000B Gateway and E- SBC
34. Routing SBC