Confirmed users
214
edits
Media/WebRTC/Architecture: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
# JS calls create one or more MediaStream objects via the GetUserMedia() API. The GUM code works with the MediaStream code and returns a MediaStream object. | # JS calls create one or more MediaStream objects via the GetUserMedia() API. The GUM code works with the MediaStream code and returns a MediaStream object. | ||
# JS calls create a PeerConnection | # JS calls new PeerConnection() which creates a PeerConnection object. [QUESTION: does this create a CC_Call right here?] | ||
# JS calls pc.AddStream() to add a stream to the PeerConnection. | |||
# JS calls pc.CreateOffer() to create an offer. | |||
# Inside PeerConnection.createOffer(), the following steps happen: | |||
## A Create offer request is sent to the CCAPP_Task | |||
## An appropriate number of WebRTC streams are set up to match the number of streams. | |||
## Some number of mtransports are set up (to match the appropriate number of streams) [OPEN QUESTION: is this done by PeerConnection or inside SIPCC?. | |||
<h2> Thread Diagram </h2> | <h2> Thread Diagram </h2> | ||