Ethereal-dev: [Ethereal-dev] Re: Camel Patch

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: ronnie sahlberg <ronniesahlberg@xxxxxxxxx>
Date: Sat, 30 Apr 2005 15:03:19 -0400
you should not use   other_decode_bitfield_value(),

you should also use proper value_strings and not that switch()case construct.

then avoid using proto_tree_add_text()

packet-ansi_a.c is not a good example to build on. it is old and using
old outated apis.


do you have an example capture you can send me and a reference to that
spec  and i can implement it properly.



On 4/30/05, Javier Acuña <javier.acuna@xxxxxxxxxx> wrote:
> 
> 
> >The conformance magic for ReleaseCallArg is pretty big.
> >
> >Is it possible to refactor this and specify ReleaseCallArg in the ASN
> >file instead?
> 
> Hi, the cfn is indeed quite large. But according to the specification that
> I'm working with, ReleaseCall is an octet string encoded according to the
> "Cause" clause of ITU Q850.
> 
> ITU Q850 is specified in terms of bits and bytes. I don't know how to
> refactor something like that into ASN1, so please tell me any ideas you
> might have.
> 
> Best Regards
> Javier Acuña
> 
> 
> 
> 
> ________________________________________________________________
> 
> Mensaje enviado desde el Servicio Webmail del Dominio sixbell.cl
> 
> 
> 
>                   
> 
> 
> _____________________________
> La informacion contenida en esta transmision es confidencial, y no puede ser
> usada por otras personas que su(s) destinatario(s). El uso no autorizado de
> la informacion contenida en esta transmision puede ser sancionado. Si ha
> recibido esta transmision por error, por favor destruyala y notifique al
> remitente telefonicamente, con cobro revertido o via e-mail.
> 
> The information contained in this transmission is privileged, and may not be
> used by any person other than its addressee(s). Unauthorized use of the
> information contained in this transmission may be punished  by law.  If
> received in error, please destroy and notify the sender by calling collect
> or by e-mail.
> _____________________________
>