|Issue 5836||Setting DSCP constraint on windows7 OS does not work|
|Starred by 28 users||Reported by rajkumar...@gmail.com, Apr 28 2016||Back to list|
What steps will reproduce the problem? 1. Set 'googdscp' constraint to true and make webrtc call to another webrtc page on chrome browser. DSCP value marked on the packets is 0x00, which is default forwarding "Standard" service class. The same scenario when tested on mac and linux OS works perfectly with the DSCP value marked on the packet to be 2E(i.e., 46 - Expedited forwarding) What is the expected result? Default value of DSCP for voice/video calls should be set correctly. What do you see instead? DSCP value marked on the packets is 0x00, which is default forwarding "Standard" service class. What version of the product are you using? On what operating system? Chrome 50, Windows 7 Os Please provide any additional information below. The same scenario when tested on mac OS and linux works perfectly with the DSCP value marked on the packet to be 2E(i.e., 46 - Expedited forwarding)
May 2 2016,
pthatcher@, please help to have a check.
May 2 2016,
This may not be possible for Win 7.
May 2 2016,
Oct 18 2016,
Oct 26 2016,
This is not a P1.
Dec 5 2016,
[bulk-edit] This issue appears to have been triaged (as evidenced by the presence of the EngTriaged label) and also has an Owner -- hence, changing its status to Assigned. If the currently set Owner is wrong, then please re-assign to a correct Owner, or remove Owner and set status to Available.
Could you please provide an estimated target milestone for this, as we have this issue reported from few customer escalations. Recommend if this can be moved to Pri:1, as it has high impact on Contact center customer currently. thanks!
Any updates ?
Request to communicate us on the milestone targeted for this atleast.
Sorry for not noticing your request earlier. We'll aim for fixing this in M58.
Looking forward for the update
Will this make it to M58?
No; bumping milestone. This is still high on our priorities though so it's more likely to hit M59.
Hi, Any update? Is it still planned for release in M59 or is it more likely to hit M60? Thanks!
Some other things have come up, but it's still possible we'll get to it.
Removing the milestone since there is no estimate on when this is likely to be looked at (as per #15). Please update the milestone accordingly otherwise.
Any updates on this one?
Jul 18 (5 days ago),
We may look at this soon. After some brief investigation, I found this: https://support.microsoft.com/en-us/help/2733528/policy-based-qos-not-working-in-windows-7-clients It sounds like starting in Windows 7, DSCP markings are only enabled if the network interface is attached to a "domain". Here's something more of an explanation: https://technet.microsoft.com/en-us/library/dd919203(v=ws.10).aspx There's this too: https://blogs.msdn.microsoft.com/wndp/2009/01/27/qos-in-windows-7/ I still don't completely understand this, but wanted to make a note of it before I forgot.
|► Sign in to add a comment|