Ethereal-dev: RE: [Ethereal-dev] items with and without filterable fields in H.248

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Anders Broman (AL/EAB)" <anders.broman@xxxxxxxxxxxx>
Date: Thu, 12 May 2005 13:14:53 +0200
Hi,
I had a quick look at a sample I have and could not see the problem. can you send me a file with the problem so I can have a look.
Best regards
Anders

-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx]On Behalf Of LEGO
Sent: den 11 maj 2005 18:46
To: Ethereal development
Subject: [Ethereal-dev] items with and without filterable fields in
H.248


While analyzing some traces containing BER encoded H.248 I noticed
that some items are not added to the tree the same way for every
packet.

For instance, in transactions initiated by the MGC the transactionId
is filterable while it is not for those initiated by the MGw. They are
both parsed correctly but just some ones are filterable. Something
similar happens to terminationIds  for some types of terminations they
are filtrable for some others they aren't.

I'm interested in fixing this, but I don't have yet the knowledge
about asn.1 generated dissectors to cope with the issue. So, I have
some questions:

Why this could happen?
What should I be looking for in order to fix it?

Thanks,

Luis

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev