Closed
Bug 908794
Opened 11 years ago
Closed 9 years ago
Allow changing codec order by JS between createOffer/createAnswer and setLocal/setRemote
Categories
(Core :: WebRTC: Signaling, defect)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
People
(Reporter: ehugg, Assigned: bwc)
References
Details
Allow the Javascript to swap codec priority in the audio (which is the one where we have more than one codec). For example, JS could change the offer to prefer G.711 rather than Opus.
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → ethanhugg
Assignee | ||
Comment 1•9 years ago
|
||
This might just work now...
Assignee | ||
Comment 2•9 years ago
|
||
Looking at the code, I don't think this works exactly.
Assignee: ethanhugg → docfaraday
Assignee | ||
Comment 3•9 years ago
|
||
Ok, the logic we have will break if JS tries to reorder codecs in a local answer, but since we do not actually put more than one codec in an answer it still works out. Changing the order in an offer should work fine.
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•