Update the sdp field in the RTCIceCandidate class to candidate #227
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During actual development, we discovered that an incorrect field description caused the backend to return an incorrect
ice-candidateto the frontend. This prevented the frontend from correctly initiating a connection request to the backend, resulting in a failed WebRTC connection establishment.We tested this using the Go language's Pion component and found that it connected successfully. Comparing the message packets revealed the issue was with the field name.
Below is a packet capture. You can see that using the Pion component, the frontend quickly initiates a connection request to the backend, while the WebRTC-Java component does not initiate any requests. After manually changing the
sdpname tocandidateon the frontend, the request could be initiated correctly.