QoS on IPSec VPN Tunnel for VOice Traffic - Help Needed
I have two sites one with a 1811 and the other with an 831. Both sites have an internet connection and there is a VPN Tunnel between them.
I want to implement QoS on the Tunnel interface as I want to prioritize voice traffic through the Tunnel. There is a Linksys VoIP system running through the tunnel.
Signaling Packets are marked with 7 Hex and RTP packets b0.
I am not very confident with QoS configuration so I used SDM to create the policy maps and classes for me, giving 70% bandwidth for voice. I then used the qos pre-classify command on the tunnel interface. Connectivity to the internet is through a Dialer Interface so the service policy is applied to this interface. Note that I cannot apply the policy directly on the tunnel interface as it does not support header compression.
I am attaching a partial config of what I have. Can someone please point out if my config is right or not and how can I check if it is working as it should be?
Re: QoS on IPSec VPN Tunnel for VOice Traffic - Help Needed
I want to enable QoS as I tried to disable all other traffic except the voice on the tunnel and voice quality was fine, so I would presume that the ISP supports QoS.
The bits I was mentioning are Diffserv Bits. Do I need to make use of these?
Also I tried to configure my class maps with the parent / child policy-map hierarchy but when I tried to put it on the fastethernet inteface connected to the DSL modem, I had an error stating that it does not support Ip Header compression. Do I need to put the "service-policy output" command on the Dialer, on the Fast Ethernet or on the Tunnel interface?
Also I noticed that the 831 does not have a match protocol sip or rtp commands. I created and ACL which caps traffic from the VoIP Pabx to the VoIP gateway and used the match access-group . I think this will still work no, as all the traffic matching the ACL is all VoIP.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...