search

zhqiyi / boghe

Automatically exported from code.google.com/p/boghe
0 stars 0 forks source link

SMS-DELIVER-REPORT instead of SMS-SUBMIT #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Select binary SMS option
2. Send SMS
3. Capture the traffic

What is the expected output? What do you see instead?
The client should send SMS-SUBMIT, according to 
http://betelco.blogspot.com/2009/10/sms-over-3gpp-ims-network.html
Wireshark 1.4.2 shows that the Boghe app sends SMS-DELIVER-REPORT in its 
RP-DATA.

What version of the product are you using? On what operating system?
Boghe-alpha (1.0.55.539)
Windows XP Pro SP3

Please provide any additional information below.
This is mentioned in comments to issue 28 which might be invalid (I have not 
verified it with proper IMS configuration yet).

Original issue reported on code.google.com by victorx...@gmail.com on 10 Jan 2011 at 9:46

Attachments:

GoogleCodeExporter commented 9 years ago 
The result shown by wireshark is incorrect as it ignores the smsc address 
information (TS 23.040 section 9.1.2.5). The first octet (TS 23.040 section 
9.2.2.2) is 0x11 (SMS-SUBMIT) instead of 0x04 (SMS-DELIVER). Perhaps I'm wrong.

Original comment by boss...@yahoo.fr on 10 Jan 2011 at 10:32

GoogleCodeExporter commented 9 years ago 
There exists at least one client application that sends SUBMIT in a way that 
Wireshark shows it as SUBMIT. Of course this doesn't prove anything - just more 
food for thought.

Original comment by victorx...@gmail.com on 11 Jan 2011 at 12:13

Attachments:

GoogleCodeExporter commented 9 years ago 
It looks like the destination address is repeated twice before the 0x11 byte.
Note the sequence 04 a8 22 22 f2.

Original comment by victorx...@gmail.com on 11 Jan 2011 at 12:58

Attachments:

GoogleCodeExporter commented 9 years ago 
Version 1.0.58 should fix the issue.

Original comment by boss...@yahoo.fr on 6 Feb 2011 at 6:55