Wireshark-bugs: [Wireshark-bugs] [Bug 12958] Wrong JSON format returned by new -T json feature
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 18 Nov 2016 13:14:03 +0000

Comment # 6 on bug 12958 from 
Hi !
I found the same issue for SIGTRAN traces where we have piggybacking. In our
case, multiple gsm_map and tcap parts.

I don't think that using an array would be feasible in this case. For TCAP/MAP
messages, the MAP part isn't necessary. Some TCAP Abort messages do not contain
MAP while Begin/Continue/End do.

This means that when having multiple messages in one packet and a TCAP Abort in
its middle, transforming gsm_map and tcap key/values into two arrays would
result in indexing mismatch between gsm_map and tcap arrays that would make
correspondence between the two layers impossible.

The safest way for TCAP messages would be to insert the gsm_map dictionary
inside the corresponding tcap (the one which is just before) and create a tcap
array to avoid duplicates.

I'm anonymizing an example packet before attaching it

You are receiving this mail because:
  • You are watching all bug changes.