![cisco 2950 manual configuration cisco 2950 manual configuration](https://www.cisco.com/c/dam/en/us/support/docs/security-vpn/public-key-infrastructure-pki/211333-IOS-PKI-Deployment-Guide-Initial-Design-00.png)
Trying to apply this QoS policy to every interface runs the 2950 out of resources:
![cisco 2950 manual configuration cisco 2950 manual configuration](https://i.ytimg.com/vi/Z8qin4kC_gA/hqdefault.jpg)
Apply the “Per Interface” specific commands to enable QoS on the uplink interface.Adjust the “Weighted Round Robin” queues (via COS markings) to give more weight to RTP Voice traffic.Create a Policy Map that uses your Class Maps.Create Class Maps to “Classify” traffic into groups by name.Create access list 103 for your “Voice Control” traffic.Create access list 104 for your “Priority Applications” traffic like video and Citrix etc.Create access list 105 for your “RTP Voice” traffic (Don’t worry if you don’t list every UDP port, we will get everything with DSCP 46 in the class map later).Verify that you set your IP PBX and IP Phones to mark Voice RTP traffic as COS 5 / DSCP 46 (and Voice Control traffic COS 3 / DSCP 26 if you can).In the examples below, it is assumed that Voice RTP traffic is already marked COS 5 / DSCP 46 by configuring your IP PBX and VoIP phones to do so.– All other regular traffic (like email and web) are not marked (by default this usually the case) The following QoS markings are assumed:.
![cisco 2950 manual configuration cisco 2950 manual configuration](https://data2.manualslib.com/first-image/i14/70/6976/697533/cisco-catalyst-2950.jpg)
Your VoIP gear (Phones and PBX etc.) has the ability to mark voice RTP traffic via COS and DSCP.You are using an existing 2950 only until you can afford to purchase a 2960 or better (You have been warned!).The Cisco 2950 Ethernet switch has some limited basic QoS functionality that you can (and should) configure to support VoIP.