Receiving SMS stopped working

[chainingsolid]

I have summarized the issue for the ModemManager folks as best I can, and will mark this issue solved.

The stored messages are not some sort of FIFO for the most recent X messages of any type as I initially suspected.  They all appear to be SMS messages, though apparently not all SMS messages get stored in this manner.

A person can use AT+CPMS? to see the storage size and how much is used.  A response like '+CPMS: "ME",35,99,"MT",35,99,"MT",35,99' would mean 35 of a maximum of 99 messages are currently stored.  I think doing a AT+CMGD=,2 in a daily or even weekly cron will keep the system from getting clogged again until a proper solution is found.  It seems like doing the purge too often risks interfering with normal modem operations.

 
Thanks, this just temporarily fixed another Verizon users SMS functionality! Kind curious what you used to send the AT commands? I used atinout (http://atinout.sourceforge.net/), but it took me like 10 minutes, due to low levels of experience with Linux command line in general. I do want to have a go at trying to figure out whats up with these SMS messages and if there's any pattern to them.

[treebeard]

I've been using picocom but lately it seems like it truncates some of the output from the modem so I'm going to try minicom, and maybe atinout as well.  You can send AT+CMGF=1 to put the modem in a sort of text response mode and then AT+CMGL="ALL" should display the text of all messages in the modem. I still don't see any pattern, and there is nothing unusual in the normal logs when a message gets stuck.