http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=35098
User: morriss
Date: 2010/12/01 03:26 PM
Log:
From Neil Piercy via https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3301 :
The information which is used to determine which sub-dissector to use for the
various Data messages within an SCCP connection is only present within the
initial Connection Request, so even with connection tracking on, unless the
trace contains the Connection Request no sub-dissector is called. It is common
for traces to only contain a single carried protocol anyway - e.g. RANAP.
The supplied patch adds a user preference for a "default payload"
sub-dissector, which is called in preference to the Data dissector if nothing
else has claimed the packet first.
Directory: /trunk/epan/dissectors/
Changes Path Action
+37 -13 packet-sccp.c Modified