McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 8

↗ View in doc context
page
8
source
voice-quality/troubleshooting/qos-voip-solutions/qos-voip-solutions.md
chunk_id
voice-quality::troubleshooting::qos-voip-solutions::qos-voip-solutions::7

Quality of Service for Voice over IP QoS Queueing Mechanisms 8 QoSVoIP.mif LLQ Configuration Example The following configuration example shows how to configure LLQ: Configuration Example 5: LLQ access-list 100 permit udp any any range 16384 32000 access-list 100 permit tcp any any eq 1720 access-list 101 permit tcp any any eq 80 access-list 102 permit tcp any any eq 23 ! class-map voip match access-group 100 class-map data1 match protocol class-map data2 match access-group 102 ! policy-map llq class voip priority 32 class data1 bandwidth 64 class data2 bandwidth 32 class class-default fair-queue ! interface Serial1/0 bandwidth 256 service-policy output llq In this example, any traffic that matches access list 100 will be classified as class voip (meaning voice traffic) and given high priority up to 32 kbps. Access list 100 matches the common UDP ports used by VoIP and H.323 signaling traffic to TCP port 1720. The class data1 command matches web traffic (TCP port 80 as seen in access list 101) and guarantees 64 kbps; the class data2 command matches Telnet traffic (TCP port 23 as seen in access list 102) and guarantees 32 kbps. The default class is configured to give an equal share of the remaining bandwidth to unclassified flows. The policy is called llq, and it is applied on outgoing traffic on serial interface 1/0, which has a total bandwidth of 256 kbps. Note By default, the total guaranteed bandwidth and priority bandwidth for all classes should be less than 75 percent of the interface bandwidth. You can modify this percentage by using the max-reserved bandwidth interface configuration command.

Image 1 from page 8