This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

i have two "gsm_sms" packets in ss7 network. these packets contain two parts of a multipart SMS. in user data heaher (UDH) of these packets i saw Message parts =2 ,and other properties of first packet is : message part number =1 , message idendifier =35 and TP-MMS FLAG shows: more message are waiting for MS in this SC. properties of second packet is : message part number =2 , message idendifier =35 and TP-MMS FLAG shows: No more message are waiting for MS in this SC. in the wireshark these packets are reassembled, however TP-Originating Address of these packets are different. is it ok?

asked 06 Apr '17, 04:10

ghader's gravatar image

ghader
61141620
accept rate: 0%

edited 06 Apr '17, 06:02

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k572


it is a bug of wireshark (packet-gsm_sms.c). according to gsm 03.40 packets that have same message identifier and same TP-Originating Adresses and same Service center should be reassembled. however in packet-gsm_sms.c packets that have same message identifier are reassembled.

permanent link
This answer is marked "community wiki".

answered 07 Apr '17, 08:21

hhw's gravatar image

hhw
104711
accept rate: 100%

wikified 07 Apr '17, 08:32

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×13

question asked: 06 Apr '17, 04:10

question was seen: 698 times

last updated: 07 Apr '17, 08:32

p​o​w​e​r​e​d by O​S​Q​A