I am trying to analyse a problem with H264 data over RTP when using FU-A fragmentation. Sometimes wireshark can decode the first 3 fields in the packets and sometimes it can't. I think that the problem is likely in my data, not wireshark because all of the h264 packets in a given file with either decode or not. I have manually decoded several of the fields in packets that fail to decode and they seem correct. How can I track down the origin of this problem? Thank you, Chuck Crisler asked 15 Jan '14, 07:02  ChuckCrisler |
This is a static archive of our old Q&A Site.
Please post any new questions and answers at ask.wireshark.org.
Hi, Wireshark does not do H.264 reasembly so it's not unlikly that it's a Wireshark bug. As far as I remember wireshark should not try to dissect h.264 unless it starts with a NAL unit identifier or somthing like that. You could open a bug report and attach a sall sample trace.