Open
Bug 1532658
Opened 5 years ago
Updated 1 year ago
Support webrtc-priority for RTCRtpSender
Categories
(Core :: WebRTC: Networking, enhancement, P3)
Tracking
()
NEW
People
(Reporter: alstrashkov, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
|
56.81 KB,
image/png
|
Details |
dscp.png
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36
Steps to reproduce:
- Set priority to each RTCRtpSender
myRTCPeerConnection.getSenders().forEach(async sender => {
let params = sender.getParameters();
params.priority = 'high';
await sender.setParameters(params);
console.log('params have successfully accepted');
})
Actual results:
DSCP packets is marked CS0 (Default)
Expected results:
DSCP packets is marked according to recommended values from the table
https://tools.ietf.org/html/draft-ietf-tsvwg-rtcweb-qos-18#section-5
|
||
Updated•5 years ago
|
Component: Untriaged → WebRTC: Networking
Product: Firefox → Core
|
||
Comment 1•5 years ago
|
||
Yeah, we don't do anything with that param yet.
Status: UNCONFIRMED → NEW
Rank: 25
Ever confirmed: true
Priority: -- → P3
|
|
||
Updated•2 years ago
|
Summary: Setting `priority` parameter of RTCRtpSender doesn`t work → Support webrtc-priority for RTCRtpSender
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•