Hi, It would be good to have it possible in the future. E.g. it is possible for (I think quite similar) Q.932/QSIG. There are official QSIG opcodes implemented in the QSIG dissector and I have plugin with our extensions using its own opcodes.
Regards, Tomas -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anders Broman Sent: Wednesday, June 06, 2007 11:08 PM To: 'Developer support list for Wireshark' Subject: Re: [Wireshark-dev] how to make tcap subdissector in plugin Hi, I suppose this means you have to rebuild the complete MAP Dissector as a plugin adding your opcode(s) if the opcode isn't clashing with the existing ones perhaps it can be added to the existing MAP dissector. Why do you feel the you need to add private opcodes to MAP instead of using the existing ones adding extension containers for any private data needed or work with 3GPP to get the new opcodes you need added to MAP. Regards Anders -----Ursprungligt meddelande----- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För yin sun Skickat: den 5 juni 2007 21:13 Till: Developer support list for Wireshark Ämne: Re: [Wireshark-dev] how to make tcap subdissector in plugin It is a private opcode to MAP. /Yin On 6/5/07, Anders Broman <[EMAIL PROTECTED]> wrote: > Hi, > Is it a private opcode to MAP or something missing from MAP? > Regards > Anders > > -----Ursprungligt meddelande----- > Från: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] För yin sun > Skickat: den 5 juni 2007 20:59 > Till: Developer support list for Wireshark > Ämne: [Wireshark-dev] how to make tcap subdissector in plugin > > Hello developer, > > I have made the FooPage example working for plugin. Now I want to have > a plugin similar to GSM-MAP but as a plugin. Basically this plugin > will provide decoder for new opcode. The problem is, to register under > tcap I have to call add_itu_tcap_subdissector as I read from gsmmap > code. And this function is defined in dissectors.lib, which is not > visible to plugin. So the question is > 1. Can we in general make all the functions in dissectors accessible to > plugin. > 2. where should we draw a line between dissector and plugin. > > Thanks, > /Yin > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-dev > > _______________________________________________ > Wireshark-dev mailing list > Wireshark-dev@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-dev > _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
