CHAPTER25 Routing
Mediant 1000 Gateway & E-SBC | User's Manual
■ Routing to an Alternative Trunk Group: If the device sends the IP call to the Tel destination
and a subsequent call release reason (cause) code (e.g., 17 for User Busy) is received from the
Tel side, and you have configured this release 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 in the table. Alternative routing rules must be
configured in table rows (indices) 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 alternative routing rules with identical matching
characteristics (e.g., destination prefix number) to the "main" routing rule, but assigned with
different destinations (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.
■ 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.
■ Routing to an Alternative Physical FXO Port or Trunk within Same Trunk Group: The device
can re-route an IP-to-Tel call to a different physical FXO port or trunk if the destined FXO port or
trunk within the same Trunk Group is out of service (e.g., physically disconnected). When the
physical FXO port or trunk is disconnected, the device sends the SNMP trap, GWAPP_
TRAP_BUSYOUT_LINK notifying of the out-of-service state for the specific FXO line or trunk
number. When the FXO port or physical trunk is physically reconnected, this trap is sent
notifying of the back-to-service state.
● Instead of using the table for IP-to-Tel routing, you can employ a third-party Routing
server to handle the routing decisions. For more information, see Centralized Third-
Party Routing Server.
● You can configure up to three alternative routing rules per "main" routing rule in the
table.
● If your deployment includes calls of many different called (source) and/or calling
(destination) numbers that need to be routed to the same destination, you can
employ user-defined prefix tags to represent these numbers. Thus, instead of
configuring many routing rules, you need to configure only one routing rule using the
prefix tag as the source and destination number matching characteristics, and a
destination for the calls. For more information on prefix tags, see Dial Plan Prefix
Tags for IP-to-Tel Routing.
● By default, the device applies destination telephone number manipulation (if
configured) only after processing the routing rule. You can change this and apply
number manipulation before processing the routing rule (see the RouteModeIP2Tel
parameter). To configure number manipulation, see Configuring Source/Destination
Number Manipulation.
The following procedure describes how to configure IP-to-Tel routing rules through the Web
interface. You can also configure it through ini file [PSTNPrefix] or CLI (configure voip >
gateway routing ip2tel-routing).
➢ To configure IP-to-Tel routing rules:
1. Open the IP-to-Tel Routing table (Setup menu > Signaling & Media tab > Gateway folder >
Routing > IP > Tel Routing).
2. Click New; the following dialog box appears:
- 594 -
To Next Page
Loading...
Need help?
General
