RTCP failure handling about uvgrtp

[wowaser]

Do you mean a sort of timeout mechanism that will drop the participant after it has been unresponsive N seconds?

[jrsnen]

@wowaser something like that. Based on your comment from #180:

When one side crashes and is restarted, the RTCP goes crazy. Functionally, RTP and RTCP still work, because they are connectionless. This is because when restarted, the stream gets new random SSRC and starts sending RR/SR and other RTCP packets with that SSRC. If the receiver is restarted, the sender side spams this (the "new" incomplete participant does not have a socket allocated): If the sender is restarted, the receiver side spams this:

In both cases, the RTCP thread on the receiver side never exits, even after destructors are called and everything goes out of scope.

This situation could most likely be handled better. I have not fully investigated all the issues related to this.

[wowaser]

Well, the one with sockets happens because the participant is added not on stream initialization, but as a "dummy" after the RR/SR from it is received. So no sockets have been created for that SSRC and it starts complaining about that

[tampsa]

Fixed by 767c504