RE: No receiver reports for inbound sessions.

Hi,

>I assume that by inbound sessions you mean sessions which do not send packets/do not have destinations. Please, correct me if I'm wrong.

Yes, I separate the concept of inbound (only receive RTP packets, no destinations) and outbound (only sends RTP packets, have destinations) sessions.

>Um, right now I think this is a big bug. And yes, I would say it is enough to look at the list of sync sources. In that case I think >>sending RRs to data sinks who are not sending data packets would be delayed until the first RTCP packet is received from them (and a sync. source object is created). Looks like it is the desired behavior though, and anyway it's a secondary detail, I'll have a look at the >standards to see if there is any recommendation on this.

Well, it does make sense to always sent RR to valid Sync. Sources, and to them only. I haven't found anything I can refer to in the standards so far. If you find anything, please let me know. Meanwhile, I'll loop over all Sync. Sources.

-Jörgen