Media/WebRTC/Architecture: Difference between revisions

Jump to navigation Jump to search
Line 196: Line 196:


The callee receives an offer through its signaling mechanism and calls the JS API setRemoteDescription passing in the SDP. Internally in the GSMTask the offer SDP is parsed, the remote media streams are constructed and events are fired back to the DOM Thread signaling the addition of remote media streams.  If there are ICE candidates in the offer SDP they are dispatched to the STS thread for ICE processing.
The callee receives an offer through its signaling mechanism and calls the JS API setRemoteDescription passing in the SDP. Internally in the GSMTask the offer SDP is parsed, the remote media streams are constructed and events are fired back to the DOM Thread signaling the addition of remote media streams.  If there are ICE candidates in the offer SDP they are dispatched to the STS thread for ICE processing.
[Question: Enda. I have not shown the interaction where the remote media streams are created, I am not sure what GSMTask talks to here.]


=== Signaling System: CreateAnswer(Callee) ===
=== Signaling System: CreateAnswer(Callee) ===
43

edits

Navigation menu