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. To sum it up simply, even though Aircall is tagging all the packets correctly, (value 46 (EF101110)), Windows is not taking this information into account. Unfortunately, as a result, you will not be able to configure a QoS for use with Aircall.
⚠️ Please note that Chromium is currently undergoing an investigation and this 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 to this situation by configuring a QoS via the QoS Packet Scheduler in Windows 10. This is by default added to your device and triggered when a new connection is configured.
Now, let’s take a look at the steps below to configure the QoS using Local Group Policy Editor.
Hold down Win+ R together on the keyboard to open Run Dialog.In the empty space, type gpedit.msc (if not available please follow the steps mentioned here)
Hit Enter to get access to Local Group Policy Editor.
Once the window opens, please Navigate the following path: Local Computer Policy Computer Configuration Administrative Templates Network QoS Packet Scheduler
On the right-hand side of the console, locate limit reservable bandwidth and double click.
Click on the radio button of enabled and later set up the percentage of the bandwidth limit with 0.
Finally, click on the ok button in order to confirm and exit from the GP editor. Once completed, please restart your computer to apply the changes.
If you would like more detailed information about this topic, please feel free to refer to the following tutorial.
Still in need of assistance? Please feel free to reach out to the Support Team and we’ll be happy to assist!