no i havent done so....where is the rtp dissector preferences??? thanks
On 06/03/2008, Martin Mathieson <[EMAIL PROTECTED]> wrote: > > Did you turn on the RTP heuristic dissector in the RTP dissector > preferences? > > Could you possibly send a capture file? > > > On Thu, Mar 6, 2008 at 9:02 PM, Fabiana moreno <[EMAIL PROTECTED]> wrote: > > > Hey Martin i configured my client to listen to port 7070(udp) > > So, now in my captures i just see udp packets..that's fine > > But when i try to decode to rtp...there's the same error... > > i should be able to decode udp to rtp smoothly right? > > > > > > On 06/03/2008, Martin Mathieson <[EMAIL PROTECTED]> > > wrote: > > > > > > Yes, but have you tried to configure preferences in the RTSP client or > > > server to encourage it to use RTP over UDP instead (the RTSP protocol > > > allows > > > this). > > > > > > On Thu, Mar 6, 2008 at 10:52 AM, Fabiana moreno <[EMAIL PROTECTED]> > > > wrote: > > > > > > > That´s is the thing... i am not seeing any udp packets in my > > > > capture. just tcp and rtsp. > > > > Attached are the capture files(one .pcap and the other in text form) > > > > that includes RTSP signalling > > > > > > > > > > > > > > > > > > > > > > > > On 06/03/2008, Martin Mathieson <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > > Could you possibly post a capture file that includes the RTSP > > > > > signalling? > > > > > We should be configuring the RTP stream with the dynamic payload > > > > > type so that it can be displayed properly... > > > > > > > > > > > > > > > On Wed, Mar 5, 2008 at 11:08 PM, Fabiana moreno < > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > Well it's my final year project and i need to analyse the QoS > > > > > > parameters when streaming over wireless lan. > > > > > > I'm streaming an mpeg4 video from a server to my client (the > > > > > > last one is the one where wireshark is installed) > > > > > > So im trying to to capture all the packets im getting when > > > > > > streaming. > > > > > > My server supports rtcp/rtp and i think (correct me if im wrong) > > > > > > that the best way to analyse all these packets are to decode them > > > > > > to udp and > > > > > > then to rtp but im getting the problem mentioned before. > > > > > > > > > > > > But is there some way i can fix this? > > > > > > > > > > > > > > > > > > On 05/03/2008, Jaap Keuter <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > Well, I dont' really understand what you do, but the > > > > > > > PT=unknown is from the > > > > > > > fact that this packet type is dynamically assigned, negotiated > > > > > > > between > > > > > > > parties. If Wireshark doesn't see the negotiations, it can't > > > > > > > make out which > > > > > > > codec goes with PT 96. So yes, it can happen you see this. > > > > > > > > > > > > > > Thanx, > > > > > > > Jaap > > > > > > > > > > > > > > > > > > > > > Fabiana moreno wrote: > > > > > > > > hello!!! > > > > > > > > I'm streaming an mpeg4 video with darwin streamer server > > > > > > > trhough my > > > > > > > > WLAN. I'm using wireshark to analyse the packets im > > > > > > > receiving. > > > > > > > > I see TCP/RTSP packets but when i decode to UDP and then to > > > > > > > RTP to > > > > > > > > anlyse it, wireshark shows the following in all the packets, > > > > > > > here a sample: > > > > > > > > > > > > > > > > 34 0.253327 192.168.123.100 <http://192.168.123.100/> > > > > > > > > 192.168.123.101 <http://192.168.123.101/> RTP PT=Unknown > > > > > > > (96), > > > > > > > > SSRC=0x4B6C00C, Seq=65416, Time=1531529067 > > > > > > > > > > > > > > > > is this what i suppose to see? any suggestions in how to > > > > > > > analyse packets > > > > > > > > im receiving while streaming? please help!! im new > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Wireshark-users mailing list > > > > > > > Wireshark-users@wireshark.org > > > > > > > http://www.wireshark.org/mailman/listinfo/wireshark-users > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Wireshark-users mailing list > > > > > > Wireshark-users@wireshark.org > > > > > > http://www.wireshark.org/mailman/listinfo/wireshark-users > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Wireshark-users mailing list > > > > > Wireshark-users@wireshark.org > > > > > http://www.wireshark.org/mailman/listinfo/wireshark-users > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Wireshark-users mailing list > > > > Wireshark-users@wireshark.org > > > > http://www.wireshark.org/mailman/listinfo/wireshark-users > > > > > > > > > > > > > > _______________________________________________ > > > Wireshark-users mailing list > > > Wireshark-users@wireshark.org > > > http://www.wireshark.org/mailman/listinfo/wireshark-users > > > > > > > > > > _______________________________________________ > > Wireshark-users mailing list > > Wireshark-users@wireshark.org > > http://www.wireshark.org/mailman/listinfo/wireshark-users > > > > > > _______________________________________________ > Wireshark-users mailing list > Wireshark-users@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-users > >
_______________________________________________ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
