Comment # 2
on bug 9643
from Robert Gahan
Hi Pascal,
Thanks for your reply. I did not spot that option before.
However, I am unsure of what the implications of setting
that option might be for a large capture where multiple
network nodes are being traced (with different application
context versions).
The idea behind my change is that opcode 46 (mo-ForwardSm)
was only introduced in MAP phase 3 and does not exist in previous
phases.
So if the application context is absent, and opcode 46 is
used perhaps then we can decode as a MO-FSM-V3.
(As opcode 46 is only associated with V3).
If application context is present but set to 1 or 2 ,
and opcode = 46, then I guess this is an error according
to the specifications (and a FSM decode should
not be attempted ??)
[ As an aside, when the dialogue/portion is absent,
could wireshark used TCAP OTID/DTID to glean the
application context from a previous packet ?? - I am
not too sure if this feasible/realistic]
Regarding "If version 3 is widely used and v1/v2 are obsolete,".
>From what I have seen, V3 is certainly most popular but I guess there is legacy
v1 infrastructure and I have (or am about to) log some V1 related decoding
bugs.
You are receiving this mail because:
- You are watching all bug changes.