Wireshark · Wireshark-users: Re: [Wireshark-users] Dissector for ANSI TCAP NATIONAL code:0 not implemented. Contact Wireshark dev

[Anders Broman <a.broman@xxxxxxxxx>]

I think the problem is related to bug https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4466
e.g Request/response matching
Regards
Anders
Martin Visser skrev 2010-08-28 14:49:

I suspect anything missing in Wireshark for TCAP is because you haven't written the dissector for it yet, Felice ;-)

Seriously, though  if you want to see a feature added you probably should submit a feature request via http://bugs.wireshark.org with a sample .pcap file.

Regards, Martin

MartinVisser99@xxxxxxxxx

On Fri, Aug 27, 2010 at 8:17 AM, Felice Mastrostefano <felice@xxxxxxxxxxxxxxxxx> wrote:

Hello Community,

If I understand correctly Wireshark is not capable of decoding ANSI MAP responses to, for example, Authentication Request Invoke and Registration Notification Request Invoke because these responses don't include an operation code specifying the type of response.

I may be missing something but why not correlate the TCAP response to the TCAP request using the identifier in order to determine the type of response? Any idea why this isn't supported in Wireshark today?

Thanks,
Felice M.

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe