AudioCodes Mediant 500L - Page 535

Version 7.2 535 Mediant 500L Gateway & E-SBC
User's Manual 24. Routing

"unavailable":
• Digital interfaces: All trunks are busy or unavailable
• Analog interfaces: All FXS / FXO lines pertaining to a Trunk Group are busy or
unavailable
The following procedure describes how to configure Forward on Busy Trunks through the
Web interface. You can also configure it through ini file (ForwardOnBusyTrunkDest) or CLI
(configure voip > gateway routing fwd-on-bsy-trk-dst).
 To configure a Forward on Busy Trunk Destination rule:
1. Open the Forward on Busy Trunk Destination table (Setup menu > Signaling &
Media tab > Gateway folder > Routing > Forward on Busy Trunk Destination).
2. Click New; the following dialog box appears:
Figure 24-14: Forward on Busy Trunk Destination Table - Add Dialog Box
The figure above displays a configuration that forwards IP-to-Tel calls destined for
Trunk Group ID 1 to destination IP address 10.13.5.67 if conditions mentioned earlier
exist.
3. Configure a rule according to the parameters described in the table below.
4. Click Apply, and then reset the device with a save-to-flash for your settings to take
effect.
Table 24-10: Forward on Busy Trunk Destination Parameter Descriptions
Parameter Description
Index
[ForwardOnBusyTrunkDest_In
dex]
Defines an index number for the new table row.
Note: Each row must be configured with a unique index.
Trunk Group ID
trunk-group-id
[ForwardOnBusyTrunkDest_T
runkGroupId]
Defines the Trunk Group ID to which the IP call is destined to.
Forward Destination
forward-dst
[ForwardOnBusyTrunkDest_F
orwardDestination]
Defines the alternative IP destination for the call used if the Trunk
Group is busy or unavailable.
The valid value can be an IP address in dotted-decimal notation, an
FQDN, or a SIP Request-URI user name and host part (i.e.,
user@host). The following syntax can also be used:
host:port;transport=xxx (i.e., IP address, port and transport type).
Note:
 If you do not specify a port, the device uses UDP port 5060.
 When configured with a user@host, the original destination
number is replaced by the user part.