Malformed packet in the GSM MAP

asked 2018-05-25 06:16:43 +0000

Hanosh
1 ●1 ●2 ●1

Hi,

We couldn't decode some GSM MAP packets in the wireshark.

Kindly check and revert, how to decode it properly in the wireshark.

Thanks, Varghese

edit retag flag offensive close merge delete

Comments

At the very least you would need to provide the capture that has the issue and your OS and Wireshark version details.

grahamb ( 2018-05-25 08:50:47 +0000 )edit

Thanks for the response. I couldn't attach the trace here, So I just pasted below and Version 1.2.8 (SVN Rev 32676)

[... snipped for brevity ...]

GSM SMS TPDU (GSM 03.40) SMS-DELIVER
    1... .... = TP-RP: TP Reply Path parameter is set in this SMS SUBMIT/DELIVER
    .1.. .... = TP-UDHI: The beginning of the TP UD field contains a Header in addition to the short message
    ..1. .... = TP-SRI: A status report shall be returned to the SME
    .... .1.. = TP-MMS: No more messages are waiting for the MS in this SC
    .... ..00 = TP-MTI: SMS-DELIVER (0)
    TP-Originating-Address - (919566737288)
    TP-PID: 0
    TP-DCS: 0
        00.. .... = Coding Group Bits: General Data Coding indication (0)
        Special case, GSM 7 bit default alphabet
    TP-Service-Centre-Time-Stamp
        Year 18, Month 05, Day 15
        Hour 09, Minutes 59, Seconds 03
        Timezone: GMT + 5 hours 30 minutes
    TP-User-Data-Length: (6) depends on Data-Coding-Scheme
    TP-User-Data
        User-Data Header
            User Data Header Length (32)
            IE: Reserved for ...

(more)

Hanosh ( 2018-05-25 10:48:47 +0000 )edit

1.2.8 is a very old version (nearly a decade), any chance of trying a modern one that might have fixed the issue?

grahamb ( 2018-05-25 11:54:11 +0000 )edit

add a comment

Malformed packet in the GSM MAP

Comments

1 Answer

Your Answer

Question Tools

Stats

Related questions

Malformed packet in the GSM MAP edit

Comments

1 Answer

Your Answer

Question Tools

Stats

Related questions

Malformed packet in the GSM MAP