Closed
Bug 1276369
Opened 10 years ago
Closed 3 years ago
Implement setParameter for RTPReceiver
Categories
(Core :: WebRTC, defect, P3)
Core
WebRTC
Tracking
()
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | affected |
| backlog | webrtc/webaudio+ |
People
(Reporter: drno, Unassigned, NeedInfo)
References
Details
Currently the spec does not specify a setParameter() call for the RTPReceiver. But it appears to be the only sensible way for setting a bandwidth restriction on the receiver, which if set can be signaled via 'b=...' in the SDP to the other side to restrict the RTPSender.
|
Reporter | |
Updated•10 years ago
|
backlog: --- → webrtc/webaudio+
Rank: 29
|
||
Comment 1•8 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 2•3 years ago
|
||
There's still no setParameters in RTCRtpReceiver or RTCRtpReceiver extensions. Closing.
But it appears to be the only sensible way for setting a bandwidth restriction on the receiver, which if set can be signaled via 'b=...' in the SDP to the other side to restrict the RTPSender.
I'm curious, how is this handled today? If not handled, is there a spec issue filed?
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(drno)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•