AudioCodes Mediant 800B MSBR User Manual page 405

Mediant 800B MSBR
Parameter
IP Profile ID
CLI: ip-profile-id
[PREFIX_ProfileId]
Status
Web/EMS: Charge Code
CLI: charge-code
[PREFIX_MeteringCode]
Cost Group ID
CLI: cost-group-id
[PREFIX_CostGroup]
Forking Group
CLI: forking-group
[PREFIX_ForkingGroup]
Version 6.8
SIP Interface.
To configure SRD's, see Configuring SRDs on page 264.
Assigns an IP Profile ID to this IP destination call. This allows you
to assign numerous configuration attributes (e.g., voice codes) per
routing rule. To configure IP Profiles, see ''Configuring IP Profiles''
on page 314.
(Read-only field) Displays the connectivity status of the routing
rule's IP destination. If there is connectivity with the destination,
this field displays "OK" and the device uses this routing rule if
required.
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.
Assigns a Charge Code to the routing rule. To configure Charge
Codes, see ''Configuring Charge Codes Table'' on page 470.
Note: This parameter is applicable only to FXS interfaces and E1
Euro ISDN trunks.
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 238.
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.
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
405
Description
Mediant 800B MSBR
28. Routing