Technical data

Global QoS Settings

7 0.0.0.0 0.0.0.0 5200 0.0.0.0 0.0.0.0 0 17

other forward head

8 0.0.0.0 0.0.0.0 0 0.0.0.0 0.0.0.0 5200 17

other forward head

QoS and Firewall Rules(6 entries)

The first two pre-configured QoS rules give priority to H.323v1 traffic sent to and

from TCP port 1720 respectively. The next two QoS rules give priority to SIP traffic

sent to and from UDP/TCP port 5060 respectively. Rules 7 and 8 are for Vocera

badges and use port 5200 with UDP.

You normally do not need to configure QoS rules in the controller, unless you have

special requirements in your configuration. For example:

 You want to drop packets coming from certain ports or IP addresses.

 You want to configure the controller to give priority to traffic other than H.323v1

and SIP traffic.

You can configure rules to provide priority-based or reserved QoS. QoS is applied with

reserved traffic being allocated the first portion of total bandwidth, followed by

fixed priority levels, and finally by the best-effort (default) traffic class. You can

configure reserved QoS for new applications using the average packet rate and token

bucket rate parameters together as the traffic specification (also called TSpec in

IETF IntServ RFCs).

Global QoS Settings

Global QoS parameters configure settings that determine call quality on a global

level. These settings allow you to fine tune Call Admission Control (CAC), client load

balancing, bandwidth scaling, and time-to-live settings.

You can configure the following global quality-of-service parameters:

Table 18: Global Quality-of-Service Parameters

Command Purpose

qosvars admission { admitall |

pending | reject }

Admission control. Valid values are admitall, pending, and

reject.

qosvars ttl ttl-value

Default time-to-live in seconds for all other protocols besides

TCP and UDP.