Project: webrtc Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 5836 Setting DSCP constraint on windows7 OS does not work
Starred by 24 users Reported by rajkumar...@gmail.com, Apr 28 2016 Back to list
Status: Assigned
Owner:
Cc:
Components:
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment
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)


 
Project Member Comment 1 by braveyao@webrtc.org, May 2 2016
Cc: braveyao@webrtc.org
Components: Network
Owner: pthatcher@webrtc.org
pthatcher@, please help to have a check.
Project Member Comment 2 by pthatcher@webrtc.org, May 2 2016
Cc: sergeyu@chromium.org
Owner: deadbeef@webrtc.org
This may not be possible for Win 7.
Project Member Comment 3 by pthatcher@webrtc.org, May 2 2016
Labels: EngTriaged
Project Member Comment 4 by honghaiz@webrtc.org, Oct 18 2016
Labels: -Pri-2 Pri-1
Project Member Comment 5 by pthatcher@google.com, Oct 26 2016
Labels: -Pri-1 Pri-2
This is not a P1.
Project Member Comment 6 by anatolid@chromium.org, Dec 5
Status: Assigned
[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.
Project Member Comment 10 by deadbeef@webrtc.org, Feb 6
Labels: M-58
Sorry for not noticing your request earlier. We'll aim for fixing this in M58.
Looking forward for the update
Project Member Comment 12 by anatolid@chromium.org, Feb 23
Will this make it to M58?
Project Member Comment 13 by deadbeef@chromium.org, Feb 23
Labels: -M-58 M-59
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!
Project Member Comment 15 by deadbeef@webrtc.org, Mar 22
Some other things have come up, but it's still possible we'll get to it.
Project Member Comment 16 by anatolid@webrtc.org, Apr 18
Labels: -M-59
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.
Sign in to add a comment