h specific types of traffic. There are a wide variety of matching possibilities for class maps-they can match specific IP precedence values, DSCP values, or even ACLs. The only function class maps accomplish is matching. The following class map, called Voice-Calls, matches either DSCP EF (express forwarding), or IP precedence 5: class-map match-any Voice-Calls description [--- Actual Calls (Set on IP Phones and Dial-Peers) ]---] match ip dscp ef match ip precedence 5 This is technically unnecessary, however, because (as was discussed in the last chapter) the two are synonymous. Let's change it SO it's easier to read: class-map match-any Voice-Calls description [ Actual Calls (Set on IP Phones and Dial-Peers) ]---] match ip precedence 5 We could just as easily have used DSCP EF, but this is a simple configuration, SO we'll stick with IP precedence. Configuring the Routers We now need to create class maps for the other items in our list. Next is call control: class-map match-any Voice-Control description [ Call Control (Set on CallManager and IP Phones) ]---] match ip precedence 3 Call Manager, the voice gateways, and the IP phones are all capable of setting the precedence values for us, SO we'll take advantage of that, and assume that all voice call-control traffic has been marked with an IP precedence of 3. The next item in our list is telnet and SSH. In this example, we'll match the protocols by name in the class map: class-map match-any Telnet-Traffic description [--- Telnet & SSH ]---] match protocol telnet match protocol ssh For HTTP, however, we need to include more than just the protocol name. We can't simply say match protocol http because then we'd match HTTP traffic from any source to any destination. Our requirements indicate that we need a way to match HTTP (only port 80) traffic either sourced from or destined for 10.10.100.100. Access lists to the rescue: class-map match-any HTTP-Call-Center description [ Call Center HTTP ]--] match access-group 121 Now, we need to create an ACL to match our ccess-gr