Wireshark mailing list archives
Re: ANSI TCAP/ANSI MAP decode problem
From: "Anders Broman" <a.broman () telia com>
Date: Wed, 2 Dec 2009 20:37:19 +0100
Hi, In this case the source and destination in the reply does not match the Invoke: Invoke DPC: 214-20-20 OPC: 1-1-10 identifier: 00000100 ReturnResult DPC: 1-1-10 OPC: 214-190-1 <---------- identifier: 00000100 I suppose one could dissect all ReturnResults for certain ssn:s (preference) as an unknown ANSI MAP operation reply with all possible tags. (Nothing I plan to take on). Regards Anders -----Ursprungligt meddelande----- Från: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] För Michael Lum Skickat: den 2 december 2009 19:49 Till: Developer support list for Wireshark Ämne: [Wireshark-dev] ANSI TCAP/ANSI MAP decode problem <<err-ansi_map.snoop>> Here is another capture file containing ANSI MTP3/ANSI TCAP/ANSI MAP that does not dissect the return result. I keep getting complaints from users that Wireshark does not decode as well as Ethereal. I think this is a ANSI TCAP problem but I can't tell how it is supposed to match invokes with return results. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- ANSI TCAP/ANSI MAP decode problem Michael Lum (Dec 02)
- Re: ANSI TCAP/ANSI MAP decode problem Anders Broman (Dec 02)