New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTCIceTransport 'failed' state #199
Comments
disconnectedThe RTCIceTransport has received at least one local and remote candidate, and a local and remote RTCIceCandidateComplete dictionary was not added as the last candidate but all appropriate candidate pairs thus far have been tested and failed (or prior obtained consent was removed). Other other candidate pairs may become available for testing as new candidates are trickled thus the transport is not failed yet. failedA local and remote RTCIceCandidateComplete dictionary was added as the last candidate to the RTCIceTransport and all appropriate candidate pairs have been tested and failed. . |
Added the "failed" state to RTCIceTransportState, as noted in: Issue #199 Added text relating to handling of incoming media packets prior to remote fingerprint verification, as noted in: Issue #200 Added a complete attribute to the RTCIceCandidateComplete dictionary, as noted in: Issue #207 Updated the description of RTCIceGatherer.close() and the "closed" state, as noted in: Issue #208 Updated Statistics API error handling to reflect proposed changes to the WebRTC 1.0 API, as noted in: Issue #214 Updated Section 10 (RTCDtmfSender) to reflect changes in the WebRTC 1.0 API, as noted in: Issue #215 Clarified state transitions due to consent failure, as noted in: Issue #216 Added a reference to [FEC], as noted in: Issue #217
Spec does not have an
RTCIceTransport
state offailed
which exists both in the ICE RFC and trickle ice. We do have adisconnected
state.The text was updated successfully, but these errors were encountered: