When using a Windows device, you may experience an issue with DSCP tagging. When trying to classify network traffic, Windows will not provide any DSCP tags.

In simple terms, even though Aircall is tagging all packets correctly with value 46 (EF101110), Windows is not taking this information into account. As a result, you will not be able to configure a QoS rule based on DSCP tags for use with Aircall.

Important: Chromium is currently undergoing an investigation related to this behavior and the issue will be resolved as quickly as possible.
If you would like to follow this issue closely, please refer to the following link here.

Aircall proposes a temporary solution by configuring QoS via the QoS Packet Scheduler in Windows 10. This component is added to your device by default and is triggered when a new connection is configured.

The steps below describe how to configure QoS using Local Group Policy Editor.

Configure QoS using Local Group Policy Editor

Steps:

  1. Hold down Win + R on the keyboard to open the Run dialog.

  2. In the field, type gpedit.msc

    • If this is not available, please follow the steps mentioned here.

  3. Press Enter to open Local Group Policy Editor.

  1. In the left-hand panel, navigate to:
    Local Computer Policy > Computer Configuration > Administrative Templates > Network > QoS Packet Scheduler

  2. On the right-hand side of the console, locate Limit reservable bandwidth and double-click it.

  1. Select the Enabled radio button.

  2. Set the bandwidth limit percentage to 0.

  1. Click OK to confirm and exit Local Group Policy Editor.

  2. Restart your computer to apply the changes.

If you would like more detailed information about this topic, please refer to the following tutorial.