You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just to be clear, we can tell all candidates have been gathered locally by way of the gathering state (and thus can signal it remotely).
However, when we receive a remote signal that no more candidates will arrive from the remote party we can't tell the ORTC RTCIceTransport that no more candidates are to arrive and thus you are free to go into the completed state and clean up and resources.
@ibc we will post this to the list too, just capturing as an issue. There is "some" value to the completed state because some implementation can know it's safe to shutdown non used candidates (like turn) when completed.
Clarified onerror usage in sender and receiver objects, as noted in:
Clarified SST-MS capability issue noted in:
Clarification of send() and receive() usage as noted in:
Changed ICE state diagram as noted in:
Removed getParameters methods and changed send() method as noted in:
Changed definition of framerateScale and resolutionScale as noted in:
Substituted "muxId" for the "receiverId" as noted in:
Clarified the setting of track.kind as described in:
Added SSRC conflict event to the RTCRtpSender, as described in:
Addressed the "end of candidates" issues noted in: