MC7455 - unable to clean status reports at "SR"

michaeld · January 17, 2024, 9:23am

When the status reports are enabled and they are written into the storage, there is no way for them to be cleared. The capacity of the “SR” memory is probably 30. That means, that after sending 30 SMS messages, the modem is not able to send an SMS message. The memory is cleared only after full reset. We are configuring the reports with “AT+CNMI=1,2,0,1,0”.
Example
at+cpms=“SR”
+CPMS: 10,30,1,2,0,75

OK
AT+CMGD=1,4
OK
at+cpms=“SR”
+CPMS: 10,30,1,2,0,75

OK

jyijyi · January 17, 2024, 10:06am

my test shows that the “SR” value will not go up after sending SMS

at+cnmi=1,2,0,1,0
OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: MC7455
Revision: SWI9X30C_02.38.00.00 rE3F3E55C03AE94 jenkins 2022/01/13 05:16:00
MEID: 35907206012345
ESN: 12800012345, 80012345
IMEI: 359072060012345
IMEI SV: 22
FSN: LQ530100512345
+GCAP: +CGSM


OK
at+cpms="SR"
+CPMS: 0,30,0,40,0,40

OK
at+cmgs="1234567"
> asdfqwer

+CMGS: 10

OK
at+cpms?
+CPMS: "SR",0,30,"SM",0,40,"SM",0,40

OK

michaeld · January 17, 2024, 10:31am

In your example the sms is not actually delivered, and obviously you don’t have delivery report.
+CDSI: “SR”,14
Is an indication that the report is received and stored. We did not find any configuration of “+CNMI” which allows us to receive “+CDS” notifications without storing them

jyijyi · January 17, 2024, 10:32am

i can receive the SMS, so it should be delivered

michaeld · January 17, 2024, 10:37am

For our situation to reproduce you should be able to observe +CDSI: “SR”,14 and +CDS unsolicited result codes in the modem serial interface.

jyijyi · January 17, 2024, 10:40am

how to observe this +CDSI?

michaeld · January 17, 2024, 11:03am

In order to receive sms delivery report, we are sending the sms messages in PDU mode and adding delivery request into the PDU. Additionally, “+CNMI” need to be configured.

This is the excerpt from our log, I hope it will be clear

1705412535.936 D modem.py:send_command : /tmp/modem_04 TX: AT+CMMS=1
1705412535.942 D modem.py:getline : /tmp/modem_04 RX: OK
1705412535.942 I sender.py:set_status : /tmp/modem_04 Changing status READY → TARGET
1705412536.133 D modem.py:getline : /tmp/modem_02 RX: >
1705412536.133 D sender.py:store_sms : 079179520002001121000C91795224467213401002C120
1705412536.159 D modem.py:getline : /tmp/modem_02 RX: +CMGW: 0
1705412536.160 D modem.py:getline : /tmp/modem_02 RX: OK

1705412537.333 D modem.py:send_command : /tmp/modem_02 TX: AT+CMSS=0
1705412537.437 I sender.py:run : /tmp/modem_04 Keeping waiting for send event.
1705412537.660 D modem.py:getline : /tmp/modem_02 RX: +CMSS: 182
1705412537.661 D modem.py:getline : /tmp/modem_02 RX: OK
1705412537.661 I sender.py:send_sms_from_mem : /tmp/modem_02 Sent SMS number 182
1705412537.661 I sender.py:run : /tmp/modem_02 Sending took 0.334 s
1705412537.662 I sender.py:wait_for_delivery_report: /tmp/modem_02 Waiting for delivery report for 10.0 s…
1705412538.355 D modem.py:getline : /tmp/modem_02 RX: +CDSI: “SR”,0

michaeld · January 17, 2024, 11:48am

Here is more convenient reproduction of the issue for SMS in text mode. It is possible to observe the +CMGD command does not affect the status report storage
AT+CNMI=1,2,0,1,0
OK
at+cpms=“SR”
+CPMS: 13,30,1,2,0,75

OK
AT+CMGS=“+972525397371”

dd

+CMGS: 44

OK

+CDS: 6,44,“972525397371”,241,“24/01/17,13:46:12+08”,“24/01/17,13:46:32+08”,0
at+cpms=“SR”
+CPMS: 14,30,1,2,0,75

OK
at+cmgd=1,4
OK
at+cpms=“SR”
+CPMS: 14,30,1,2,0,75

OK

jyijyi · January 17, 2024, 1:13pm

here is my test on MC7455:

AT+CNMI=1,2,0,1,0
OK
at+cmgs="63919599"
> asdfasdf

+CMGS: 17

OK

+CMT: "+85263919599",,"24/01/17,21:11:53+32"
asdfasdf
at+cpms?
+CPMS: "SR",0,30,"SR",1,75,"SM",2,40

OK
at+cmgd=1,4
OK
at+cpms?
+CPMS: "SR",0,30,"SR",0,75,"SM",2,40

OK

michaeld · January 17, 2024, 3:14pm

In this example you are receiving “+CMT” unsolicited result code, which is actually a report about incoming SMS message. Our problem is with “+CDS” and “+CDSI” result codes, representing SMS status reports. Probably they are behaving differently.

jyijyi · January 17, 2024, 3:30pm

i cannot generate the “+CDS” and “+CDSI” result codes, any idea?

are you using same FW as mine?

michaeld · January 18, 2024, 10:10am

We are trying to upgrade to 02.38.00.00. Hope it will change something. For your tests - sometimes status report comes after 20-30 seconds, may be you need to wait more.

jyijyi · January 18, 2024, 3:55pm

I don’t see the notification:


[2024-01-18 23:50:43.843] at!Gstatus?
[2024-01-18 23:50:47.180] !GSTATUS: 
[2024-01-18 23:50:47.180] Current Time:  141		Temperature: 26
[2024-01-18 23:50:47.180] Reset Counter: 1		Mode:        ONLINE         
[2024-01-18 23:50:47.180] System mode:   LTE        	PS state:    Attached     
[2024-01-18 23:50:47.180] LTE band:      B3     		LTE bw:      20 MHz  
[2024-01-18 23:50:47.180] LTE Rx chan:   1400		LTE Tx chan: 19400
[2024-01-18 23:50:47.180] LTE CA state:  INACTIVE    		LTE Scell band:B7     
[2024-01-18 23:50:47.180] LTE Scell bw:20 MHz  		LTE Scell chan:3150
[2024-01-18 23:50:47.180] EMM state:     Registered     	Normal Service 
[2024-01-18 23:50:47.180] RRC state:     RRC Connected  
[2024-01-18 23:50:47.180] IMS reg state: No Srv  		
[2024-01-18 23:50:47.180] 
[2024-01-18 23:50:47.180] PCC RxM RSSI:  -61		RSRP (dBm):  -94
[2024-01-18 23:50:47.180] PCC RxD RSSI:  -96		RSRP (dBm):  -140
[2024-01-18 23:50:47.180] SCC RxM RSSI:  -85		RSRP (dBm):  -108
[2024-01-18 23:50:47.180] SCC RxD RSSI:  -105		RSRP (dBm):  -134
[2024-01-18 23:50:47.180] Tx Power:      --		TAC:         0652 (1618)
[2024-01-18 23:50:47.180] RSRQ (dB):     -12.7		Cell ID:     01E5110C (31789324)
[2024-01-18 23:50:47.180] SINR (dB):      3.8
[2024-01-18 23:50:47.180] 
[2024-01-18 23:50:47.180] 
[2024-01-18 23:50:47.180] OK
[2024-01-18 23:50:52.997] AT+CNMI=1,2,0,1,0
[2024-01-18 23:50:53.725] OK
[2024-01-18 23:50:54.534] at+cpms?
[2024-01-18 23:50:56.106] +CPMS: "SR",0,30,"SR",0,75,"SR",0,75
[2024-01-18 23:50:56.106] 
[2024-01-18 23:50:56.106] OK
[2024-01-18 23:51:38.041] at+cpms?
[2024-01-18 23:51:40.113] +CPMS: "SR",0,30,"SR",0,75,"SR",0,75
[2024-01-18 23:51:40.113] 
[2024-01-18 23:51:40.113] OK
[2024-01-18 23:52:19.294] at+cmgs="63919599"
[2024-01-18 23:52:22.305] > asdfasdf
[2024-01-18 23:52:24.076] 
[2024-01-18 23:52:24.076] +CMGS: 20
[2024-01-18 23:52:24.076] 
[2024-01-18 23:52:24.076] OK
[2024-01-18 23:52:24.298] 
[2024-01-18 23:52:24.298] +CMT: "+85263919599",,"24/01/18,23:52:23+32"
[2024-01-18 23:52:24.298] asdfasdf
[2024-01-18 23:52:28.319] at+cpms?
[2024-01-18 23:52:29.801] +CPMS: "SR",0,30,"SR",1,75,"SR",1,75
[2024-01-18 23:52:29.801] 
[2024-01-18 23:52:29.801] OK
[2024-01-18 23:53:51.943] at+cmgd=1,4
[2024-01-18 23:53:54.822] OK
[2024-01-18 23:53:55.615] at+cpms?
[2024-01-18 23:53:56.892] +CPMS: "SR",0,30,"SR",0,75,"SR",0,75
[2024-01-18 23:53:56.892] 
[2024-01-18 23:53:56.892] OK

