Christophe,
This packet looks very odd. Upon closer inspection I suspect some code
incorrectly translates the address from WAP Puah format (as used over PAP)
to MSISDN format: take a closer look at the extraneous string "/TYPE=PLMN"
after the trailing zero octet.
Probably this is a capture of a prototype system. Anyway, the 500 server
error in packet 114 confirms my findings (malformed MMSE packet). Try fixing
that address isssue, and then perform another capture. Hopefully that one
will yield positive results!
Best regards,
Olivier
----- Original Message -----
From: ronnie sahlberg
there were a couple of things wrong in the dissector which caused it
to dump core.
i have checked in fixes for the dissector so it does not dump core any
more.
thanks for the example capture.
On Tue, 21 Dec 2004 16:24:23 +0100, CHARBONNIER Christophe
Christophe Charbonnier wrote:
Hi everyone,
I have a MMSE transaction which makes (t)ethereal to stop on an
assertion:
========================================================================
=======
** ERROR **: file proto.c: line 1296 (proto_tree_add_string): assertion
failed: (hfinfo->type == FT_STRING || hfinfo->type == FT_STRINGZ)
========================================================================
=======
With some little investigations, I figured out that hfinfo->type is set
to 15 (FT_ABSOLUTE_TIME [date/time]) on this particular frame (number
112). The assertion is then understood.
But why is this packet wrong ??
Could some-one tell me more about it ???
The capture-file is attached...
Thank you for your help
Christophe