Ethereal-dev: [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 Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: LEGO <luis.ontanon@xxxxxxxxx>
Date: Wed, 11 May 2005 18:46:16 +0200
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