ows: Voice-RTP Packets in this class will be put into the strict priority queue. The queue will be sized for 128 Kbps. This is roughly the size of two 64 Kbps G711-encoded VoIP calls. Packets with an IP precedence of 5 will be put into this queue. This is defined in the Voice-RTP class map. Voice-Control The voice control for the VoIP class should not consume much bandwidth. I have guaranteed 5 percent of the link's total bandwidth to this class. Packets marked with an IP precedence of 3 will be put into this queue. This is defined in the Voice- Control class map. I have guaranteed this class 10 percent of the link's total bandwidth. Any traffic with a destination port of 80 will match this class, as referenced by the HTTP class map and access list 101. class-default This queue is where packets that don't match any other queue will end up. The only definition for the queue is that these packets will be fair-queued. They will treated as they would be on a regular T1 serial link, but only after the other queues have been processed. The configuration for the class maps is as follows. class-default is a default class in IOS that requires no configuration: class-map match-any HTTP match access-group 101 class-map match-any Voice-RTP match ip precedence 5 class-map match-all Voice-Control match ip precedence 3 Chapter 34: The Converged Network The HTTP class references access list 101 for matching packets. The access list checks for the presence of HTTP packets: access-list 101 permit tcp any any eq WWW access-list 101 permit tcp any any eq 443 I could have used the statement match protocol http in the class map instead of calling an access list. However, this would have matched only port 80. Using an access list allows the flexibility of adding HTTPS (port 443) or HTTP running on nonstandard ports such as 8080. Monitoring QoS You monitor queues primarily through a couple of simple commands. The output of these commands contains a lot of information, SO I'll explain what you need to look for. First, run the show interf