AudioCodes Mediant 3000 User Manual page 504

Parameter
Cost Group
[PREFIX_CostGroup]
Charge Code
[PREFIX_MeteringC
ode]
Status Tab
Connectivity Status
User's Manual
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.
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 (None).
To configure Cost Groups, see ''Configuring Cost Groups'' on page 275.
Note: To implement LCR and its Cost Groups, you must enable LCR

To implement LCR and its Cost Groups, the Gateway Routing Policy must
be enabled for LCR (see ''Configuring a Gateway Routing Policy Rule'' on
page 510). 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.
Assigns a Charge Code to the routing rule for generating metering pulses
(Advice of Charge).
By default, no value is defined (None).
To configure Charge Codes, see ''Configuring Charge Codes'' on page 539.
Note: The parameter is applicable only to E1 Euro ISDN trunks.
(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.
For IP Groups, the status indicates the connectivity with the SIP proxy
server's address configured for the Proxy Set that is associated with the IP
Group. For the status to be displayed, the Proxy Keep-Alive feature, which
monitors the connectivity with proxy servers per Proxy Set, must be enabled
for the Proxy Set (see ''Configuring Proxy Sets'' on page 355). If a Proxy Set
is configured with multiple proxies for redundancy, the status may change
according to the proxy server with which the device attempts to verify
connectivity. For example, if there is no response from the first configured
proxy address, the status displays "No Connectivity". However, if there is a
response from the next proxy server in the list, the status changes to "OK".
If there is connectivity with the destination, the field displays "OK" and the
device uses the routing rule if required. The routing rule is not used if any of
Description
504
Mediant 3000
Document #: LTRT-89730