Re: Wireshark-users Digest, Vol 121, Issue 6

["COHEN, HARVEY S" <hc2182 () att com>]

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

-----Original Message-----
From: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] On Behalf Of 
wireshark-users-request () wireshark org
Sent: Thursday, June 16, 2016 8:00 AM
To: wireshark-users () wireshark org
Subject: Wireshark-users Digest, Vol 121, Issue 6

Send Wireshark-users mailing list submissions to
        wireshark-users () wireshark org

To subscribe or unsubscribe via the World Wide Web, visit
        https://wireshark.org/mailman/listinfo/wireshark-users
or, via email, send a message with subject or body 'help' to
        wireshark-users-request () wireshark org

You can reach the person managing the list at
        wireshark-users-owner () wireshark org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Wireshark-users digest..."


Today's Topics:

   1. Re: Decoder for T.38 (Fax over IP) (Jeff Morriss)


----------------------------------------------------------------------

Message: 1
Date: Wed, 15 Jun 2016 11:40:26 -0400
From: Jeff Morriss <jeff.morriss.ws () gmail com>
To: Rayne <hjazz6 () ymail com>,  Community support list for Wireshark
        <wireshark-users () wireshark org>
Subject: Re: [Wireshark-users] Decoder for T.38 (Fax over IP)
Message-ID:
        <CAKkq+FZG=+JU-8CoDc+W81BAb9+M9BjcRw61FmGmruBvghbSZg () mail gmail com>
Content-Type: text/plain; charset="utf-8"

On Wed, Jun 15, 2016 at 1:50 AM, Rayne <hjazz6 () ymail com> wrote:

> Hi all,
>
> I noticed that "t38" and "t30" can be used as a filter in Wireshark 
> 1.10.5, but I can't seem to find the source code for how such packets 
> are decoded. (I can only find t35.c and t35.h in the epan directory).
>
> So my question is can Wireshark actually detect then decode such packets?
> If so, where can I find the source code for it?
Look in epan/dissectors/packet-t38.c (and packet-t30.c).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.wireshark.org/lists/wireshark-users/attachments/20160615/b229d890/attachment.html>

------------------------------

_______________________________________________
Wireshark-users mailing list
Wireshark-users () wireshark org
https://wireshark.org/mailman/listinfo/wireshark-users


End of Wireshark-users Digest, Vol 121, Issue 6
***********************************************
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe