Inbound message processing issue in Wavecom handler

[GoogleCodeExporter]

I am using Wavecom_WISMOQCDMA handler. The ReadMessages example works fine. 

But when I keep the Service running and a new message arrives, the inbound 
message processing code is unable to read the messages. There is a strange 
behavior. The command AT+CPMS="MT" is getting a response "OK" and the 
subsequent AT+CMGL="ALL" command is getting the response 
"+CPMS:10,30,1,30(cr)OK(cr)". As a result the system thinks there are no 
messages. Any idea why this could be happening? I am using v3.4.6.

Relevant debug output is attached.

Original issue reported on code.google.com by nizam.mo...@gmail.com on 13 Oct 2010 at 7:05

Attachments:

• [incoming message.txt](https://storage.googleapis.com/google-code-attachments/smslib/issue-396/comment-0/incoming message.txt)

[GoogleCodeExporter]

it's because of the delivery report behavior in CDMA (just send manual from 
atcommand you will see that the delivery report didn't stored to MT, but it 
just send out to response and this response wasn't recognized by the terminator 
at ATHandler.java), as you already know that smslib will set CNMI to 3,1,0,2,0. 
I haven't figured out how to see the delivery report yet, because the CMGR 
report on cdma doesn't behave like the gsm one, and the alternatif was using 
the +CDSI (issue 111), because of that i modif the CNMIDetector.java to 
2,1,1,0,0 by doing this you won't receive any delivery report or you can set 
delivery report to +CDSI, and figure out the issue 111 (I would love to hear it 
if you success decode +CDSI as Delivery report receipt). Thanks.

Original comment by hendrace...@gmail.com on 13 Oct 2010 at 3:04

[GoogleCodeExporter]

sorry i mean +CDS no +CDSI, the second way is to use terminator to terminate 
all response by +CDS but it require you to set the cnmi to other combination 
number, I forget which one, perhaps 3,1,0,3,0 (3 for the forth). but i have 
already forgot it, you need to see the 
http://www.sendsms.cn/download/CDMA_AT_178.pdf and find cnmi configuration for 
that. thanks

Original comment by hendrace...@gmail.com on 13 Oct 2010 at 3:08

[GoogleCodeExporter]

Any feedback on this from you guys working with CDMA modems will be great!

Original comment by T.Delenikas on 17 Oct 2010 at 5:31

• Changed state: Feedback

[GoogleCodeExporter]

This issue took much longer to debug than my expected release date, so I've 
deferred the CDMA portion by a couple weeks. I will definitely need to get this 
resolved, so I'll keep you posted.

Original comment by nizam.mo...@gmail.com on 18 Oct 2010 at 2:10

[GoogleCodeExporter]

Thanks!

Original comment by T.Delenikas on 20 Oct 2010 at 12:09

[GoogleCodeExporter]

Setting AT+CNMI=3,1,0,0,0 seems to solve the problem.

Original comment by nizam.mo...@gmail.com on 13 May 2011 at 6:55

[GoogleCodeExporter]

What is the CNMI command created by the auto-detection SMSLib code?

Original comment by T.Delenikas on 13 May 2011 at 9:00

[GoogleCodeExporter]

The auto detected CNMI code is 3,1,0,2,0. The problem appears to be only with 
the SMS-STATUS-REPORTS setting which I am turning off.

Original comment by nizam.mo...@gmail.com on 14 May 2011 at 3:45

[GoogleCodeExporter]

Wow long time not doing a post. For cdma you have to disabled sms report 
settings. Just make the forth setting to zero will disabled it (x,x,x,0,x)

Original comment by hendrace...@gmail.com on 14 May 2011 at 12:37

[GoogleCodeExporter]

Original comment by admin@smslib.org on 1 Jan 2014 at 9:25

• Changed state: Review

[GoogleCodeExporter]

Original comment by thana...@smslib.org on 26 Apr 2014 at 10:09

• Changed state: WontFix