er that these steps can be separated onto discrete devices as needed. VoIP phones will usually mark their packets, SO we'll assume that they're doing SO on our network. To configure LLQ, we need to configure three things: class maps, policy maps, and service policies. Class Maps We need to identify which packets should be marked. To do this, we will create class maps, which will match specific types of traffic. There are a wide variety of matching possibilities for class maps-they can match specific IP precedence values, DSCP val- ues, or even ACLs. The only function class maps accomplish is matching. The following class map, called Voice-Calls, matches either DSCP EF (express for- warding) 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 discussed in Chapter 31) 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. 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 Chapter 32: Designing QoS 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 saymatch protocol http