Kerr.Yang, thank you, the current modem we have set up to test for this problem is an EM06-A with firmware EM06ALAR03A05M4G.
If there is a more up to date firmware available for the EM06-A, I should be able to update before further testing as needed. I also have QLog set up on the attached router, tested, and working, and ready to capture logs to whatever instructions requested.
Thanks!
Hi,
Thanks for your query in Quectel forums.
I have no problem using the same version of the module to test, please refer to the following test process.thanks.
[2021-02-19_17:10:26:175]ATI
[2021-02-19_17:10:26:175]Quectel
[2021-02-19_17:10:26:175]EM06
[2021-02-19_17:10:26:175]Revision: EM06ALAR03A05M4G
[2021-02-19_17:10:26:175]OK
[2021-02-19_17:10:26:760]AT+csq;+cops?;+creg?;+cgreg?;+qnwinfo
[2021-02-19_17:10:26:762]+CSQ: 17,99
[2021-02-19_17:10:26:762]+COPS: 0,0,“CHINA MOBILE”,7
[2021-02-19_17:10:26:762]+CREG: 0,1
[2021-02-19_17:10:26:762]+CGREG: 0,1
[2021-02-19_17:10:26:762]+QNWINFO: “TDD LTE”,“46000”,“LTE BAND 41”,40936
[2021-02-19_17:10:26:762]OK
[2021-02-19_17:10:31:850]AT+CSCA?
[2021-02-19_17:10:31:855]+CSCA: “+8613800551500”,145
[2021-02-19_17:10:31:855]OK
[2021-02-19_17:10:34:253]AT+CMGF=1
[2021-02-19_17:10:34:253]OK
[2021-02-19_17:10:35:871]AT+CSMP=17,167,0,0
[2021-02-19_17:10:35:892]OK
[2021-02-19_17:10:37:479]AT+CSCS=“GSM”
[2021-02-19_17:10:37:479]OK
[2021-02-19_17:10:39:907]AT+CMGS=“13182850105”
[2021-02-19_17:10:39:907]> 123456
[2021-02-19_17:10:46:018]+CMGS: 8
[2021-02-19_17:10:46:018]OK
Hi,
You can also send your failed AT process to let us take a look,thanks.
Test complete as requested. The AT responses follow. There is an unfiltered qlog output file of the process available here, that was running during the entire test process, as well.
AT results (with empty lines removed):
ATI
Quectel
EM06
Revision: EM06ALAR03A05M4G
OK
AT+csq;+cops?;+creg?;+cgreg?;+qnwinfo
+CSQ: 18,99
+COPS: 0,2,“311480”,7
+CREG: 0,3
+CGREG: 0,1
+QNWINFO: “FDD LTE”,“311480”,“LTE BAND 4”,2050
OK
AT+CSCA?
+CSCA: “+19037029920”,145
OK
AT+CMGF=1
OK
AT+CSMP=17,167,0,0
OK
AT+CSCS=“GSM”
OK
AT+CMGS=“13182850105”
> 123456
+CMS ERROR: 350
At CTRL+Z, the AT terminal becomes unresponsive for two minutes while it waits for the send to time out. After the error is returned, terminal behavior returns to normal.
Thank you for your help! Please let me know if you have any trouble retrieving the log file.
Hi，
You have not successfully registered for the CS domain, and the SMS function of the module is sent through the CS domain. It is recommended that you replace the SIM card or consult the operator why the CS domain function of your SIM card is rejected.thanks.
While this is true, it is unlikely to be the source of the problem, because we have another EP06-A that is working successfully with Verizon and SMS, and it is also not registered through the CS domain. We don’t know why that one modem is working - it spontaneously started working earlier this week after one of many reboots, and we have not been able to detect any difference in settings between the working modem and the non-working modem. Here is the same AT test log, but repeated for the modem with SMS working:
ATI
Quectel
EP06
Revision: EP06ALAR02A07M4G
OK
AT+csq;+cops?;+creg?;+cgreg?;+qnwinfo
+CSQ: 21,99
+COPS: 0,0,"Verizon ",7
+CREG: 0,3
+CGREG: 0,1
+QNWINFO: “FDD LTE”,“311480”,“LTE BAND 4”,2050
OK
AT+CSCA?
+CSCA: “+19037029920”,145
OK
AT+CMGF=1
OK
AT+CSMP=17,167,0,0
OK
AT+CSCS=“GSM”
OK
AT+CMGS=“13182850105”
123456
+CMGS: 1
OK
As you can see, this modem is sending SMS just fine (and when sent to our own test number, are received just fine). Verizon began rolling out SMS over IMS several years ago, and SMS over the PS domain is their primary method now where available, with SMS over CS domain still available as fallback. However, Verizon has slowly begun shutting down their CS network and transitioning to PS only.
The working line originally (for several weeks of testing) behaved the same as the non-working line shown above, and others we’ve tested with Verizon. It began to work spontaneously after a reboot; nothing has changed in the performance of the other lines. We have avoided rebooting the working line this week while we try to detect any difference in settings that could be responsible for the different behavior. So far we have detected no differences - they both even report having the same copy of the Verizon MBN file.
The following responses are the same from both modems:
AT+CGDCONT?
+CGDCONT: 1,“IPV4V6”,“vzwims”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,1,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”,“vzw800”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0
+CGDCONT: 6,“IPV4V6”,“vzwemergency”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,1
OK
AT+CGACT?
+CGACT: 1,1
+CGACT: 2,0
+CGACT: 3,1
+CGACT: 4,0
+CGACT: 5,0
+CGACT: 6,0
OK
AT+CREG?;+CGREG?
+CREG: 0,3
+CGREG: 0,1
OK
AT+QCFG=“ims”
+QCFG: “ims”,1,0
OK
AT+CGSMS?
+CGSMS: 2
OK
AT+QCFG=“imsreg/iptype”
+QCFG: “imsreg/iptype”,0
OK
AT+QCFG=“ltesms/format”
+QCFG: “ltesms/format”,0
OK
CGPADDR returns similar responses, different only in the obvious fact that the two modems are assigned different addresses. However, on both, a V6 address is assigned to the ims context, and both V4 and V6 addresses to the main data context:
AT+CGPADDR
+CGPADDR: 1,“38.0.16.3.20.93.252.164.0.0.0.0.32.120.228.183”
+CGPADDR: 2,“”
+CGPADDR: 3,“100.82.119.89,38.0.16.3.180.106.85.193.0.0.0.79.75.70.4.1”
+CGPADDR: 4,“”
+CGPADDR: 5,“”
+CGPADDR: 6,“”
OK
Listing the MBNs produces different results for the EP06 and EM06, because the two modems have different MBNs available. However, both have the same Verizon MBN activated.
EP06-A (working):
AT+QMBNCFG=“list”
+QMBNCFG: “List”,0,0,0,“ROW_Generic_3GPP”,0x06010821,201901151
+QMBNCFG: “List”,1,0,0,“Volte_OpenMkt-Commercial-CMCC”,0x06012064,201706061
+QMBNCFG: “List”,2,0,0,“OpenMkt-Commercial-CU”,0x06011510,201706062
+QMBNCFG: “List”,3,0,0,“VoLTE-ATT”,0x0601036F,201810201
+QMBNCFG: “List”,4,0,0,“ATT_NDO”,0x06800601,201903051
+QMBNCFG: “List”,5,0,0,“ATT_FirstNET”,0x06800501,201903051
+QMBNCFG: “List”,6,1,1,“hVoLTE-Verizon”,0x060101A0,201810241
+QMBNCFG: “List”,7,0,0,“Telus-Commercial”,0x0680FE01,201903073
OK
EM06-A (not working):
AT+QMBNCFG=“list”
+QMBNCFG: “List”,0,0,0,“ROW_Generic_3GPP”,0x06010821,201901151
+QMBNCFG: “List”,1,0,0,“Volte_OpenMkt-Commercial-CMCC”,0x06012064,201907031
+QMBNCFG: “List”,2,0,0,“OpenMkt-Commercial-CU”,0x06011510,201706062
+QMBNCFG: “List”,3,0,0,“VoLTE-ATT”,0x0601036F,201904171
+QMBNCFG: “List”,4,0,0,“ATT_NDO”,0x06800601,201903051
+QMBNCFG: “List”,5,0,0,“ATT_FirstNET”,0x06800501,201903051
+QMBNCFG: “List”,6,1,1,“hVoLTE-Verizon”,0x060101A0,201810241
+QMBNCFG: “List”,7,0,0,“Telus-Commercial”,0x0680FE01,201907031
+QMBNCFG: “List”,8,0,0,“USCC-Commercial_VoLTE”,0x0680FD01,201907041
+QMBNCFG: “List”,9,0,0,“Sprint-VoLTE”,0x06010324,201911041
+QMBNCFG: “List”,10,0,0,“Rogers_Canada”,0x0680FC01,201908281
+QMBNCFG: “List”,11,0,0,“Bell_Canada”,0x0680FB01,201906111
OK
If anything, having one modem now spontaneously able to send SMS is even more confusing, because we haven’t been able to identify any differences in configuration that could account for one working and one not. Is there anything else we can check that could help identify the difference?
Thank you.
Hi,
Thanks for your query in Quectel forums.
Please use the Qwinlog tool to grab a copy of the problem log and send it to us for analysis. After opening Qwinlog and clicking start, you need to send AT+CFUN=0 and AT+CFUN=1, and then you send the SMS. After the SMS fails, click stop, and then Send me the log,
The Qwinlog tool link is as follows,thank you.
link ：https://pan.baidu.com/s/1vjv8gW4mGhLSUYwYa9pJUA
Extraction code ：wh33
Thank you. Before we do, have you already reviewed the log we’ve already sent you?
In case you missed the link in the post above (I can see it’s not very visible):
That log was captured using QLog. It was running during the test we captured AT responses from above.
Please let me know if that log captures what you were looking for, if not we can capture and upload another.
Thank you!
Hi,
What is your company name?
thanks.
Hi，
Thanks for your query in Quectel forums.
Please insert this Verizon SIM card into your phone to test to see if it can send text messages normally Please insert this Verizon SIM card into your phone to test to see if it can send text messages normally.
thanks.
I’m working with the ROOter team, a development team for a fork of the OpenWRT operating system which focuses on improved LTE/5G modem support. Many successful improvements are subsequently imported back into the main OpenWRT line. We support both manufacturers making integrated router/modem solutions, and end users building custom setups with off the shelf components. Website Link
At this time, I would say approximately half the manufacturers and users we have talked to are using Quectel modems in their builds, so we have been putting extra effort into improving support for your products over the last year.
Yes - we have verified the SIMs/accounts on both of these test lines are able to send and receive SMS successfully in other Verizon devices.
Thank you for your support.
Hello Kerr.Yang,
Did nathhad capture everything you are looking for in his log? What are the next steps to getting this working? Thanks!
Hi,
Thanks for your query in Quectel forums.
Yes, similar to the operator’s sim card problem because we are not easy to reproduce in China, so we suggest that you can communicate with the operator or get technical support from our local FAE, or you can communicate with nathhad on the progress of the problem, and hope to provide you with it. help.
thanks.
The EM-12G is a GSM/GPRS module that can be used to send and receive SMS messages. Here’s an example of how you could use the EM-12G module with a Raspberry Pi to send an SMS message:
minicom package on the Raspberry Pi to communicate with the EM-12G module:sudo apt-get install minicom
minicom and configure it to communicate with the EM-12G module. The default baud rate for the EM-12G is 9600:minicom -b 9600 -o -D /dev/serial0
AT+CMGF=1 # Set the SMS message format to text mode
AT+CMGS="+1234567890" # Set the phone number to send the SMS to
> Hello, this is a test message. # Enter the SMS message text
CTRL+Z # Send the SMS message
Replace +1234567890 with the phone number you want to send the SMS to, and Hello, this is a test message. with the actual message you want to send.Note that you need to include the newline character (\n) after each AT command for the EM-12G module to recognize the command.
5. The EM-12G module will respond with a message indicating whether the SMS message was sent successfully.
+CMGS: 123 # The message was sent successfully
The EM-12G is a GSM/GPRS module that can be used to send and receive SMS messages. Here’s an example of how you could use the EM-12G module with a Raspberry Pi to send an SMS message:
minicom package on the Raspberry Pi to communicate with the EM-12G module:csharpCopy code
sudo apt-get install minicom
minicom and configure it to communicate with the EM-12G module. The default baud rate for the EM-12G is 9600:bashCopy code
minicom -b 9600 -o -D /dev/serial0
graphqlCopy code
AT+CMGF=1 # Set the SMS message format to text mode
AT+CMGS="+1234567890" # Set the phone number to send the SMS to
> Hello, this is a test message. # Enter the SMS message text
CTRL+Z # Send the SMS message
Replace +1234567890 with the phone number you want to send the SMS to, and Hello, this is a test message. with the actual message you want to send.Note that you need to include the newline character (\n) after each AT command for the EM-12G module to recognize the command.
5. The EM-12G module will respond with a message indicating whether the SMS message was sent successfully.
pythonCopy code
+CMGS: 123 # The message was sent successfully
That’s a brief overview of how you can use the EM-12G module to send SMS messages from a Raspberry Pi. There are also Python libraries available that can be used to communicate with the module programmatically, such as pyserial.
Source: SMSala Bulk SMS Provider