Configuring Inbound Ip Routing Table - AudioCodes Mediant 3000 User Manual

User's Manual
25.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 427).

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 393) or for all Trunk Groups using the global parameter
ChannelSelectMode.
Configuration of Inbound IP Routing routing rules includes two areas:

Rule: Defines the characteristics of the incoming IP call (e.g., IP Group from which the
call is received).

Action: Defines the action that is done if the incoming call matches the characteristics
of the rule (i.e., routes the call to the specified Tel/Trunk Group destination).
The device searches the table from top to bottom for the first rule that matches the
characteristics of the incoming call. If it finds a matching rule, it sends the call to the Tel
destination configured for that rule. If it doesn't find a matching rule, it rejects the call.
The device also supports alternative routing if the IP-to-Tel call cannot be routed to the
Trunk Group:

Routing to an Alternative Trunk Group: If a call release reason (cause) code (e.g.,
17 for User Busy) is received from the Tel side for a specific IP-to-Tel call and you
have configured this reason code in the Reasons for IP-to-Tel Alternative Routing
table, the device re-routes the call to an alternative Trunk Group if an alternative
routing rule has been configured. You must configure the alternative routing rules in
table rows (indices) that are located anywhere below the "main" routing rule. For
example, if you configure a "main" routing rule in Index 4, the alternative routing rule
can be configured in Index 6. In addition, you must configure the alternative routing
rules with identical matching characteristics (e.g., destination prefix number) to the
"main" routing rule, but assigned with different destinations (i.e., Trunk Groups). For
more information on IP-to-Tel alternative routing and for configuring call release
reasons for alternative routing, see ''Alternative Routing to Trunk upon Q.931 Call
Release Cause Code'' on page 448.

Routing to an IP Destination (i.e., Call Redirection): The device can re-route the
IP-to-Tel call to an alternative IP destination, using SIP 3xx responses. For more
information, see ''Alternative Routing to IP Destinations upon Busy Trunk'' on page
449.

Routing to an Alternative Physical Trunk Within the Same Trunk Group: The
device can re-route an IP-to-Tel call to a different physical trunk if the destined trunk
within the same Trunk Group is out of service (e.g., physically disconnected). When
the physical trunk is disconnected, the device sends the SNMP trap,
GWAPP_TRAP_BUSYOUT_LINK notifying of the out-of-service state for the specific
trunk number. When the physical trunk is physically reconnected, this trap is sent
notifying of the back-to-service state.
Version 6.8 437
25. Routing
Mediant 3000