https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4526
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jeff.morriss.ws@xxxxxxxxx
Resolution| |FIXED
--- Comment #6 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2011-08-09 18:46:24 PDT ---
Actually the TCAP persistentdata stuff stores ACNs for situations just like
this.
The problem here, though, is that while the BEGIN goes from PC 5370->5354, the
CONTINUE comes back from 5352->6031. The 3rd message (2nd CONTINUE) then goes
from 5370->5352. The result is that the persistentdata stuff (when enabled in
the TCAP preferences) doesn't match the messages together.
Starting some time ago (r33097, present in 1.6.0), the SCCP dissector gained a
preference to set the source and destination GT addresses. That helps in
situations like this: the GT addresses on both sides are stable and with that
preference enabled, the 3rd frame is correctly dissected (as a v3 SMS).
So: enable the SCCP preference to set the GT addresses and enable the TCAP
preferences for persistentdata.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.