rtpsession: receiving own RTCP packet triggers SSRC reset (multicast)
When using multicast, rtpsession will handle the RTCP packets it receives from itself. As a result, it will conclude that a sender is on the network with the same SSRC (collission detection) and will trigger an SSRC rotation on the payloader.
This was detected with rtpsink, but I remember fixing this issue some time ago with using rtpsrc too.
0:00:34.327905772 3455462 0x7f5c6c06b520 DEBUG rtpsession rtpsession.c:3035:rtp_session_process_rtcp: received RTCP packet
0:00:34.327952247 3455462 0x7f5c6c06b520 DEBUG rtpsession rtpsession.c:2424:rtp_session_process_sr: got SR packet: SSRC 5b942eaf, time 117:48:14.735605623
0:00:34.327975166 3455462 0x7f5c6c06b520 DEBUG rtpsession rtpsession.c:1703:check_collision: Collision for SSRC 5b942eaf from new incoming packet, change our sender ssrc
0:00:34.327997084 3455462 0x7f5c6c06b520 DEBUG rtpsource rtpsource.c:1300:rtp_source_mark_bye: marking SSRC 5b942eaf as BYE, reason: SSRC Collision
0:00:34.328074452 3455462 0x7f5c6c06b520 DEBUG GST_EVENT gstevent.c:310:gst_event_new_custom: creating new event 0x7f5c600054b0 custom-upstream 69121
Seems to be related to this issue: #568 (closed)