From: Rick (ccie_2003@hotmail.com)
Date: Sun Jan 12 2003 - 18:44:44 GMT-3
Rouing VOIP and Data Packets over different VCs
Can someone please clarify that the below is common practice of just blocking
routes over the
VC to separate voice and data onto different VCs? Also, maybe someone could
add to this by sharing a different way.
Thanks,
Rick
page 264-265 in Integrating voice and data networks.*****
1. allocate a block of IP address for just VOIP. You can assign these address
to loopbacks for VOIP
endpoints. You can assign a single one of these addresses to a loopback
address for the VOIP gateway.
2.You now have a concise way to refer to all VOIP traffic flows using only IP
address info, which
enables a standard IP routing protocol to distinguish VOIP data packets.
To capitalize on this distinction, you need to create a two simple IP
access-lists that can be
reused on every router. The 1st list indentifys only the VOIP address, and the
2nd list indentifies
all other address. Using the address block created for VOIP address in the
preceding paragragh,
you access lists would look like this:
access-list 1 permit 192.168.254.0 0.0.0.255
access-list 2 deny 192.168.254.0 0.0.0.255
access-list 2 permit any
To steer all VOIP traffic to a voice VC, simply apply access-list 1 as an
inbound route filter
on the voice VC, and apply access-list 2 an inbound route filter on the data
VC. For both EIGRP
and OSPF, you can configure the following:
distribute-list 1 in serial 1/0:0.1
distribute-list 2 in serial 1/0:0.2
You may need a floating static route to point the voice traffic to a different
VC when the voice
vc fails
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:47 GMT-3