These ares my questions on the whireshark :
- is there any possibility to know on which ITU, ETSI, 3GPP
recommandations releases have been coded the dissectors to be used for
MAP, CAMEL, ISUP, BSSMAP, RANAP, etc.. Application Parts ?
For the most part, the versions used by the dissectors are listed in the
header of each source file. For example, you can read at the top of the
GSM-MAP dissector:
http://anonsvn.wireshark.org/viewvc/viewvc.py/trunk/epan/dissectors/packet-gsm_map.c?view=markup
* References GSM MAP:
* ETSI TS 129 002
* Updated to ETSI TS 129 002 V7.5.0 (3GPP TS 29.002 V7.5.0 (2006-09) Release 7)
* Updated to ETSI TS 129 002 V8.1.0 (3GPP TS 29.002 V8.1.0 (2007-06) Release 8)
* References GSM SS
* References: 3GPP TS 24.080
For dissectors generated from the ASN.1 source (such as GSM MAP) you can
check the ASN source, too:
http://anonsvn.wireshark.org/viewvc/viewvc.py/trunk/asn1/gsmmap/GSMMAP.asn?view=markup
- The K12 Tektronix analyzer give us the way to build ourself the
protocol stack corresponding to a specific GSM.xx or TS.xx
recommandation release ! Is it possible to add in your project a tool to
manage these protocol stacks, specialy because, for training and
pedagogic objectives, it should be nice to control exactly the output of
a trace decoding ?
Do you mean using specific versions of each protocol with some specific
version of another protocol?
Wireshark could support that as each protocol dissector can have
preferences to choose what standard/spec it uses--this is especially
prevalent in the SIGTRAN dissectors which support several I-D's and the
RFC version. AFAIK among the SS7 dissectors only the MTP3 dissector has
a choice of standards: ITU, ANSI, Japanese, and Chinese though this
choice then affects many of the other dissectors (e.g., ISUP, SCCP).
Oh, I guess TCAP does support both the ANSI and ITU variants but it
chooses the variant automatically.
