Open
Bug 1004510
Opened 10 years ago
Updated 1 year ago
Support PRANSWER in WebRTC JSEP signaling protocol
Categories
(Core :: WebRTC: Signaling, defect, P4)
Core
WebRTC: Signaling
Tracking
()
NEW
mozilla35
backlog | webrtc/webaudio+ |
People
(Reporter: jesup, Unassigned)
References
(Blocks 2 open bugs)
Details
PRANSWER is part of the JSEP draft/plans
Comment 1•10 years ago
|
||
Hey Adam -- How much work is involved to add PRANSWER? Some folks from our community are very interested in knowing what's involved to add this and where this might fall on our roadmap.
Flags: needinfo?(adam)
Comment 2•10 years ago
|
||
In theory, this shouldn't be a huge amount of work. Basically, we need to replicate the "inband ringing" behavior from fsmdef_ev_out_alerting (in fsmdef.c) when we see PRANSWER messages (see the switch statements in fsmdef_ev_setlocaldesc and fsmdef_ev_setremotedesc). The tricky part here is ensuring that the subsequent final answer can be processed without blowing stuff up. We know that this isn't currently the case (which is why renegotiation is currently disabled) -- but if we fix this for renegotiation, then it would be fixed for PRANSWER (and vice-versa). So, if we land Bug 857115 first, then PRANSWER should be a pretty minor tweak in the signaling code; if we don't, then we need to fix whatever causes things to break when we try to modify an ongoing media stream as a prerequisite... and that might be a fairly large chunk of work.
Flags: needinfo?(adam)
See Also: → 857115
Updated•10 years ago
|
Priority: -- → P1
Target Milestone: --- → mozilla33
Updated•10 years ago
|
Whiteboard: p=1
Updated•10 years ago
|
Target Milestone: mozilla33 → mozilla35
Updated•9 years ago
|
backlog: --- → webRTC+
Points: --- → 1
Rank: 35
Whiteboard: p=1
Comment 3•9 years ago
|
||
Issue - I still see this error in the js console:"NotSupportedError: pranswer not yet implemented";when i use the pranswer; I try Firefox 41 and Firefox Nightly; They both failed.
Comment 5•8 years ago
|
||
is there any update on the time line for this?
Comment 6•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•