<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Cisco ASA QoS for VoIP Traffic</title>
	<atom:link href="http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/</link>
	<description>IP Networks Training and Tutorials</description>
	<lastBuildDate>Fri, 03 Feb 2012 16:50:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Cisco</title>
		<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/comment-page-1/#comment-1591</link>
		<dc:creator>Cisco</dc:creator>
		<pubDate>Tue, 28 Dec 2010 17:26:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkstraining.com/?p=325#comment-1591</guid>
		<description>Priority queue will only apply to an interface in &quot;outbound&quot; direction.

In your example above. Please indicate ASA-2 outside interface with a priority queue applied to it&#039;s outside interface matching traffic going from 192.168.2.0/24 to 192.168.1.0/24</description>
		<content:encoded><![CDATA[<p>Priority queue will only apply to an interface in &#8220;outbound&#8221; direction.</p>
<p>In your example above. Please indicate ASA-2 outside interface with a priority queue applied to it&#8217;s outside interface matching traffic going from 192.168.2.0/24 to 192.168.1.0/24</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlogAdmin</title>
		<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/comment-page-1/#comment-91</link>
		<dc:creator>BlogAdmin</dc:creator>
		<pubDate>Thu, 19 Nov 2009 18:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkstraining.com/?p=325#comment-91</guid>
		<description>fkento

Thanks for the comment. Usually the signaling control protocols (H323, SIP, and SCCP) use TCP ports for communication. H323 uses TCP 1720, SIP uses TCP port 5060 and the Cisco SCCP protocol uses TCP 2000. Sometimes I have seen devices using UDP also so yes you might be right that UDP should be configured also on the ACL in addition to TCP. For payload voice traffic, this is definitely UDP (Real Time Protocol-RTP).

Cheers</description>
		<content:encoded><![CDATA[<p>fkento</p>
<p>Thanks for the comment. Usually the signaling control protocols (H323, SIP, and SCCP) use TCP ports for communication. H323 uses TCP 1720, SIP uses TCP port 5060 and the Cisco SCCP protocol uses TCP 2000. Sometimes I have seen devices using UDP also so yes you might be right that UDP should be configured also on the ACL in addition to TCP. For payload voice traffic, this is definitely UDP (Real Time Protocol-RTP).</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fkento</title>
		<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/comment-page-1/#comment-90</link>
		<dc:creator>fkento</dc:creator>
		<pubDate>Thu, 19 Nov 2009 14:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkstraining.com/?p=325#comment-90</guid>
		<description>First of all, thanks for the great information on your site. It is very helpful. However, I just want to point out that I was having problems getting priority queuing to work so I called Cisco and they said priority queuing will not work unless you also implement traffic policing or shaping. Here is a good article that discusses both. http://tinyurl.com/yed7e6l

Also, your access list only matches tcp traffic and most VoIP traffic is udp so you&#039;re probably not matching any packets with the current ACL. I changed mine to udp and it&#039;s working now.

Thanks
Kent</description>
		<content:encoded><![CDATA[<p>First of all, thanks for the great information on your site. It is very helpful. However, I just want to point out that I was having problems getting priority queuing to work so I called Cisco and they said priority queuing will not work unless you also implement traffic policing or shaping. Here is a good article that discusses both. <a href="http://tinyurl.com/yed7e6l" rel="nofollow">http://tinyurl.com/yed7e6l</a></p>
<p>Also, your access list only matches tcp traffic and most VoIP traffic is udp so you&#8217;re probably not matching any packets with the current ACL. I changed mine to udp and it&#8217;s working now.</p>
<p>Thanks<br />
Kent</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlogAdmin</title>
		<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/comment-page-1/#comment-89</link>
		<dc:creator>BlogAdmin</dc:creator>
		<pubDate>Mon, 09 Nov 2009 06:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkstraining.com/?p=325#comment-89</guid>
		<description>Well guys the firewall I tested the above configuration on did not give me an error message. Maybe it depends on the software version. Anyway, my opinion is to forget about matching the DSCP EF value and use only the ACL matching. Since the ACL is very specific (i.e you match specific traffic with specific ports, h323,sip,2000) then you can be assured that you are only prioritizing voice traffic and nothing else. Also, matching on the DSCP value might not be a very reliable match since you depend on the voice source device which must set the DSCP value of the voice packets to EF.</description>
		<content:encoded><![CDATA[<p>Well guys the firewall I tested the above configuration on did not give me an error message. Maybe it depends on the software version. Anyway, my opinion is to forget about matching the DSCP EF value and use only the ACL matching. Since the ACL is very specific (i.e you match specific traffic with specific ports, h323,sip,2000) then you can be assured that you are only prioritizing voice traffic and nothing else. Also, matching on the DSCP value might not be a very reliable match since you depend on the voice source device which must set the DSCP value of the voice packets to EF.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fkento</title>
		<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/comment-page-1/#comment-88</link>
		<dc:creator>fkento</dc:creator>
		<pubDate>Sun, 08 Nov 2009 21:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkstraining.com/?p=325#comment-88</guid>
		<description>I too am having the same problem as Wesley. When I try to add the second match, I get this

ERROR: Multiple match commands are not supported except for the &#039;match tunnel-group or default-inspect-traffic&#039; command.

This seems to imply that you cannot have two match statements in a class-map. If that is true, how do you match traffic with Express Forwarding and the ACL?

Thanks for your help!</description>
		<content:encoded><![CDATA[<p>I too am having the same problem as Wesley. When I try to add the second match, I get this</p>
<p>ERROR: Multiple match commands are not supported except for the &#8216;match tunnel-group or default-inspect-traffic&#8217; command.</p>
<p>This seems to imply that you cannot have two match statements in a class-map. If that is true, how do you match traffic with Express Forwarding and the ACL?</p>
<p>Thanks for your help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlogAdmin</title>
		<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/comment-page-1/#comment-87</link>
		<dc:creator>BlogAdmin</dc:creator>
		<pubDate>Tue, 19 May 2009 13:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkstraining.com/?p=325#comment-87</guid>
		<description>First of all, for the access list match you must create the ACL first and then use it in the match statement of the class-map. For the dscp value match, this should work just as I show in the example. If you still have problems for matching the dscp value, just leave the ACL match only.

Cheers
Harris</description>
		<content:encoded><![CDATA[<p>First of all, for the access list match you must create the ACL first and then use it in the match statement of the class-map. For the dscp value match, this should work just as I show in the example. If you still have problems for matching the dscp value, just leave the ACL match only.</p>
<p>Cheers<br />
Harris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wesley</title>
		<link>http://www.networkstraining.com/cisco-asa-qos-for-voip-traffic/comment-page-1/#comment-86</link>
		<dc:creator>Wesley</dc:creator>
		<pubDate>Mon, 18 May 2009 15:40:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.networkstraining.com/?p=325#comment-86</guid>
		<description>ASA-1(config)# class-map Voice-OUT
ASA-1(config-cmap)# match dscp ef
ASA-1(config-cmap)# match access-list VoIP-Traffic-OUT

I cannot add these 2 matches. Can you help me?</description>
		<content:encoded><![CDATA[<p>ASA-1(config)# class-map Voice-OUT<br />
ASA-1(config-cmap)# match dscp ef<br />
ASA-1(config-cmap)# match access-list VoIP-Traffic-OUT</p>
<p>I cannot add these 2 matches. Can you help me?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

Served from: www.networkstraining.com @ 2012-02-04 13:01:42 -->
