<div>
Excellent. &nbsp;Thank you.
</div>


<div>
<div class="content wysiwyg-content">
I have auto qos turned on my edge switch. &nbsp;I have a trunk to the root bridge and router via a gig port on each. &nbsp;How can I verify that RTP packets are getting the properly slapped with DSCP value EF and that that is being maintained as I hand off the RTP packets to my MPLS provider? &nbsp;When I am looking at the netflow data for the WAN/MPLS router I am seeing the RTP traffic marked as CS0. &nbsp;And I'm trying to troubleshoot how the packets are losing the EF that I believe the phone puts on their natively and the Auto QoS should slap on there if not. &nbsp;<br />
<br />
<br />
interface FastEthernet1/0/6<br />
&nbsp;switchport mode access<br />
&nbsp;switchport voice vlan 2<br />
&nbsp;srr-queue bandwidth share 10 10 60 20<br />
&nbsp;srr-queue bandwidth shape &nbsp;10 &nbsp;0 &nbsp;0 &nbsp;0<br />
&nbsp;priority-queue out<br />
&nbsp;mls qos trust device cisco-phone<br />
&nbsp;mls qos trust cos<br />
&nbsp;auto qos voip cisco-phone<br />
&nbsp;spanning-tree portfast<br />
&nbsp;service-policy input AutoQoS-Police-CiscoPhone<br />

</div>
</div>


I have auto qos turned on my edge switch.  I have a trunk to the root bridge and router via a gig port on each.  How can I verify that RTP packets are getting the properly slapped with DSCP value EF and that that is being maintained as I hand off the RTP packets to my MPLS provider?  When I am looking at the netflow data for the WAN/MPLS router I am seeing the RTP traffic marked as CS0.  And I'm trying to troubleshoot how the packets are losing the EF that I believe the phone puts on their natively and the Auto QoS should slap on there if not.  


interface FastEthernet1/0/6
 switchport mode access
 switchport voice vlan 2
 srr-queue bandwidth share 10 10 60 20
 srr-queue bandwidth shape  10  0  0  0
 priority-queue out
 mls qos trust device cisco-phone
 mls qos trust cos
 auto qos voip cisco-phone
 spanning-tree portfast
 service-policy input AutoQoS-Police-CiscoPhone


Cisco VOIP QoS - passing on the markings

IP telephony (Internet Protocol telephony) is a general term for the technologies that use the Internet Protocol's packet-switched connections to exchange voice, fax, and other forms of information that have traditionally been carried over the dedicated circuit-switched connections of the public switched telephone network (PSTN). Using the Internet, calls travel as packets of data on shared lines, avoiding the tolls of the PSTN. The challenge in IP telephony is to deliver the voice, fax, or video packets in a dependable flow to the user.

IP Telephony

Network Operations includes asset management, help-desk supervision, security and user policies, infrastructure administration and anything else that affects the operation of your network. Discussions will include those of best practices in platforms, configurations, performance, security and accounting.

Network Operations

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.