Re: [webrtc-pc] Clarify a=ssrc attributes when track is changed/removed (#2783)

> there's no mention so far of failure to interop with a remote endpoint that removes a=ssrc when a=inactive. Is there an interop problem here with Chrome and Firefox, for example?

I think this is just my poor writing at work, but it is mentioned. From the OP:

> Further, when offering an m-line that removes these a=ssrc attributes for inactive m-lines and then adding them back with a direction of sendonly Chrome fails to restart the video streams(it logs "VideoReceiveStreamInterface not connected to a VideoSink."). Firefox correctly restarts these streams.

In fact the reason for I created this issue is that I noticed that webrtc-rs, which I'm working on, does not include the any `a=ssrc` lines when a sending track has been removed and it causes Chromium browser to fail to resume the video stream when reinstating the track. I'm not sure about Firefox and Chrome interop, but it's a good question

GitHub Notification of comment by k0nserv
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Monday, 31 October 2022 19:03:17 UTC