Wireshark-bugs: [Wireshark-bugs] [Bug 9564] ISUP(ANSI) Backwards Call Indicators decoded incorre
Evan Huus
changed
bug 9564
What |
Removed |
Added |
Status |
CONFIRMED
|
INCOMPLETE
|
CC |
|
eapache@gmail.com
|
Comment # 3
on bug 9564
from Evan Huus
Hi Geoff, sorry for the delays. If you want to help us improve the decoding
there are a few things that will help:
Use a build from Wireshark trunk (download from
https://www.wireshark.org/download/automated/) so that you have the absolute
latest changes (some of the issues may already have been fixed).
For packets that are decoded wrong, attach a capture (which you already have)
and provide a packet number, which bytes are wrong, and how they ought to be
decoded. Since it sounds like you know enough C to navigate the source,
approximate line numbers or function names would help too :)
In this particular case I am not too familiar with the protocol, but there are
both ANSI and ITU specs we may have to decode. Is there potentially a problem
with recognizing which one we should follow, or is that already a preference or
encoded in the packet somewhere? I don't want to break ITU decoding while
fixing ANSI decoding.
Thanks,
Evan
You are receiving this mail because:
- You are watching all bug changes.