is it proto_reg_handoff_xxx (ok) or just proto_reg_handoff (won't do) ?
On Wed, Mar 12, 2008 at 1:22 PM, <atdev.queries@xxxxxxxxx> wrote:
> Hi,
>
> I had already included the packet_x.c in Makefile.common and also tried "rm epan/dissectors/register.c" but no luck. The proto_register_xxx function is working fine, but proto_reg_handoff is not.
>
>
> ________________________________
>
> From: wireshark-dev-bounces@xxxxxxxxxxxxx on behalf of Luis EG Ontanon
> Sent: Wed 3/12/2008 5:11 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Unable to register over TCAP
>
>
>
>
>
> have you added your packet-x.c file to Makefile.common ?
>
> if so, try "rm epan/dissectors/register.c" and make again.
>
>
>
>
> On Wed, Mar 12, 2008 at 11:33 AM, <atdev.queries@xxxxxxxxx> wrote:
> >
> >
> > Hi all ,
> >
> > I have written a dissector ( ASN.1 format), which runs over ETSI-TCAP.
> > Now,this dissector has an SCCP sub-system number.In general , the
> > sub-dissectors running over ITU-TCAP( eg : camel , GSMMAP) are registered in
> > the following way:
> >
> > In the proto_register_xxx(void):
> >
> > range_convert_str(&global_ssn_range, "6-9", MAX_SSN);
> > ssn_range = range_empty();
> > prefs_register_range_preference(xxx_module, "tcap.ssn", "XXX SSNs", "TCAP
> > Subsystem numbers used for XXX", &global_ssn_range, MAX_SSN);
> >
> > In proto_reg_handoff_xxx(void), we use:
> >
> > if ( !xxx_initialised)
> > {
> > }
> > else{
> > range_foreach(ssn_range, range_delete_callback);}
> > ...
> > ssn_range = range_copy(global_ssn_range);
> > range_foreach(ssn_range, range_add_callback);
> >
> > For a dissector having SCCP SSN, we use :
> >
> > dissector_delete("sccp.ssn", SCCP_SSN_XXX, xxx_handle);
> > dissector_add("sccp.ssn", SCCP_SSN_XXX, xxx_handle);
> >
> > Now I am not able to register either ways . Proto_reg_handoff_xxx is not
> > getting called at all.
> > Can somebody please help me ??
> >
> > The information contained in this electronic message and any attachments to
> > this message are intended for the exclusive use of the addressee(s) and may
> > contain proprietary, confidential or privileged information. If you are not
> > the intended recipient, you should not disseminate, distribute or copy this
> > e-mail. Please notify the sender immediately and destroy all copies of this
> > message and any attachments.
> >
> > WARNING: Computer viruses can be transmitted via email. The recipient should
> > check this email and any attachments for the presence of viruses. The
> > company accepts no liability for any damage caused by any virus transmitted
> > by this email.
> >
> > www.wipro.com
> > _______________________________________________
> > Wireshark-dev mailing list
> > Wireshark-dev@xxxxxxxxxxxxx
> > http://www.wireshark.org/mailman/listinfo/wireshark-dev
> >
> >
>
>
>
> --
> This information is top security. When you have read it, destroy yourself.
> -- Marshall McLuhan
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
>
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>
> www.wipro.com
>
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
