>
> So the right place for it would be "File->Export->PDML" in the menu, but
> this would require implementing a new dialog (with packet range
> selection and such like in the print dialog).
>
> Regards, ULFL
>
> BTW: what are you doing with the PDML output when you have generated it?
>
Hi,
Yes I agree, File->Export->PDML would probably be the best alternative, but
Print dialogue would be OK as a temporar solution at least.
The first thing I used PDML for was in order to post-process T.38 Fax
captures (T.30 signalling and T.4 picture data) in a very simple program.
The program dumps the T.4 picture data into a file and then I can use e.g.
fax2tiff (libtiff) to convert it to a TIFF picture (and then into
a PDF document if I want). The program uses the T.30 signalling to know if
the data is 1D/2D/... coded and so on.
I have started a bit to make a program that should be able to generate
different type of statistics for different protocols and so on.
The program uses configuration files that specifies the fieldnames I'm
interested in, some simple rules (e.g. based on field values) and so on.
The program doesn't know anything about SIP/H.323/..., but with a certain
configuration file I can get it to dump certain fields for each SIP-call (or
a specific call or calls matching a certain rule) e.g. in a CVS file or to
calculate certain kind of statistics for the calls.
The program is very very very limited right now (haven't had almost any time
to work on it yet), but anyway really useful in some cases.
There are several other simple programs/scripts that I have made earlier
that uses the tethereal summary printout and or the
hex output, or the detailed printouts, or ....
In future I intend to use PDML/PSML instead for some of those.
-Call-flow/Sequence-diagram tool (I have mainly used it for H.323/SIP but
it can be useful for many other protocols)
-External decoding for H.245/H.225/... PDUs (I used it often earlier when
H.323-plugin had problems with certain messages + nonStandardData)
and a lot more ...