43
edits
Media/WebRTC/Architecture: Difference between revisions
Jump to navigation
Jump to search
→Signaling System: SetRemote(Callee)
| Line 193: | Line 193: | ||
http://www.websequencediagrams.com/?lz=dGl0bGUgU2lnbmFsaW5nIFRocmVhZHMgKENhbGxlZTogU2V0UmVtb3RlRGVzY3JpcHRpb24pCnBhcnRpY2lwYW50ICJET00AMQciIGFzIERPTQATDVBDIGFzIFBDACcOQ0NBUFBfVGFzawAwBQAKBQBKDUdTTVRhc2sgYXMgR1MARA5TVFMgYXMgU1RTCgpET00gLT4gUEM6IERpc3BhdGNoKACBHhZQQyAtPgBjBjogSVBDKEZFQVRVUkVfU0VUUkVNT1RFU0MpCgCBEwUgLT4gR1NNACEGQ0NfTVNHABwKRAAjBQoKR1MAdQUAIwVnc21zZHBfbmVnb3RpYXRlX29mZmVyX3NkcAAfCFNUUwCBFwtJQ0UgQ2FuZGlkYXRlcykARAkAgRcHAIFACnRhdGU9QWxlcnRpbmcpIACBFQoAgWMOABkOAIFkB0RPTQA6EU4AgRsHACIFCgo&s=default | http://www.websequencediagrams.com/?lz=dGl0bGUgU2lnbmFsaW5nIFRocmVhZHMgKENhbGxlZTogU2V0UmVtb3RlRGVzY3JpcHRpb24pCnBhcnRpY2lwYW50ICJET00AMQciIGFzIERPTQATDVBDIGFzIFBDACcOQ0NBUFBfVGFzawAwBQAKBQBKDUdTTVRhc2sgYXMgR1MARA5TVFMgYXMgU1RTCgpET00gLT4gUEM6IERpc3BhdGNoKACBHhZQQyAtPgBjBjogSVBDKEZFQVRVUkVfU0VUUkVNT1RFU0MpCgCBEwUgLT4gR1NNACEGQ0NfTVNHABwKRAAjBQoKR1MAdQUAIwVnc21zZHBfbmVnb3RpYXRlX29mZmVyX3NkcAAfCFNUUwCBFwtJQ0UgQ2FuZGlkYXRlcykARAkAgRcHAIFACnRhdGU9QWxlcnRpbmcpIACBFQoAgWMOABkOAIFkB0RPTQA6EU4AgRsHACIFCgo&s=default | ||
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. | |||
=== Signaling System: CreateAnswer(Callee) === | === Signaling System: CreateAnswer(Callee) === | ||