Configuration Example - Avaya G250 Administration

Configuring WAN interfaces
are available to supply addressing in situations where you wish to run routing over your
network link without committing a subnet. For information on configuring dynamic IP
addressing, see
unnumbered IP, see
Object tracking can be used with the Loopback interface to provide an alternative method
●
for activating the Dialer interface when connectivity with the main office is lost. This is
useful in configurations where the WAN interface is not connected directly to the G250/
G350. Use object tracking to configure RTRs to verify connectivity with the main office. If
the RTR fails, the object tracker can be configured to change the status of the Loopback
interface to down. If the Dialer interface is configured as the backup for the Loopback
interface, the Dialer interface will automatically dial when connectivity fails. For more
information about object tracking, see
Note:
In a situation where the same modem is used for inbound Avaya Service calls
Note:
and outbound dial backup calls, only one call can be active at any time.
Note:
Refer to www.multitech.com for a listing of modem AT commands used to
Note:
configure the modem directly.
You must disable modem dial backup before configuring FIPS.
●

Configuration example

This example sets up a modem dial backup for the WAN link between a branch office and the
headquarters data center. The branch office is connected to the corporate network using a
G250. IP phone users in the branch office connect to an MGC located in the headquarters data
center, and there is an RAS located in the headquarters data center, with multiple phone lines
available for dial access. The primary WAN connection is a PPP link connected to the port
Serial 2/1. The dialer PPP session uses CHAP encryption. The corporate network is routed
using OSPF. An analog trunk connects the branch office to the PSTN for non-corporate bearer
traffic.
Figure 16 shows the network topology.
156 Administration for the Avaya G250 and Avaya G350 Media Gateways
Using dynamic local peer IP
Configuring unnumbered IP interfaces
on page 392. For information on configuring
on page 315.
Object tracking on page 171.