Ethereal-users: RE: [Ethereal-users] GSM MAP SMS decode

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "John Vincent" <jpv@xxxxxxxxxxx>
Date: Tue, 16 Aug 2005 12:22:38 +0200
Hi Anders,

I just downloaded the snapshot build 0.10.12-SVN-15374 and your fix seems to work perfectly.

I didn't check every bit and byte, but I tried a few different GSM-MAP traces I have on file (SMS traffic) and
they all seemed to decode fine.

Thanks once again for your help.

/John.

-----Original Message-----
From: Anders Broman [mailto:a.broman@xxxxxxxxx]
Sent: Monday, August 15, 2005 9:42 PM
To: jpv@xxxxxxxxxxx; 'Ethereal-Users@Ethereal. Com'
Subject: SV: [Ethereal-users] GSM MAP SMS decode


Hi,
The problem was that the TP-Parameter-Indicator is "4) Mandatory if any of
the optional parameters following TP-PI is present, otherwise optional." And
a check whether the parameter was there or not was missing.
I have checked in a fix, please check it with your traces.
Brg
Anders

-----Ursprungligt meddelande-----
Fr�n: John Vincent [mailto:jpv@xxxxxxxxxxx]
Skickat: den 8 augusti 2005 15:51
Till: Anders Broman; Ethereal-Users@Ethereal. Com
�mne: RE: [Ethereal-users] GSM MAP SMS decode

Hi Anders,

I guess you're away this week, so you'll read this when you're back... I
hope you had a good holiday :-)

Your fix for UCS2 GSM SMS messages works. Thanks again.

There is another error that also produces the [Malformed Packet: GSM SMS]
message, which I think is caused by
the SMS decoder over-running the end of the SCCP packet (but I haven't
looked at the code).

The trace I sent you already contains examples of these decoding errors. As
far as I can see, the error only
occurs with the SMS-STATUS-REPORT pdu carried on GSM MAP over M3UA.

What seems to be happening is that the SMS-STATUS-REPORT can have optional
data at the end that is not present
in this trace, however the M3UA encapsulating protocol pads the packet to a
4-byte boundary. The
SMS-STATUS-REPORT decoder overruns the end of the SCCP packet and tries to
decode these padding bytes and
produces the error message when it fails to do so. (at least that's what it
looks like to me)

Thanks in advance,

/John.


-----Original Message-----
From: Anders Broman [mailto:a.broman@xxxxxxxxx]
Sent: Tuesday, August 02, 2005 11:32 PM
To: John Vincent
Subject: SV: [Ethereal-users] GSM MAP SMS decode


Hi,
I think I have "solved" the problem - [Malformed Packet: GSM SMS] part. The
text does not display though.
Brg
Anders

-----Ursprungligt meddelande-----
Fr�n: John Vincent [mailto:jpv@xxxxxxxxxxx]
Skickat: den 2 augusti 2005 17:08
Till: Anders Broman
�mne: [Ethereal-users] GSM MAP SMS decode

Hi Anders,

I attach a trace of GSM-MAP SMS using both UCS2 and 7-bit GSM alphabet,
carried on TCAP/SCCP/M3UA/SCTP/IP. The
trace was captured using tethereal's default format, and I've zipped it
using gzip, so it's not too big to
email.

Thanks for your interest.

/John.

>
>Hi,
>
>If you send me a trace I can try to have a look at the [Malformed Packet:
GSM SMS] part.
>
>Brg
>
>Anders
>





!DSPAM:4300efcc636512101111907!