Closed Bug 1004510 Opened 12 years ago Closed 17 days ago

Support PRANSWER in WebRTC JSEP signaling protocol

Categories

(Core :: WebRTC: Signaling, defect, P2)

defect
Points:
1

Tracking

()

RESOLVED FIXED
158 Branch
Tracking Status
firefox158 --- fixed

People

(Reporter: jesup, Assigned: bwc)

References

(Blocks 2 open bugs)

Details

Attachments

(2 files)

PRANSWER is part of the JSEP draft/plans
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)
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
Priority: -- → P1
Target Milestone: --- → mozilla33
Whiteboard: p=1
Depends on: 857115
Priority: P1 → P3
Target Milestone: mozilla33 → mozilla35
backlog: --- → webRTC+
Points: --- → 1
Rank: 35
Whiteboard: p=1
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.
is there any update on the time line for this?
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Blocks: 1533020
Severity: normal → S3
See Also: → 2019381
Severity: S3 → S2
Priority: P4 → P2

This could end up being tricky, and it probably makes sense to start on this early to discover just how tricky it will be, and what it will interact with. pranswer is (in part) an explicit way of setting up early media (see bug 2019381), so these two bugs will probably be worked at the same time.

Depends on: 1339203
Assignee: nobody → docfaraday
Target Milestone: mozilla35 → ---
Depends on: 2072358
Attachment #9645293 - Attachment description: WIP: Bug 1004510: (WIP) Test-cases for pranswer. → WIP: Bug 1004510: Test-cases for pranswer.
Attachment #9645294 - Attachment description: WIP: Bug 1004510: (WIP) pranswer support → WIP: Bug 1004510: pranswer support
Attachment #9645293 - Attachment description: WIP: Bug 1004510: Test-cases for pranswer. → Bug 1004510: Test-cases for pranswer. r?mjf
Attachment #9645294 - Attachment description: WIP: Bug 1004510: pranswer support → Bug 1004510: pranswer support r?mjf
Status: NEW → RESOLVED
Closed: 17 days ago
Resolution: --- → FIXED
Target Milestone: --- → 158 Branch

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/62891 for changes under testing/web-platform/tests

:bwc did you want to mention this in the 158 release notes? Please nominate if so.

Flags: needinfo?(docfaraday)
QA Whiteboard: [qa-triage-done-c159/b158]

(In reply to Dianna Smith [:diannaS] from comment #13)

:bwc did you want to mention this in the 158 release notes? Please nominate if so.

Haha, no. This feature is kinda stupid, but it's in the spec and interop 2026, so here we are.

Flags: needinfo?(docfaraday)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: