AudioCodes Mediant 500 MSBR, User Manual

Page: 503 / 1248

Version 7.2 503 Mediant 500 MSBR
User's Manual 27. Routing
Parameter Description
is unavailable and alternative routing is enabled, the device sends the call
according to index entry 2 (Forking Group "3"). Even if index entry 2 is
unavailable and alternative routing is enabled, the device ignores index
entry 3 because it belongs to a Forking Group that is lower than index
entry 2.
Note:

To enable Tel-to-IP call forking, set the 'Tel2IP Call Forking Mode'
(
Tel2IPCallForkingMode ) parameter to Enable .

You can configure the device to immediately send the INVITE message to
the first member of the Forking Group (as in normal operation) and then
only after a user-defined interval, send the INVITE messages
simultaneously to the other members. If the device receives a SIP 4xx or
5xx in response to the first INVITE, it immediately sends INVITEs to all
the other members, regardless of the interval. To configure this feature,
see the ForkingDelayTimeForInvite ini file parameter.

You can implement Forking Groups when the destination is an LDAP
server or a domain name using DNS. In such scenarios, the INVITE is
sent to all the queried LDAP or resolved IP addresses, respectively. You
can also use LDAP routing rules with standard routing rules for Forking
Groups.

When the UseDifferentRTPportAfterHold parameter is enabled, every
forked call is sent with a different RTP port. Thus, ensure that the device
has sufficient available RTP ports for these forked calls.
Cost Group
cost-group-id
[PREFIX_CostGroup
]
Assigns a Cost Group to the routing rule for determining the cost of the call
(i.e., Least Cost Routing or LCR).
By default, no value is defined.
To configure Cost Groups, see Configuring Cost Groups on page 248.
Note: To implement LCR and its Cost Groups, you must enable LCR

To implement LCR and its Cost Groups, the Routing Policy must be
enabled for LCR (see Configuring a Gateway Routing Policy Rule on
page 509). If LCR is disabled, the device ignores the parameter.

The Routing Policy also determines whether matched routing rules that
are
not assigned Cost Groups are considered as a higher or lower cost
route compared to matching routing rules that are assigned Cost Groups.
For example, if the 'Default Call Cost' parameter in the Routing Policy is
configured to
Lowest Cost , even if the device locates matching routing
rules that are assigned Cost Groups, the first-matched routing rule without
an assigned Cost Group is considered as the lowest cost route and thus,
chosen as the preferred route.
Charge Code
charge-code
[PREFIX_MeteringC
ode]
Assigns a Charge Code to the routing rule for generating metering pulses
(Advice of Charge).
By default, no value is defined.
To configure Charge Codes, see Configuring Charge Codes on page 593.
Note: The parameter is applicable only to FXS and Euro ISDN PRI/BRI
trunks.
Status Tab
Connectivity Status (Read-only field) Displays the connectivity status of the routing rule's
destination. The destination can be an IP address or an IP Group, as
configured in the 'Destination IP Address' and 'Destination IP Group' fields
respectively.