michaeld · January 19, 2024, 6:24am

Hello. We have upgraded to the latest firmware and made more detailed test. Please take a look. Hope it is reproduces in your environment

SMS delivery report minimum example

Connect to modem 4

sudo microcom /dev/ttyUSB29 -s 115200

at+cfun=1,1
OK

sudo microcom /dev/ttyUSB29 -s 115200

ate
OK

ati
Manufacturer: Sierra Wireless, Incorporated
Model: MC7455
Revision: SWI9X30C_02.38.00.00 rE3F3E55C03AE94 jenkins 2022/01/13 05:16:00
MEID: 35457251202320
IMEI: 354572512023201
IMEI SV: 22
FSN: LQ231622560310
+GCAP: +CGSM

OK

Enable SMS report and Status report and discard old URC (Error!)

AT+CNMI=0,2,0,1,0
+CMS ERROR: 303

Enable SMS report and Status report and flush URC (Error!)

AT+CNMI=2,2,0,1,0
+CMS ERROR: 303

Enable SMS report and Status report and discard new URC when buffer full (No error, but not what we want!)

AT+CNMI=1,2,0,1,0
OK

Configure first byte of PDU to enable request of delivery report

AT+CSMP=49,
+CMS ERROR: 313

AT+CSMP?
+CSMP: 49,0,0

Check SR memory storage (3 slots of 30 were occupied before!)

AT+CPMS=“SR”
+CPMS: 3,30,1,2,1,2

OK
AT+CPMS?
+CPMS: “SR”,3,30,“SM”,1,2,“SM”,1,2

OK

Send SMS, receive delivery report in +CDS URC

AT+CMGF=1
OK
AT+CSCS=“GSM”
OK
at+cmgs=“+972542642731”

asdasdasd

+CMGS: 4

OK

+CDS: 6,13,“972542642731”,241,“24/01/18,16:31:06+08”,“24/01/18,16:31:07+08”,0

Check SR memory storage (4 slots occupied, even after clearing!)

AT+CPMS?
+CPMS: “SR”,4,30,“SM”,1,2,“SM”,1,2

OK

at+cmgd=1,4
OK

AT+CPMS?
+CPMS: “SR”,4,30,“SM”,1,2,“SM”,1,2

OK

Send 25 more SMS, send the next one

at+cmgs=“+972542642731”

29 slots left, taking the 30th

+CMGS: 45

OK

+CDS: 6,45,“972542642731”,241,“24/01/18,16:37:44+08”,“24/01/18,16:37:46+08”,0

AT+CPMS?
+CPMS: “SR”,30,30,“SM”,1,2,“SM”,1,2

No more CDS will arrive, because SR all slots are occupied

at+cmgs=“+972542642731”

30 SR slots occupied

+CMGS: 46

OK

jyijyi · January 19, 2024, 6:37am

i don’t see what has been added to generate this notification compared to my log

michaeld · January 19, 2024, 7:32am

For text mode, +CSMP command is required. It returns error on the modem, however it is still enables status report for the text mode sms. Please review my session below. First two sms did not receive the status, however the third did
at
OK
AT+CMGF=1
OK
AT+CSCS=“GSM”
OK
at+cmgs=“+972542642731”

