Operating system name and version: Ubuntu
Version of smsd: 3.1.12
Smsd installed from: sources
Name and model of a modem / phone: Wavecom
Interface: USB

I receive a few hundreds sms during a real-time voting competition. After some time, the incoming sms in my modem were not deleted in the modem by smsd. This caused a repetitive cycle of reading the same batch of sms from the modem and new sms cannot be received. To date, i received more than 20,000 sms with the same batch of sms in my modem that were not deleted and the count keeps going up.

I was able to remove this batch of sms by putting the sim card in my mobile phone and manually delete the sms. But the problem persists after i put it in my gsm modem with the new batch of incoming sms.

Is there any setting I need to take note to handle bulk incoming sms? The log file reported that the CMGL got some input errors.

Any help is greatly appreciated!

I need to see the log. You can protect it with Private tags, if necessary.

Appreciate your kind expert advise for my problems.

smsd.conf

Hidden private text.

log file

Hidden private text.

It looks like your modem has a bad firmware which causes this problem. When trying to delete the message #1, modem does not answer and after that it has "echo on" and every deletion will fail. At the end it also drops from the network, or at least says so.

Have you tried with a default check_memory_method which is 1, or with 3 which is little bit slower than 31?

I have to think if a response to AT+CMGD should be checked. However, if no response or ERROR is received, smsd cannot do much more than create an alert and stop completely.

The modem works well if i clear the stored messages with a mobile phone. And normal operation will resume if there are few incoming SMS received. Any further diagnostic help?

Right now I do not know about further diagnostics, sorry.

When the SIM is full, the modem does not work properly. There is not much to do for it.

Have you checked if check_memory_method = 3 helps? It probably may help, because currently those messages may be in "unread" state, but with method 3 they should be in "read" state when smsd tries to delete them.

I just cleared the stored messages in the GSM SIM card using my mobile phone. And I set the check_memory_method = 3. The newest batch of SMS (lots of them) that came in were processed properly till now.

I think the modem will have some problem deleting message when the SIM card became full. Any way to prevent that? And is check_memory_method = 3 the ideal configuration for my current modem given its mentioned limitation?

wilyn wrote

I just cleared the stored messages in the GSM SIM card using my mobile phone. And I set the check_memory_method = 3. The newest batch of SMS (lots of them) that came in were processed properly till now.

Next time when this problem occurs, you could stop the smsd and start it in communication mode:
smsd -C modem1

The try if you can delete messages using any combination of AT commands. For example, read a message: AT+CMGR=12, and then try to delete it: AT+CMGD=12. Also try if ATZ makes any difference. Or perhaps you need to reset the modem, at least take the SIM out and put it back.

wilyn wrote

I think the modem will have some problem deleting message when the SIM card became full. Any way to prevent that?

Yes it really has some problem...

It's not possible to prevent fulfillment. You already have the setting receive_before_send = yes, but it of course does not help when smsd is not running.

Your device is "Wavecom", but you did not provide any other information. Use the modem setting report_device_details = yes, restart smsd and show the piece of a log here.

wilyn wrote

And is check_memory_method = 3 the ideal configuration for my current modem given its mentioned limitation?

I do not know because of the faulty firmware.

Thanks for the advise.

Can you explain the difference between check_memory_method = 3 and check_memory_method = 31?

I am using check_memory_method = 3 now but I can't test my modem because I don't have hundred of incoming SMS now.

wilyn wrote

Can you explain the difference between check_memory_method = 3 and check_memory_method = 31?

It's explained here.

wilyn wrote

I am using check_memory_method = 3 now but I can't test my modem because I don't have hundred of incoming SMS now.

You only need 30 or 31 incoming SMS for testing. Change incoming = no and report = no, then send 31 SMS to your SIM. It's then filled up and you can do tests.

keke wrote

Your device is "Wavecom", but you did not provide any other information. Use the modem setting report_device_details = yes, restart smsd and show the piece of a log here.

I was asking this because "device details" usually are useful when resolving problems. Can you show the piece of a log?

2010-09-23 01:47:38,2, smsd: Smsd v3.1.14 started.
2010-09-23 01:47:38,2, smsd: Running as root:root.
2010-09-23 01:47:38,4, smsd: File mode creation mask: 022 (0644, rw-r--r--).
2010-09-23 01:47:42,7, Wavecom: ## Start of device details
2010-09-23 01:47:42,7, Wavecom: # Manufacturer identification:
2010-09-23 01:47:43,7, Wavecom: -> AT+CGMI
2010-09-23 01:47:43,7, Wavecom: <- WAVEC0M MODEM
OK
2010-09-23 01:47:43,7, Wavecom: # Model identification:
2010-09-23 01:47:43,7, Wavecom: -> AT+CGMM
2010-09-23 01:47:43,7, Wavecom: <- MULTIBAND 900E 1800
OK
2010-09-23 01:47:43,7, Wavecom: # Revision identification:
2010-09-23 01:47:44,7, Wavecom: -> AT+CGMR
2010-09-23 01:47:45,7, Wavecom: <- 532a09gg.2C2 1828120 040802 18:22

Thank's.

"details" end with a line like:
2010-09-22 21:00:30,7, GSM1: ## End of device details

...but in your current case, rest of details are not very important.

In my case, iTegno 3000 which is based on the chip from Wavecom, says:

2010-09-22 21:00:23,7, GSM1: ## Start of device details
2010-09-22 21:00:23,7, GSM1: # Manufacturer identification:
2010-09-22 21:00:23,7, GSM1: -> AT+CGMI
2010-09-22 21:00:24,7, GSM1: <- WAVECOM MODEM
OK
2010-09-22 21:00:24,7, GSM1: # Model identification:
2010-09-22 21:00:24,7, GSM1: -> AT+CGMM
2010-09-22 21:00:24,7, GSM1: <- MULTIBAND 900E 1800
OK
2010-09-22 21:00:24,7, GSM1: # Revision identification:
2010-09-22 21:00:25,7, GSM1: -> AT+CGMR
2010-09-22 21:00:25,7, GSM1: <- 652a09gg.Q2406A 1489876 060706 17:19
OK

...and so on.

The revision of firmware is very different, about two years in age. As I have tested operations with filled up SIM with my device, without any problems, I think that you really should upgrade your device.

Is this problem still active? If it is, have you checked if you can delete messages manually (smsd -C modem1)?

Not sure whether this problem is resolved. Haven't been having sms poll for quite some time. Once the problem begins, there is no way to delete sms via the gsm modem. The only way is to delete through mobile phone.