CloudWebRTC
CloudWebRTC
@renefloor thanks for pointing it out. Yes, this does cause some issues. In the recent update, I read the docs you linked, which will be of great help to the...
I retracted the latest version. and released `webrtc_interface: 1.2.2+hotfix.2` to make the historical version work. This will cause some dart analyzer warnings in `flutter-webrtc`, but will not affect compilation and...
the issue is caused by the mismatch of the `fmtp` parameters? `a=fmtp:107 level-asymmetry-allowed=1;packetization-mode=0;profile-level-id=42e01f`
Have you tried using vp8? It seems that your Android app did not reply with any valid H264 payload, so the negotiation is invalid. ``` m=video 9 UDP/TLS/RTP/SAVPF 0 c=IN...
so you need to confirm that the Android device has a valid H264 Codec
I think you need to connect to android studio for native code level debugging, make sure the HW codec is valid and registered to WebRTC EncoderFatctory.
The easiest way, you can create offer on android and check whether h264 is included in the SDP
Since wasm compilation errors prevent uploading to pub, this branch needs to be merged first. The current version can be compiled correctly with --wasm, but there are still bugs when...
484 may be related to the format of the SIP URI you called. Please make sure your URI is a reachable address.
https://github.com/webrtc-sdk/android/issues/7