a

+CMGS: 74

OK
AT+CPMS=“SR”
+CPMS: 0,30,1,2,1,2

OK
AT+CNMI=1,2,0,1,0
OK
at+cmgs=“+972542642731”

b

+CMGS: 75

OK
AT+CSMP=49,
+CMS ERROR: 313
AT+CNMI?
+CNMI: 1,2,0,1,0

OK
AT+CSMP?
+CSMP: 49,0,0

OK
at+cmgs=“+972542642731”

c

+CMGS: 76

OK

+CDS: 6,76,“972542642731”,241,“24/01/19,09:27:30+08”,“24/01/19,09:27:31+08”,0

jyijyi · January 19, 2024, 7:55am

no +CDS is observed, could this be related to network operator?


ati3
Manufacturer: Sierra Wireless, Incorporated
Model: MC7455
Revision: SWI9X30C_02.38.00.00 rE3F3E55C03AE94 jenkins 2022/01/13 05:16:00
MEID: 35907206012435
ESN: 12800001232, 80001234
IMEI: 359072060012345
IMEI SV: 22
FSN: LQ530100512345
+GCAP: +CGSM


OK
at+cmgf=1
OK
aat
OK
at+cscs?
+CSCS: "IRA"

OK
at+cscs="GSM"
OK
at+cpms?
+CPMS: "SM",2,40,"SM",2,40,"MT",0,255

OK
at+cpms="SR"
+CPMS: 0,30,2,40,0,255

OK
at+cnmi=1,2,0,1,0
OK
at+csmp?
+CSMP: ,,0,0

OK
at+csmp=49,0,0
OK
at+cmgs="1234567"
> asdfadf

+CMGS: 21

OK
at+csmp?
+CSMP: 49,0,0,0

OK
AT+CSMP=49,
OK
at+cmgs="1234567"
> asdfasdf

+CMGS: 22

OK

michaeld · January 19, 2024, 8:10am

May be try with actual phone number and make sure the sms is actually delivered. Otherwise, yes it may be the operator

jyijyi · January 19, 2024, 8:12am

yes, it is actual phone number and i can receive the sms in my phone, i just modify the log
I have tried another SIM with another operator, the result is the same:

at!gstatus?
!GSTATUS:
Current Time:  52               Temperature: 26
Reset Counter: 1                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
LTE band:      B5               LTE bw:      10 MHz
LTE Rx chan:   2460             LTE Tx chan: 20460
LTE CA state:  NOT ASSIGNED
EMM state:     Registered       Normal Service
RRC state:     RRC Connected
IMS reg state: No Srv

PCC RxM RSSI:  -59              RSRP (dBm):  -86
PCC RxD RSSI:  -100             RSRP (dBm):  -140
Tx Power:      --               TAC:         2775 (10101)
RSRQ (dB):     -10.8            Cell ID:     016E8A49 (24021577)
SINR (dB):      6.8


OK
at+csmp?
+CSMP: ,,0,0

OK
at+cmgf=1
OK
at+cscs?
+CSCS: "IRA"

OK
at+cscs="GSM"
OK
at+cpms="SR"
+CPMS: 0,30,39,80,0,75

OK
at+cnmi=1,2,0,1,0
OK
at+csmp=49,0,0
OK
at+cmgs="1234567"
> asdfasdf

+CMGS: 37

OK
at+cpms?
+CPMS: "SR",0,30,"SM",39,80,"SR",0,75

OK

michaeld · January 19, 2024, 8:25am

I wonder how “1234567” may be the actual phone number

Topic		Replies	Views
MC8704 doesn't give SMS STATUS REPORT MC/EM Series	5	1701	April 24, 2017
only few SMS-STATUS REPORTs received MC/EM Series	1	814	November 1, 2017
Unable to receive "+CSDI" URC with MC8775 MC/EM Series	1	756	May 19, 2015
EM7455 in Thinkpad X270 can send SMS but cannot recieve MC/EM Series	3	199	March 20, 2024
MC7354 Stops receiving SMS after 50 messages MC/EM Series	5	1621	November 16, 2016