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
The logs seem ok but no video is exchanged between the two peers, the left side shows the localstream but the right side only shows a black canvas when hitting the call button.
I see that you tied this issue to an ipv6-only problem we've seen in other contexts.
Can you possibly share the result of running "ip addr" (linux) or similar commands for other OSes so that we can see what interfaces and addresses are available?
This is likely a Chrome bug, not a bug in the page; if verified, we'll probably move this to crbug.com.
I'm not sure how to run that command on Android but if I check in the device settings I can see that there are 4 addresses listed: 3 IPv6 addresses (one of them link-local f80:...) and one IPv4 (the device ip address on the local network)
Please read first!
Please use discuss-webrtc for general technical discussions and questions.
Note: If the checkboxes above are not checked (which you do after the issue is posted), the issue will be closed.
Browser affected
Chrome (83.0.4103.106) on Pixel 4a
Description
running the perfect negotiation does not give expected results, although the logs seem correct no remoteVideo is rendered on either polite or impolite peer side
https://webrtc.github.io/samples/src/content/peerconnection/perfect-negotiation/
Steps to reproduce
Start both peers connection and swap the sending track
Expected results
additional remote video element is added next to local video elements
Actual results
only local video elements are displayed, no additional element added
The text was updated successfully, but these errors were encountered: