Andreas Fink wrote:
On 19.04.2006, at 04:40, Jeff Morriss wrote:
[...]
Similar problem I'm having if I try to filter using mtp3 pointcodes.
They are displayed in ITU format X-XXX-X but I cant enter them like
this, I must enter them in 14 bit numerical value (which requires
external translation by hand).
They should also be displayed on decimal, at least in the MTP3
dissector (something like "Originating Point Code NNNN (X-XXX-X)".
It does at some places. It does not in the summary list when you filter
for MTP3 (the places where you would see source IP/destination IP) is
the popupated with ITU formatted pointcodes. It also does not in MTP3
management messages like a Routing update (TFP or TFA). That's the part
where you really want to see both formattings. Probably easy to fix but
my first attempt to play with dissector source resulted in a crash :-/.
If you mean MTP3MG not displaying the structured format, that's been
fixed in SVN (see bug 332:
http://bugs.ethereal.com/bugzilla/show_bug.cgi?id=332 )
Yes, this is one of the problems with the dissection of MTP3 point
codes: the structured MTP3 point code string is only appended to the
point code item, it is not added as a filterable field (except in ANSI
and China ITU where the PCs are always formatted as a 8-8-8 string).
(Another problem is that not all dissectors show you the structured
format.)
Ok so we should add this to the "todo" list. Might do it myself once I
figure out on how to write dissectors properly. EMI/UCP is also a
missing one I wanted to add.
It's been on my list of things to do for a while but I hate
cut-n-pasting code so I keep trying to come up with One Big Function
that will do it all and handle all the cases but then I keep getting
interrupted before I can find an elegant solution.