Configuring Inbound Ip Routing Table - AudioCodes Mediant 1000B User Manual

Analog & digital voip media gateway enterprise session border controller gateway & e-sbc
Hide thumbs Also See for Mediant 1000B:
Table of Contents

Advertisement

Parameter
24.3

Configuring Inbound IP Routing Table

The Inbound IP Routing table lets you configure up to 120 inbound call routing rules:
For IP-to-IP routing: The table is used to identify an incoming call as an IP-to-IP call
and subsequently, to assign the call to an IP Group, referred to as a source IP Group.
These IP-to-IP calls can later be routed to an outbound destination IP Group (see
Configuring Outbound IP Routing Table on page 383).
For IP-to-Tel routing: This table is used to route incoming IP calls to Trunk Groups.
The specific channel pertaining to the Trunk Group to which the call is routed is
determined according to the Trunk Group's channel selection mode. The channel
selection mode can be defined per Trunk Group (see ''Configuring Trunk Group
Settings'' on page 353) or for all Trunk Groups using the global parameter
ChannelSelectMode.
The Inbound IP Routing table provides two configuration areas:
Matching characteristics of incoming IP call, for example, prefix of destination number.
Operation (destination), for example, sends to a specific Trunk Group.
User's Manual
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 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.
Notes:
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 (simultaneously) the INVITE messages 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,
use 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.
392
Mediant 1000B Gateway & SBC
Description
Document #: LTRT-27034

Advertisement

Table of Contents
loading

Table of Contents