Hi Anirudh,
On Wed, Mar 11, 2020 at 08:21:18AM +0530, Anirudh Agarwal wrote:
> Hello everyone,
> First I would like to introduce myself, I am Anirudh Agarwal, a B.Tech 3rd
> year computer science student from the college IET Lucknow, India. I am
> interested in the project " WebRTC: DTLS-SRTP decryption and Opus playback
> support " for the GSoC '20.
>
> I have successfully created the build environment of the wireshark in my
> ubuntu 18.04.
>
> While I was exploring the bug
> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11723
>
> i encountered the RTP player was not able to play the audio even after
> re-opening it again and again. After reaching the state as shown in the
> screenshot, I clicked the play button but nothing happened. Am I doing
> something wrong or is it the bug which needs to be resolved.
If you scroll a bit to the right in the initial dialog (or resize the
window), can you see "22" in the Packets column? Following the steps in
Bug 11723, opening the VoIP calls dialog initially shows "11". When I
press "Play Streams", the contents will only appear once the column
reaches "22".
okay, I got this. The value of the packet switches to 22 from 11, and so on.
If I close the RTP Player dialog again, and press "Play Streams" again,
then the contents will be empty. I have not investigated why this
happens, but it might be related to some state in the dialog not being
cleared when the "tap" mechanism[1] used by the RTP player passed
through it. That could also explain the 11 -> 22 -> 33 -> ... Packets
bug. And yes, it is an open bug, feel free to investigate it and submit
a patch for it. :-)
In my case, when I press the "play stream", the RTP player screen pops up which is "unable" to play any kind of audio even at the first time, when the value of packets column becomes 22 from 11. Now is this happening only with me. After this I tried with the aaa.pcap sample packet also, the value of the "packet" column is changing randomly, and "RTP player is unable to play the stream" (not even the first time). Is the RTP player thing is happening just with me, is there anyone who is also working on the same bug?
[1]: https://gitlab.com/wireshark/wireshark/-/blob/master/doc/README.tapping
--
Kind regards,
Peter Wu
https://lekensteyn.nl
