We use jitsi-videobridge (1077) and we create the offer for our peers.
If we put transport-cc (https://tools.ietf.org/html/draft-holmer-rmcat-transport-wide-cc-extensions-01) in the sdp then the video is laggy and has a higher latency compared to if we do not put it in the sdp. The video is a screenshare between Chrome and Chrome. If the two peers communicate peer-to-peer (with transport-cc) then the video is the same like without transport-cc at jitsi-videobridge, fine.
The same happens for older jitsi’s (for example 879, where I guess there is no transport-cc support yet, are the unknown rtcp-packets/header-extensions dropped in this case or just forwarded, I don’t know) as well.
Do you have a guess why could this happen?