On 6/20/2016 10:16 AM, COHEN, HARVEY S wrote:
Wireshark does a pretty good job decoding T.38 that contains non-ECM T.30.
For T.38 with ECM T.30, Wireshark tries to interpret image data as T.30 protocol messages, creating something of a mess and confusing unwary users.
Harvey S. Cohen
Office +1-732-420-4099
Mobile +1-908-768-5833
Please file a bug report at bugs.wireshark.org and attach a capture file
showing the problem.
(If needed you can mark the bug a private to restrict access to the
capture file to only the Wireshark core developers).
Thanks
P.S. I've created a separate subject for this thread.
