All Cisco QoS books and papers are focused on managing congstion over output queues (TxQ). There is few or no mention to INPUT queues. What is the reason? Is it so irrelevant?
Please consider this scenario: A hub-and-spoke network (central node "A") with 2 remote nodes ("B" and "C") connected to "A" through FR PVCs. "B" is only transmitting VoIP to "A" and "C" is only transmitting data. "A" receive both traffics in the same interface. If "C" is flooding with FTP traffic the INPUT queue in "A", What do I do to avoid that VoIP traffic coming from "B" be discarded in "A"? How do you manage congestion in "A" INPUT queue?
What I am talking about is called 'Hierarchical Qos policy' and is configured in a Cisco router using the MQC. Recent IOS versions use the MQC framework rather than the legacy frame-relay traffic-shaping, so be sure to research this correctly before you implement this.
Note also that a traffic-shaper differs from a traffic policer in that it actually shapes the traffic to a specific rate by slightly delaying traffic until the next interval rather than discarding traffic that exceeds the traffic rate like a policer. The difference between the two is staggering for VoIP, video, TCP throughput, response time for interactive applications such as telnet, ssh, tn3270, citrix, etc.
One problem with all the QoS information that is out there is that there are literally hundreds of commands available in Cisco IOS for various QoS features and hardware platforms and this makes it very difficult to figure out which tools to use for your specific network.
Feel free to send any questions that you have and I will do my best to answer them, including giving you some guidance in how to configure this properly. Done correctly, this is really not that complicated.
Here are a few URLs to get you started: