Global Quality-of-Service Parameters (requires Level 10 permission)

Use this page (Configuration > QoS > System Settings) to configure global QoS parameters.

  1. In the On/Off list, select one of the following values:
  2. In the Admission Control list, select one of the following values, which specifies what happens to a QoS flow (for example, a newly established voice call) that requests air resources that are not available at that time:

    By default, admission control is set to Request Pending.

  3. In the Drop Policy box, select one of the following values, which specifies what happens to a QoS flow's packets when the queues for that flow are full:
  4. In the Default Time-to-Live box, type the amount of time that the system recognizes and holds resources for an ongoing flow (for example, a voice call) without seeing any packet activity. The value can be between 0 to 65,535 seconds.

    For example, if you set the default time-to-live value to 300 seconds, a call can continue for 5 minutes without any packets being exchanged before the resources for it are relinquished. Applications that use silence suppression might require higher time-to-live values.

  5. In the UDP Time-to-Live box, type the amount of time the QoS UDP flow can be inactive before the flow is moved to the best-effort class.

    The value can be between 0 to 65,535 seconds.

  6. In the TCP Time-to-Live box, type the amount of time the QoS TCP flow can be inactive before the flow is moved to the best-effort class.

    The value can be between 0 to 65,535 seconds.

  7. Bandwidth scaling controls the overbooking factor for QoS flows.

    A valid value is from 1% to 100,000%. Normally, this value is set to 100%. A value under 100% reduces the amount of resources that can be reserved, allowing resources for best-effort traffic in a fully loaded environment. Specify a value over 100% when using applications that overestimate the amount of resources they use and is best used to account for applications that use silence suppression or vary the amount of traffic being sent. For example, if you specify a value of 110%, the system acts as if there is 10% more real bandwidth available.

  8. In the Maximum Calls per AP box, enter the maximum number of simultaneous calls for APs. Valid number of calls range from 0 to 256. By default, 0 is set, which allows all calls. Specifying a call limit (threshold) per AP ensures a consistent level of voice quality. This setting implements the Call Admission Control (CAC) feature, which ensures a consistent level of voice quality by setting a threshold for the number of calls per AP. As an AP nears the set threshold, CAC denies new SIP connections until enough bandwidth is available to effectively handle the resulting media stream.

    When the call limit for the AP is exceeded, all new calls receive a 486_BusyHere response until the number of calls is less than the specified threshold. On handoff from one AP to another, if there are no resources available in the second AP, the call is classified as Pending/Best-effort until the needed resources are available.

  9. For Maximum Calls per Interference Region, you can indicate that a region will stop adding phone calls when 0-256 calls are active.
  10. In the Maximum Stations per AP box, enter the maximum number of clients (stations) that can associate with an AP. This value can be between 0 and 128; by default, it is set to 128. By setting this limit, you can configure client load balance across APs, ensuring a level of QoS for client call sessions. When the maximum number of stations per AP is reached, new call associations can be distributed among APs and BSSIDs in a round-robin fashion, evening out the distribution if the Load Balance Overflow setting  is set to On.
  11. In the Maximum Stations per BSSID, enter the maximum number of clients (stations) that can associate with a BSSID. This value can be between 0 and 1023; by default, it is set to 0. By setting this limit, you can configure client load balancing across BSSIDs, ensuring a level of QoS for client call sessions. When the maximum number of stations per BSSID is reached, new call associations can be distributed among BSSIDs in a round-robin fashion, evening out the distribution if the Load Balance Overflow setting is on.

    If you want to perform client load balancing across VirtualCells, then it is recommended that you set this value to the number of devices in the network divided by the number of VirtualCells (or BSSIDs). If you expect that at some times there may be additional devices beyond that joining the network, you should also set Load Balance Overflow to On so that once the maximum number of stations limit is reached, round-robin will be performed to balance new client assignments.

  12. In the Load Balance Overflow drop-down list, select On to enable client load balancing across BSSIDs and APs, ensuring a level of QoS for client call sessions. This setting is  used in conjunction with the Maximum Stations per AP and Maximum Stations per BSSID settings. When this setting is enabled, and the maximum number of stations is reached, new call associations are distributed among APs and BSSIDs in a round-robin fashion, evening out the distribution.
  13. In the Maximum Calls Per BSSID, enter the maximum number of simultaneous calls for BSSIDs. Valid number of calls range from 0 to 1023. By default, 0 is set, which allows all calls.  By setting this limit, you can configure a threshold for the maximum number of calls per BSS. This command implements the Call Admission Control (CAC) feature, which ensures a consistent level of voice quality by setting a threshold for the number of calls per BSS. As a BSS nears the set threshold, CAC denies new SIP connections until enough bandwidth is available to effectively handle the resulting media stream.

    When the call limit for the BSS is exceeded, all new calls receive a 486_BusyHere response until the number of calls is under the specified threshold.

  14. In the CAC Deauth drop-down list, select On to enable CAC (Call Admission Control) resources. When set to On, the system sends an 802.11 De-authentication frame to push the client to an alternate BSS. When set to Off (default setting), the system sends a modified INVITE message (with an URI of sip:#*#*#*#*#*@a.com) to the SIP server so that it can generate a Reorder-Tone using the INFO message. In all cases, if it is the terminator that exceeds the available CAC, a 486_BusyHere message is sent to the SIP server.
  15. In the Station Assignment Age Time, enter a value for the amount of time an AP caches a client's state while waiting for a Probe or Authenticate request/response sequence with a BSS to complete. Possible values range from 5 to 2000; the default 30 seconds is adequate for most sites and should not be changed unless recommended by Customer Service. 
  16. In the SIP Idle Timeout, enter a value for the amount of time the a call can idle before it must be answered (the setting is a part of CAC). The valid range is from 5 to 3600 seconds, with the default setting at 120 seconds. 
  17. To save your changes, click OK.

For QoS examples, see the System Director Configuration Guide.