|
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.
Hi,
I have checked in the new asn2eth
generated TCAP dissector please try it out.
Best regards
Anders
| 
