Class Rules - AudioCodes MP-20 Series User Manual

User's Manual
8. In the 'Bandwidth' field, define the bandwidth for the class:
•
Reserved: reserved (i.e., guaranteed) bandwidth (Committed Information Rate /
CIR) in kbps.
•
Maximum: specify the maximum bandwidth
9. From the 'Policy' drop-down list, select the policy for routing packets within the class:
• Priority: Priority queuing uses multiple queues so that traffic is distributed among
queues based on priority. This priority is defined according to packet priority,
which can be defined explicitly by a DSCP value or an 802.1p value.
•
FIFO: First In First Out. This priority queue ignores any previously-marked packet
priority.
•
Fairness: The fairness algorithm ensures no starvation by granting all packets a
certain level of priority.
•
RED: Random Early Detection. Utilizes statistical methods to drop packets in a
'probabilistic' way before queues overflow. Dropping packets in this way slows a
source down enough to keep the queue steady and reduces the number of
packets that would be lost when a queue overflows and a host is transmitting at a
high rate.
10. From the 'Schedule' drop-down list, select the scheduler rule (defined in Section
on page 55) that defines the time segments during which the class can be active. By
default, the class is always active.
11. Click OK to save your settings.

11.2.2.1 Class Rules

Class rules define which packets belong to the class. Without class rules, the shaping class
has no effect. Each class can have outbound and inbound rules for outgoing and incoming
traffic respectively. For example, you can define that all outgoing packets from computer A
in your LAN belong to your VoIP class. These packets are limited to the class settings
(bandwidth, schedule, etc.). In addition, you can define the traffic protocol and priority for
each rule (this is not mandatory as in Traffic Priority rules).
11.2.2.1.1 Inbound and Outbound Data
The device can control outgoing data easily. It can queue packets, delay them, give
precedence to other packets, or drop them. This helps in resolving upload (Tx) traffic
bottlenecks and in most cases is sufficient. However, in the case of download (Rx) traffic
bottlenecks, the ability to control the flow is much more limited. The device cannot queue
packets, since in most cases the LAN is much faster than the WAN and when the device
receives a packet from the WAN, it passes it immediately to the LAN.
QoS for ingress data has the following limitations, which do not exist for outgoing data:

QoS can only be applied to TCP streams (UDP streams cannot be delayed)

No borrowing mechanism

When reserving Rx bandwidth, it is strictly taken from the bandwidth of all other
classes
Version 4.4.3 121 MP-20x Multimedia Home Gateway
11. Quality of Service
5.6.1