The VideoLAN Forums

Hi Everyone,

I'm trying to capture RTCP packets using Wireshark on the server. I think I'm doing something wrong. Here is my setup: From a server laptop, I send two unicast, RTP streams (the same video) to two different ports (even numbered) on a client laptop. I'm using VLC 1.1.5 and the following command line on the server:

% vlc myvideo.wmv --sout #duplicate{dst=display, dst=rtp{dst=<client_ip>,port=1234,mux=ts}, dst=rtp{dst=<client_ip>,port=1236,mux=ts}}

I can see the video playing on the server as well as on two instances of the VLC client (by opening network streams on appropriate ports). So things are getting streamed on the two ports and are playing correctly. However, on the server laptop, I have setup Wireshark to receive RTCP packets (filtered from ip.src=<client_ip>), but I don't see anything. Why is that? Do I need to use RTSP to get the RTCP packets?

thanks,
Amit

I have the same problem!!
expecting someone to fix

VLC does not send RTCP-RR for TS streams, as it is completely useless.

Hi Remi,
Thanks for your reply. Would you be so kind to modify the command (or write a new one) I have in my post so VLC sends RTCP-RR packets?
thanks,
Amit

VLC does not send RTCP-RR for TS streams, as it is completely useless.

useless!!!! based on what....
if my vlc is a client and if i want to know what my server send to it. trust me it is really very usefull....

The feedback you would get for RTCP-RR is considered totally useless by my MPEG-TS experts. As far as I understand, RTP/TS is mainly multicast. And I agree with them that RTCP-RR is harmful rather than helpful in multicast scenarii. By the way, VLC is not the only RTP/TS receiver that does not implement RTCP-RR.

That being said, if you are not happy, you're welcome to sponsor the extra work needed, or do it yourself. The code is open-source.

The feedback you would get for RTCP-RR is considered totally useless by my MPEG-TS experts. As far as I understand, RTP/TS is mainly multicast. And I agree with them that RTCP-RR is harmful rather than helpful in multicast scenarii. By the way, VLC is not the only RTP/TS receiver that does not implement RTCP-RR.

That being said, if you are not happy, you're welcome to sponsor the extra work needed, or do it yourself. The code is open-source.

Dear Remi, I would like to but really i dont have enough time for it i mean for the contribution ....and unfortunality i am not that much good coder as much as you guys...
now! maybe I can explain my problem and you can give an answer with your experience... I am using vlc as a client and i want to control how many packet vlc is getting and how much it displays? and aother question is about if there is no EOF does it mean that vlc couldnt decode and display it... for the prediction i need to know and i supose that rtcp is the way i can solve thats why i was that much insist about the rtcp rr...if i know that rtcp rr (i mean the client . rtcp receive report I can get then i can do something for the rr results...)
thank you for the asnwe i hope i was not unrespectful because always i respect to people who are smart as much as you guys (vlc)

RTCP-RR does not do any of that. I don't think there is any way to do that with pure RTP/RTCP anyhow.