Checked in with some checks on if (parameter_tvb).
Brg
Anders
-----Ursprungligt meddelande-----
Från: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] För Jacques, Olivier (OCBU-Test
Infra)
Skickat: den 8 juni 2005 14:34
Till: Ethereal development; tim@xxxxxxxxxxxxxxx
Ämne: RE: [Ethereal-dev] New asn.1 based TCAP dissector.
Thanks, it looks great now. This TCAP dissector is a great progress.
Here is an additional diff:
- beautify TCAP decoding without upper dissector associated.
Thanks,
Olivier.
> -----Ursprungligt meddelande-----
> Från: ethereal-dev-bounces@xxxxxxxxxxxx
> [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] För Tim
> Skickat: den 7 juni 2005 21:38
> Till: 'Ethereal development'
> Ämne: RE: [Ethereal-dev] New asn.1 based TCAP dissector.
>
> Here's a diff that fixes issues you have reported, let me
> know if you have any more problems.
>
> Tim
> -----Original Message-----
> From: ethereal-dev-bounces@xxxxxxxxxxxx
> [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of
> Jacques, Olivier (OCBU-Test Infra)
> Sent: 07 June 2005 08:54
> To: Ethereal development
> Subject: RE: [Ethereal-dev] New asn.1 based TCAP dissector.
> Hi,
>
> I just tried it with several traces I have. First, great job,
> the decoding looks really nice already!
>
> Here are my results:
> 1- All tests
> 1.1- In colinfo, the message type is not indicated
> (begin, continue, end, ...). This would be nice.
> 1.2- ITU/ANSI auto-detection works nicely. Still have to
> set the standard in MTP3 preferences.
> 2- TCAP ITU - Camel
> Works nicely.
> 3- TCAP ANSI
> 3.1 An ANSI MAP trace doesn't display a MAP tree on the
> GUI. MAP protocol goes directly in the component portion. I
> don't know if this is intended, but it's a little bit
> disturbing given that Ethereal always create a tree for a
> protocol layer. An ITU MAP works OK.
> -> see tcap_1.jpg
> 4- TCAP ITU - unknown upper protocol
> This time, no upper protocol is triggered. So TCAP
> dissector is on its own.
> 4.1- For a Camel trace (Camel dissector de-activated), I
> get BER errors and nothing is decoded. The expected behavior
> would be to have parameter types, length and value displayed
> (previous TCAP dissector was doing that)
> components:
> Item: invoke (1)
> invoke
> invokeID: 1
> BER Error: This field lies beyond the end
> of the known sequence definition.
> BER Error: This field lies beyond the end
> of the known sequence definition.
> Item: invoke (1)
> invoke
> invokeID: 2
> BER Error: This field lies beyond the end
> of the known sequence definition.
>
> I can provide the captures with a direct email.
>
> Regards,
> Olivier.
>
>
>
>
> From: ethereal-dev-bounces@xxxxxxxxxxxx
> [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Anders Broman
> Sent: mardi 7 juin 2005 07:55
> To: ethereal-dev@xxxxxxxxxxxx
> Subject: [Ethereal-dev] New asn.1 based TCAP dissector.
> Hi,
> I have checked in the new asn2eth generated TCAP dissector
> please try it out.
> Best regards
> Anders
>
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
