Ethereal-dev: Re: [Ethereal-dev] Doing some work with the TCAP dissector.
Tim wrote:
I have been working at converting the TCAP dissector to an ASN.1 based
dissector.
Great!
I have ITU variant working but it needs more work. At this time I need
some ANSI tcap traces to get the ANSI variant working. If anyone can let
me have some ANSI examples I could complete this work.
I'll see if I can find you some (clean) examples to send you off-list.
Incidentally I had an idea with the tcap sub-dissectors, like MAP, INAP,
CAMEL etc. Currently these are configured using the SSN field faked in
the TCAP layer. We need to keep this for traces without an application
context number, but a modification to the sub-dissectors to register
themselves against the application context number and get the TCAP
dissector to try both methods.
That is also a great idea. :-)
Another thing (on my to-do list) is to:
- Add an "Automatic" TCAP standard preference to the TCAP dissector;
when set to that decode the message as ITU if the message type is an ITU
one; if it's ANSI then decode it as ANSI (this is possible because the
message types are mutually exclusive)
- Make the TCAP dissector heuristic: if the message type matches the
configured (ANSI, ITU, or Automatic) standard then it's TCAP (RANAP is
already heuristic).
If you have time or are so motivated, those would also be welcome
changes. :-)
