Closed Bug 735352 Opened 13 years ago Closed 13 years ago

Implement webrtc/signaling calls to support JSEP/ROAP

Categories

(Core :: WebRTC: Signaling, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 729541

People

(Reporter: ehugg, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Build ID: 20120215223356 Steps to reproduce: The JSEP 02 spec 7.1 shows this: This example demonstrates a ROAP call, without the use of trickle candidates. // Call is initiated toward Answerer OffererJS->OffererUA: pc = new PeerConnection(); OffererJS->OffererUA: pc.addStream(localStream, null); OffererJS->OffererUA: pc.startIce(); OffererUA->OffererJS: iceCallback(candidate, false); OffererJS->OffererUA: offer = pc.createOffer(null); OffererJS->OffererUA: pc.setLocalDescription(SDP_OFFER, offer.toSdp()); OffererJS->AnswererJS: {"type":"OFFER", "sdp":"<offer>"} // OFFER arrives at Answerer AnswererJS->AnswererUA: pc = new PeerConnection(); AnswererJS->AnswererUA: pc.setRemoteDescription(SDP_OFFER, msg.sdp); AnswererUA->AnswererJS: onaddstream(remoteStream); AnswererJS->AnswererUA: pc.startIce(); AnswererUA->OffererUA: iceCallback(candidate, false); // Answerer accepts call AnswererJS->AnswererUA: peer.addStream(localStream, null); AnswererJS->AnswererUA: answer = peer.createAnswer(msg.offer, null); AnswererJS->AnswererUA: peer.setLocalDescription(SDP_ANSWER, answer); AnswererJS->OffererJS: {"type":"ANSWER","sdp":"<answer>"} // ANSWER arrives at Offerer OffererJS->OffererUA: peer.setRemoteDescription(ANSWER, answer); OffererUA->OffererJS: onaddstream(remoteStream); // ICE Completes (at Answerer) AnswererUA->AnswererJS: onopen(); AnswererUA->OffererUA: Media We should implement the methods in the signaling code to support this feature.
OS: Windows 7 → All
Hardware: x86_64 → All
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.