Confirmed users
214
edits
Media/WebRTC/Architecture: Difference between revisions
Jump to navigation
Jump to search
→Signaling System: SetLocal(Caller)
| Line 186: | Line 186: | ||
=== Signaling System: SetLocal(Caller) === | === Signaling System: SetLocal(Caller) === | ||
http://www.websequencediagrams.com/?lz= | http://www.websequencediagrams.com/?lz=dGl0bGUgU2lnbmFsaW5nIFRocmVhZHMgKENhbGxlcjogU2V0TG9jYWxEZXNjcmlwdGlvbikKCnBhcnRpY2lwYW50ICJET00AMQciIGFzIERPTQATDVBDIGFzIFBDACcOQ0NBUFBfVGFzawAwBQAKBQBKDUdTTVRhc2sgYXMgR1NNCgoKRE9NIC0-IFBDOiBEaXNwYXRjaCgAgQkVUEMgLT4ATAY6IElQQyhGRUFUVVJFX1NFVExPQ0FMREVTQykKAH0FIC0-IEdTTQAiBkNDX01TRwAYDwoKR1MAdAUAIgVDb21wYXJlIFNEUCB0byBPZmZlciBTRFAAHQoAcQcAgRkKdGF0ZT1DYWxsIFNlbnQpIABvCgCBPQ4AGQ8AgUAHRE9NADwRTmVnb3RpYXRpbmcpCgo&s=default | ||
Once the caller has generated the offer the JS can call SetLocalDescription(). This just bubbles its way down to the GSMTask | |||
which verifies that the SDP is correct (currently this means matches the outstanding SDP) and if so partially assembles the | |||
appropriate media streams and transport objects. Note that we cannot actually plug them together until we have | |||
the DTLS fingerprint from the other side (or we will need some clever UI). See the SetRemote(Caller) section below. | |||
=== Signaling System: SetRemote(Callee) === | === Signaling System: SetRemote(Callee) === | ||