ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 2560] editcap -c option drops data

Date: Thu, 22 May 2008 22:24:54 -0700 (PDT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2560





--- Comment #1 from Jaap Keuter <jaap.keuter@xxxxxxxxx>  2008-05-22 22:24:52 PDT ---
So, I guess the call setup information is in the first file, together with the
properly decoded RTP/RTCP data. While in the second file there is only RTP/RTCP
data?

What happens is that Wireshark learns from the call setup information what UDP
packets to interpret as RTP/RTCP. If you load the second file, it can't learn
that since there's no call set info, so it stops at the UDP layer.

What if you go into the protocol preferences for RTP/RTCP and enable "Try to
decode RT(C)P outside of conversations". Does it now show your RTP/RTCP
packets? 


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.