Hello,
Currently, I am solving an SMS issue with my EC2. The device is unable to send SMS when in PS-only mode. The AT+QCFG=“ims” simply does not work. May I have the latest firmware and any info regarding this issue? I am quite positive I am not the only one who is having this kind of problem.
Thank!
Used wrong account for this topic. Please send me the driver to karel.stary@advantech.cz.
I’m not sure I can help, but here goes.
What do the following AT commands return:
AT+CGDCONT?
AT+CGPADDR
AT$QCPDPIMSCFGE?
By all means mangle the AT+CGPADDR result if you think it might contain sensitive info.
Hello again.
I decided to give it a few more days of troubleshooting, but I was still unable to get it running.
First, let me provide you with some information.
We have multiple modules in our US test lab. We are using mostly AT&T and Verizon SIM cards. We are using different vendors for the LTE module, and one of them is EC25-AF(D). As I can use different Network providers + module manufacturer combinations, I was able to determine that there is no connection to the network provider. I confirmed that all the EC25-AF(D) are unable to send or receive SMS.
Usually, we are running this config.
~ $ sudo gsmat ‘ati’
Quectel
EC25-AF(D)
Revision: EC25AFFDR07A10M4G
~ $ sudo gsmat ‘AT+CREG?’
+CREG: 0,0
~ $ sudo gsmat ‘AT+CGREG?’
+CGREG: 0,1
~ $ sudo gsmat ‘AT+CEREG?’
+CEREG: 0,1
~ $ sudo gsmat ‘AT+COPS?’
+COPS: 0,0,“Verizon Wireless”,7
~ $ sudo gsmat ‘AT+CGATT?’
+CGATT: 1
~ $ sudo gsmat ‘AT+CGSMS?’
+CGSMS: 0
(tried option 2 as well)
~ $ sudo gsmat ‘AT+CGDCONT?’
+CGDCONT: 1,“IPV4V6”,“ims”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0
+CGDCONT: 2,“IPV4V6”,“VZWADMIN”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0
+CGDCONT: 3,“IPV4V6”,“VZWINTERNET”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0
+CGDCONT: 4,“IPV4V6”,“VZWAPP”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0
+CGDCONT: 5,“IPV4V6”,“VZWEMERGENCY”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,1
+CGDCONT: 6,“IPV4V6”,“VZWCLASS6”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0
~ $ sudo gsmat ‘AT$QCPDPIMSCFGE?’
$QCPDPIMSCFGE: 1 , 0 , 0 , 0
$QCPDPIMSCFGE: 2 , 0 , 0 , 0
$QCPDPIMSCFGE: 3 , 0 , 0 , 0
$QCPDPIMSCFGE: 4 , 0 , 0 , 0
$QCPDPIMSCFGE: 5 , 0 , 0 , 0
$QCPDPIMSCFGE: 6 , 0 , 0 , 0
~ $ sudo gsmat ‘AT$QCPDPIMSCFGE?’
$QCPDPIMSCFGE: 1 , 1 , 1 , 0
$QCPDPIMSCFGE: 2 , 0 , 0 , 0
$QCPDPIMSCFGE: 3 , 0 , 0 , 0
$QCPDPIMSCFGE: 4 , 0 , 0 , 0
$QCPDPIMSCFGE: 5 , 0 , 0 , 1
$QCPDPIMSCFGE: 6 , 0 , 0 , 0
(Tried both.)
~ $ sudo gsmat ‘AT+CGACT?’
+CGACT: 1,0
+CGACT: 2,0
+CGACT: 3,0
+CGACT: 4,0
+CGACT: 5,0
+CGACT: 6,0
~ $ sudo gsmat ‘AT+CGACT?’
+CGACT: 1,1
+CGACT: 2,0
+CGACT: 3,1
+CGACT: 4,0
+CGACT: 5,0
+CGACT: 6,0
(again tried both)
~ $ sudo gsmat ‘AT$QCPDPP?’
$QCPDPP: 1,0
$QCPDPP: 2,0
$QCPDPP: 3,0
$QCPDPP: 4,0
$QCPDPP: 5,0
$QCPDPP: 6,0
(Did not manage to get them enabled)
~ $ sudo gsmat ‘AT+QCFG=“ltesms/format”’
+QCFG: “ltesms/format”,2
~ $ sudo gsmat ‘AT+QCFG=“sms_control”’
+QCFG: “sms_control”,1,1
~ $ sudo gsmat ‘AT+QCFG=“ims”’
+QCFG: “ims”,1,0
~ $ sudo gsmat ‘AT+QCFG=“poaccept”’
+QCFG: “poaccept”,1
~ $ sudo gsmat ‘AT+QCFG=“servicedomain”’
+QCFG: “servicedomain”,1
~ $ sudo gsmat ‘AT+QNVFR=“/nv/item_files/modem/mmode/ue_usage_setting”’
+QNVFR: 01
~ $ sudo gsmat ‘AT+QNVFR=“/nv/item_files/modem/mmode/sms_only”’
+QNVFR: 01
(tried both options)
~ $ sudo gsmat ‘AT+QNVFR=“/nv/item_files/ims/IMS_enable”’
+QNVFR: 01
~ $ sudo gsmat ‘AT+QNVFR=“/nv/item_files/modem/mmode/sms_domain_pref”’
+QNVFR: 01
(I have tried all the combinations of IMS_enable and sms_domain_pref. )
~ $ sudo gsmat ‘AT+CGSMS?’
+CGSMS: 0
(Tried option 2 as well)
I have tried the NAS SMS as well (does not work). I have tried all possible PS/IMS/NAS/ combinations with no impact at all.
I know for a fact that we are smoothly running SMS via IMS on the other devices with all zeros on AT$QCPDPIMSCFGE, CGACT and AT$QCPDPP, but it may be a different implementation.
I have tried to disable the autoselection and run “ROW_Generic_3GPP”, manually selected the PDP, connected and still wasn’t able to send SMS. The situation is similar for ATT.
2025-08-11 16:34:12 [debug] sms: sent [ ATE0+CMGF=0;+CMGS=18 ]
2025-08-11 16:34:12 [debug] sms: rcvd [ ]
2025-08-11 16:34:12 [debug] sms: sent [ 0011000B818151521215F60000AA04F4F29C0E^Z ]
2025-08-11 16:34:13 [debug] sms: rcvd [ +CMGS: 4 | OK ]
Any help will be appreciated.
Quick clarification:
As far as I understand this at the moment. I am able to send the SMS (it gets the reference number (+CMGS: 3)) but the recieving devise will get none. If this would happened only for one netwrok provider I would open this with them but this situation is confirmed on both of the major vendors in US. I am trying multiple SIMs as well so its highly unlikely that the problem is something other than the module setting. I am runing same setup in my office in Czech republic and here everything works even the NAS SMS. So there has to be some combination of US network setup and module setup which is giving me this headake.
Hi Karel,
When PS-Only mode is enabled, the circuit-switched (CS) domain is disabled by design. In this configuration, SMS delivery must rely on SMS over NAS or SMS over IMS (VoLTE). However, for most U.S. operators, SMS services are provided primarily through IMS, and SMS over NAS is not supported.
On the EC25 series, when operating in PS-Only mode without a fully established IMS registration, SMS commands
AT+CMGS
may return OK at the AT interface level, but the SMS message may not be delivered by the network. This behavior is expected under the operator network constraints and does not indicate a module malfunction or firmware defect.
This also explains why the same module configuration works as expected when you try it in Czech republic, where operators still allow CS fallback or support SMS over NAS.
Conclusion
Recommendations
Thank you and have a nice day!