GStreamer based webkit2gtk fails with `Incoming unhandled RTCP ssrc(...), on_track will not be fired`

[paultag]

Thank you for maintaining webrtc-rs! We really appreciate your work over at Zoo/@KittyCAD.

I've hit an issue that's a bit outside my ability to instrument at the moment, I couldn't find a related issue on this repo, and have only found one related isue on pion/webrtc that was fixed in Feb 2020 that I don't fully understand the mechanics of yet.

I've been trying out webkit2gtk (both through tauri and directly) to see if I can get a good negotiation with a webrtc-rs backend.

I'm going to do some investigation to try and narrow this down a bit more, but in case anyone else has hit this same issue, or someone otherwise recognizes whats going on, we'd be very interested in contributing back a fix.

  2024-02-14T18:28:51.053423Z  WARN webrtc::peer_connection::peer_connection_internal: Incoming unhandled RTCP ssrc(3057885015), on_track will not be fired
    at /home/paultag/.cargo/registry/src/index.crates.io-6f17d22bba15001f/webrtc-0.9.0/src/peer_connection/peer_connection_internal.rs:322


  2024-02-14T18:28:55.081505Z  WARN webrtc::peer_connection::peer_connection_internal: Failed to accept RTCP SessionSRTP has been closed
    at /home/paultag/.cargo/registry/src/index.crates.io-6f17d22bba15001f/webrtc-0.9.0/src/peer_connection/peer_connection_internal.rs:318

Thanks again for all you do! This library is great!

[rainliu]

Do you have code example? Peer connection should add track or transceiver before setRemoteDescription.

[tfoldi]

I have the same issue. I put together a client code where I can reproduce the issue, however, I do not access the server side.

the log and program are here:

https://gist.github.com/tfoldi/270ddfdf919bf035cd96652d4bb03622

(I found what my issue was. Even if answer offered video stream, it required some authentication on the data channel before it actually opened the connection)

[rainliu]

Just one unhandled RTCP doesn't mean an issue. Most likely remote accepted offer SDP, after sent back answer SDP, then immediately start to send RTCP packets before local receives answer SDP and setRemoteDescription.

webrtc/src/peer_connection/peer_connection_internal.rs:322 [WARN] 20:15:25.873716 - Incoming unhandled RTCP ssrc(305150496), on_track will not be fired

[paultag]

Closing this issue; I never tracked it down to a specific acute cause; this is a mix of other (non-webrtc-rs) causes