AudioCodes Mediant 1000B User Manual page 492

Media gateway & enterprise session border controller (e-sbc)
Hide thumbs Also See for Mediant 1000B:
Table of Contents

Advertisement

Parameter
IP Profile
ip-profile-id
[PREFIX_ProfileNam
e]
Call Setup Rules Set
ID
call-setup-
rules-set-id
[PREFIX_CallSetup
RulesSetId]
Forking Group
forking-group
[PREFIX_ForkingGr
oup]
User's Manual
[1] TCP
[2] TLS
Assigns an IP Profile to the routing rule in the outgoing direction. The IP
Profile allows you to assign various configuration attributes (e.g., voice
coder) per routing rule. To configure IP Profiles, see 'Configuring IP Profiles'
on page 385.
Assigns a Call Setup Rule Set ID to the routing rule. The device performs the
Call Setup rules of this Set ID if the incoming call matches the characteristics
of the routing rule. The device routes the call to the destination according to
the routing rule's configured action only after it has performed the Call Setup
rules.
By default, no value is defined.
For configuring Call Setup rules, see 'Configuring Call Setup Rules' on page
281.
Defines a Forking Group number 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.
By default, no value is defined.
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. 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 the
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 entry 2 with
Forking Group "3", index entry 3 with Forking Group "2", and index entry 4
with Forking Group "1": The device first sends the call according to index
entries 1 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 (Forking Group "3"). Even if index entry 2 is
Mediant 1000B Gateway and E- SBC
Description
492
Document #: LTRT-27044

Advertisement

Table of Contents
loading

Table of Contents