Configuring policy-based routing
Applications
The most common application for policy-based routing is to provide for separate routing of voice
and data traffic. It can also be used as a means to provide backup routes for defined traffic
types.
Separate routing of voice and data traffic
Although there are many possible applications for policy-based routing, the most common
application is to create separate routing for voice and data traffic.
For example, the application shown in
packets (DSCP = 34, 41), VoIP Bearer RESV packets (DSCP = 43, 44), and VoIP Bearer
packets (DSCP = 46). Policy-based routing sends these packets over the T1 WAN line, and
sends other packets over the Internet. This saves bandwidth on the more expensive Serial
interface.
Figure 54: Policy-based routing – Voice/Data division by DSCP
Backup
You can utilize policy-based routing to define backup routes for defined classes of traffic. If the
first route on the next hop list fails, the packets are routed to a subsequent hop. When
necessary, you can use the NULL interface to drop packets when the primary next hop fails. For
example, voice packets are usually sent over a WAN line, and not the Internet. You can
configure a PBR list to drop voice packets when the WAN line is down.
620 Administration for the Avaya G450 Media Gateway
Figure 54
uses the DSCP field to identify VoIP control