ntation states that 150 bps (plus overhead) per phone should be guaranteed for call control. For four calls, that's only 600 bps. Other documentation states that 2-5 percent of overall link band- width should be allocated for call control. For a T1, that's about 30-77 Kbps. Let's take the middle ground and say we need 30 Kbps for call control: Voice control-30 Kbps We're only prioritizing Telnet and SSH for emergencies, SO these don't need a lot of bandwidth. Allocating 64 Kbps should be more than enough, and this amount won't impact other protocols: Telnet/SSH-64Kbps HTTP to and from 10.10.100.100 is a critical app on our network, SO we'll give it a sizable chunk of bandwidth. Let's say during our discovery process, HTTP traffic hov- ered at around 300 Kbps. We'll plan for growth, and allocate 384 Kbps: HTTP to/from 10.10.100.100-384 Kbps Email is prioritized only to appease the executives, SO we'll allocate it a small amount of bandwidth: 128 Kbps. This should give it enough bandwidth to function while still leaving plenty for other applications: Email (SMTP, POP, IMAP, Exchange)-128 Kbps The default queue will be allocated the remaining amount of bandwidth after the other queues are considered. Assuming a T1 at 1544 Kbps and the queues we've decided upon, we get the following results: 1,544 - (148 + 30 + 64 + 384 + 128) = 754 Kbps. So, the final element will be: Everything else (default-best effort)-remainder (754k) Our final list looks like this: Voice RTP-priority queue-148 Kbps LLQ Scenario Voice control-30 Kbps Telnet/SSH-64 Kbps HTTP to/from 10.10.100.100-384 Kbps Email (SMTP, POP, IMAP, Exchange)-128 Kbps Everything else (default-best effort)-remainder (754 Kbps) Configuring the Routers We've done all of our discovery and planning. Now it's time to get to the meat of the exercise: configuring the routers. For this implementation, we're going to configure QoS on the edge routers that connect the T1 to the individual buildings. We will do marking, classification, and policing on the same device, but rememb