AudioCodes Mediant 500 E-SBC, User Manual

Page: 393 / 920

User's Manual 24. Routing
Version 6.8 393 Mediant 500 E-SBC
Parameter Description
The routing rule is not used if any of the following is displayed:

"n/a" = The destination IP Group is unavailable

"No Connectivity" = No connection with the destination (no
response to the SIP OPTIONS).

"QoS Low" = Poor Quality of Service (QoS) of the destination.

"DNS Error" = No DNS resolution. This status is applicable only
when a domain name is used (instead of an IP address).

"Unavailable" = The destination is unreachable due to
networking issues.
Web/EMS: Charge Code
CLI: charge-code
[PREFIX_MeteringCode]
Assigns a Charge Code to the routing rule. To configure Charge
Codes, see ''Configuring Charge Codes Table'' on page
438 .
Note: This parameter is applicable only to E1 Euro ISDN trunks.
Cost Group ID
CLI: cost-group-id
[PREFIX_CostGroup]
Assigns a Cost Group with the routing rule for determining the cost
of the call. To configure Cost Groups, see ''Configuring Cost
Groups'' on page
229 .
Forking Group
CLI: forking-group
[PREFIX_ForkingGroup]
Defines a forking group ID for the routing rule. This enables forking
of incoming Tel calls to multiple IP destinations. The device sends
simultaneous INVITE messages and handles multiple SIP dialogs
until one of the calls is answered. When a call is answered, the
other calls are dropped.
Each Forking Group can contain up to 10 members. In other
words, up to 10 routing rules can be configured with the same
Forking Group number.
If all matched routing rules belong to the same Forking Group
number, the device sends an INVITE to all the destinations
belonging to this group and according to the following logic:

If matched routing rules belong to different Forking Groups, the
device sends the call to the Forking Group of the first matched
routing rule. If the call cannot be established with any of the
destinations associated with this Forking Group and alternative
routing is enabled, the device forks the call to the Forking
Group of the next matched routing rules as long as the Forking
Group is defined with a
higher number than the previous
Forking Group. For example:

Table index entries 1 and 2 are defined with Forking Group "1",
and index entries 3 and 4 with Forking Group "2": The device
first sends the call according to index entries 1 and 2, and if
unavailable and alternative routing is enabled, sends the call
according to index entries 3 and 4.

Table index entry 1 is defined with Forking Group "2", and
index entries 2, 3, and 4 with Forking Group "1": The device
sends the call according to index entry 1 only and ignores the
other index entries even if the destination is unavailable and
alternative routing is enabled. This is because the subsequent
index entries are defined with a Forking Group number that is
lower than that of index entry 1.

Table index entry 1 is defined with Forking Group "1", index
entry 2 with Forking Group "2", and index entries 3 and 4 with
Forking Group "1": The device first sends the call according to
index entries 1, 3, and 4 (all belonging to Forking Group "1"),
and if the destination is unavailable and alternative routing is
enabled, the device sends the call according to index entry 2.

Table index entry 1 is defined with Forking Group "1", index