HUAWEUI modem and Store On Sim

HUAWEUI modem and Store On Sim SearchSearch
Author Message
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 2
Registered: 05-2014
Posted on Thursday, May 14, 2015 - 09:05 pm:   

It seems that tehre are messages being "stuck" in the "SIM/USIM" card and not being processed by Now SMS.

I have SMS Message Storage set to Sim card

How do i correct them and how do i get the existing messages to be processed?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8112
Registered: 10-2002
Posted on Friday, May 15, 2015 - 12:01 am:   

Hi,

Is NowSMS processing the message repeatedly, or is NowSMS not seeing it?

Are you sure it is stuck on the SIM? Or is it stuck in Huawei's desktop software?

It is very important that the Huawei software is configured to save messages on the SIM card, otherwise that software may remove messages from the modem before NowSMS sees them.

The Huawei software is usually called Mobile Partner, but on operator branded modems, it may have a different name. With so many different versions of that software, the location of the setting varies. Often it is under Tools/Options/Text Message ... look that “New Message Save Mode” is set to “Save on SIM/USIM card or device”.

If I have misunderstood, please clarify what you are seeing.

-bn

Bryce Norwood
Now SMS/MMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 3
Registered: 05-2014
Posted on Friday, May 15, 2015 - 12:24 am:   

We have been testing this setup in "production" for a week no. NowSMS seemed to be processing all the messages including the ones that show on the sim card in the partner software.

Today i found 8 message not seen by NOWSMS. First one was a series of 4 sms and 1 mms. And a second a series of 3 smses.

NowSMS seemed to process the other messages fine. and when asked to re-send the texts the people who had problems seem to be fine to now.

We are about to put more pressure on the system next week i'd love to find out if this is going to be a problem.

Attached is a screen shot
the 705 numbers (for example) but they never where seen by nowsms.



Capture
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 4
Registered: 05-2014
Posted on Friday, May 15, 2015 - 12:25 am:   

Additional BOTH the companion program (connection manager) and nowsms both are set to receive to SIM
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 5
Registered: 05-2014
Posted on Friday, May 15, 2015 - 01:04 pm:   

Current settup of NOW SMS
Settings
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 6
Registered: 05-2014
Posted on Friday, May 15, 2015 - 01:05 pm:   

PS: "receive mms messages" is also checked (it is not in the screenshot)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5299
Registered: 08-2008
Posted on Friday, May 15, 2015 - 02:54 pm:   

Hi,

Unfortunately, we don't know what else to suggest. Those settings look good.

That said, in NowSMS, you might want to set "SMS Message Storage" to Default. Let me explain why...and what the setting actually does.

When the modem receives a message, it stores it, either on the SIM card or in device memory. With the "Default" setting, NowSMS aggressively scans both locations for received messages.

Some modems have issues, so the "SIM card" or "Device Memory" settings tell NowSMS to only check one location.

When NowSMS scans for messages, it always deletes them immediately (as the SIM/device has very limited memory).

The setting in the Huawei software has a different effect. "Save in local" deletes the message from the device (so other apps might not see it). "Save on SIM/USIM" leaves it on the device for other apps to process. I notice this setting says "...or device" in the version you are running, so maybe "default" is a better choice in NowSMS.

If you want to troubleshoot in more detail, enable the SMSDEBUG.LOG and add DebugModemPoll=Yes to the [SMSGW] section of SMSGW.INI. This will allow more investigation into what NowSMS is seeing.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 7
Registered: 05-2014
Posted on Friday, May 15, 2015 - 02:59 pm:   

Anotehr one just came in last night.

I see an garbled "TEXT MESSAGE" in the "connection Manager" (thats an MMS) but the MMS-IN directoty only has the previous MMS that was sent earlier.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5300
Registered: 08-2008
Posted on Friday, May 15, 2015 - 03:13 pm:   

I don't know what else to suggest. If NowSMS can't see the message, it can't process it.

Try the suggestions I made, and maybe they will make a difference. And if not, we can study the SMSDEBUG.LOG to see if there is some clue we are missing.

To be honest, if you are sending/receiving MMS, I would highly recommend using an Android device as a modem (over Wifi) instead of a dedicated modem device. It works well for SMS too, but MMS with a modem is slow and clunky due to interface limitations. With an Android device, we can process MMS far more efficiently.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 8
Registered: 05-2014
Posted on Friday, May 15, 2015 - 04:39 pm:   

Hi Des,

Does the ANDROID support mms the same way a modem does (IE: does it still created the files in MMS-IN and SMS-IN and such) the same way?

thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5301
Registered: 08-2008
Posted on Friday, May 15, 2015 - 04:45 pm:   

Hi,

Yes, all the interfaces are the same for files, directories, and HTTP interfaces.

The only limitation is that you can't send special SMS (e.g. flash, WAP push other than MMS) except with HTC devices.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 9
Registered: 05-2014
Posted on Friday, May 15, 2015 - 04:47 pm:   

Awsome currently we dont push out anything but sms back.

Ok ill try the suggested settings and see what happens over the next week. Ill keep the android soultion as an upgrade or if i see additional issues.

Thanks!!!!
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 12
Registered: 05-2014
Posted on Tuesday, July 21, 2015 - 01:48 pm:   

This is very odd, it happened again on a much larger scale.

From about 12:28 through 12:48 on the 17th

i have over a dozen messages from the same person sitting in the companion software's "SIM CARD" inbox however none of them show up in the smsin log

a few smses BEFORE and one AFTER that time range do, but not the ones in the list

Is there anyway to check to see if these messages are in fact on the sim card? or why nowsms does not process them
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5374
Registered: 08-2008
Posted on Tuesday, July 21, 2015 - 07:04 pm:   

Hi,

I don't see a reference to which model modem this is ... but I'd strongly suggest checking the Huawei website for updated firmware and software. Start here: http://consumer.huawei.com/en/support/downloads/

I can tell you that NowSMS doesn't delete messages from the modem until it has read them. (Unless the "Direct to Modem" setting is used, in which case messages are never stored on the modem. But Huawei modems do not support that setting.)

For investigation, I can give you a few pointers for querying the modem with AT commands. I find PuTTY to be a useful tool for running modem tests. Find it here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

AT commands to try:

Set PDU mode for syntax used in other commands:

AT+CMGF=0

Check what memory types are available:

AT+CPMS=?

Should return "SM", might also show "ME", "SR" and/or "MT"

Set default memory type:

AT+CPMS="SM"

Query read and unread messages in memory type:

AT+CMGL=0
AT+CMGL=1

Try other AT+CPMS= values and re-issue AT+CMGL commands to look for messages in other locations.

Earlier, I recommended this:

\quote(That said, in NowSMS, you might want to set "SMS Message Storage" to Default. Let me explain why...and what the setting actually does.

When the modem receives a message, it stores it, either on the SIM card or in device memory. With the "Default" setting, NowSMS aggressively scans both locations for received messages. }

We have seen modems get confused and start using a different memory type for message storage with no reason (buggy firmware?}.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 13
Registered: 05-2014
Posted on Wednesday, July 22, 2015 - 01:27 am:   

Weird debug log didn't post...

I'll repost it soon

For putty

Serial port
But what baud rate?
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 14
Registered: 05-2014
Posted on Wednesday, July 22, 2015 - 02:19 am:   

So here is what i got.

AT+CPMS="SM" Shows that there are 27/40 messages in memory (which corresponds to what the Compaion shows under Inbox.

However the AT+CMGL=[0,1,2] commands do not return ANYTHING at all. (no error. no ok)

---Log---

AT+CMGF=0
OK

AT+CPMS=?
+CPMS: ("SM","ME"),("SM","ME"),("SM","ME")
OK

AT+CPMS="SM"
+CPMS: 27,40,27,40,27,40
OK

AT+CMGL=0
AT+CMGL=1


AT+CPMS="ME"
+CPMS: 0,20,27,40,27,40
OK

AT+CMGL=0
AT+CMGL=1
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5376
Registered: 08-2008
Posted on Wednesday, July 22, 2015 - 03:53 pm:   

Hi,

That is weird. I'd definitely consider updating the firmware.

Try AT+CMGL=4 ... there is an API (that NowSMS does not use) where messages are written to the SIM before sending. I think the idea was for old phones with very limited memory to be able to keep a copy of the last few messages.

The fact that you do not get an OK response is very suspicious, and suggests memory corruption.

It might be worth issuing some delete commands to see if they have any effect.

AT+CMGD=0 ... keep increasing the number, I'd go through 39.

If there is no firmware version update, restoring the firmware to factory default may be a solution ... I'd just be concerned that the problem could reoccur.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 15
Registered: 05-2014
Posted on Thursday, July 23, 2015 - 03:20 am:   

OK here is a wierd on

i have 4 messages "suck" on the sim card

SMSDUBUG shows this some times before this message came in:
Additional after restarting the service between my putty session same message appears


----

21:43:13:959 [16] ModemTest: HUAWEI Mobile Connect - Modem
21:43:14:787 [0] UseRouteCache: Yes
21:43:24:002 [16] ModemTest: OK
21:43:24:002 [16] ThreadProcessModem: AT+CGSMS=3
21:43:24:002 [16] SendModemCommand: WriteFile failed, error 6 (6)
21:43:24:002 [16] SendModemCommand: Wrote 0 bytes, expected 11 bytes
21:43:24:002 [16] SendModemCommand: AT+CGSMS=3

21:43:24:003 [16] SendModemCommand: WriteFile failed, error 6 (6)
21:43:24:003 [16] SendModemCommand: Wrote 0 bytes, expected 10 bytes
21:43:24:003 [16] SendModemCommand: AT+CMEE=1

21:43:24:003 [16] ThreadProcessModem: AT+CNMI?
21:43:24:003 [16] SendModemCommand: WriteFile failed, error 6 (6)
21:43:24:003 [16] SendModemCommand: Wrote 0 bytes, expected 9 bytes
21:43:24:003 [16] SendModemCommand: AT+CNMI?

21:43:24:003 [16] ThreadProcessModem: AT+CNMI=?
21:43:24:003 [16] SendModemCommand: WriteFile failed, error 6 (6)
21:43:24:003 [16] SendModemCommand: Wrote 0 bytes, expected 10 bytes
21:43:24:003 [16] SendModemCommand: AT+CNMI=?

21:43:24:003 [16] ThreadProcessModem: AT+COPS?
21:43:24:003 [16] SendModemCommand: WriteFile failed, error 6 (6)
21:43:24:003 [16] SendModemCommand: Wrote 0 bytes, expected 9 bytes
21:43:24:003 [16] SendModemCommand: AT+COPS?

21:43:24:003 [16] ThreadProcessModem: AT+CSQ
21:43:24:003 [16] SendModemCommand: WriteFile failed, error 6 (6)
21:43:24:003 [16] SendModemCommand: Wrote 0 bytes, expected 7 bytes
21:43:24:003 [16] SendModemCommand: AT+CSQ

21:43:24:003 [16] ThreadProcessModem: AT+CNUM
21:43:24:003 [16] SendModemCommand: WriteFile failed, error 6 (6)
21:43:24:003 [16] SendModemCommand: Wrote 0 bytes, expected 8 bytes
21:43:24:003 [16] SendModemCommand: AT+CNUM

21:43:24:003 [16] ThreadProcessModem: Modem initialization complete:
21:43:31:000 [16] ThreadProcessModem: Before ModemRelease -
21:43:31:000 [16] ThreadProcessModem: After ModemRelease -
21:43:51:004 [16] CheckReloadModemSet: Connection settings have changed, requiring a reconnection
21:43:51:004 [16] SkipQFree: Enter
21:43:51:004 [16] GWfree: Error
21:43:51:004 [16] SkipQFree: Exit
21:43:51:004 [16] ThreadProcessModem: SDKLINK - VirtualSMSC
22:12:46:119 [1] ThreadListenForConnections: Before accept
22:12:46:119 [1] ThreadListenForConnections: After accept
22:12:47:119 [0] main: Shutdown: Closing log files
---


This time connecting directly to the SERIAL does display them:
(sorry had ECHO off but the list is done using AT+CMGL=0)
messages where truncated for privacy reasons.




OK

+CPMS: ("SM","ME"),("SM","ME"),("SM","ME")

OK

+CPMS: 4,40,4,40,4,40

OK

+CMGL: 0,0,,155
07916174854CBDA0201010608BE 8D019FAF84B4848C82984165362D30516E2D75326B426A304C7867008D928918802B313538373433 37353730352F545950453D504C4D4E00964120506963747572652F566964656F204D657373616765 210086818A808E0301E77A8805810306978083687474703A2F2F6D6D73632E696E662E656E672E74 656C75
+CMGL: 1,0,,71
079161748500804CBDA0202736D6F62 696C6974792E636F6D3A383739392F616D6D73633F4165362D30516E2D75326B426A304C786700
+CMGL: 2,0,,45
079161748580E020250714375 55447168574D5F784A61596C00
+CMGL: 3,0,,155
0791617480804280E0201010608BE 8D0185AF84B4848C8298415071437555447168574D5F784A61596C008D928918802B313930353433 31383636342F545950453D504C4D4E0086818A808E030561FE8805810306978083687474703A2F2F 6D6D73632E696E662E656E672E74656C75736D6F62696C6974792E636F6D3A383739392F616D6D73 633F41

OK
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 16
Registered: 05-2014
Posted on Thursday, July 23, 2015 - 05:10 pm:   

As of last night the HAUWIE stick stopped initalizing... got an error that the modem would not initialize.. although all the AT commands seem to work

I bought an new one and it would not read the messages of the sim card (they would just pile up on the sim card!)

i ended up sacraficing my android phone to get it all up and running, so i can take these sticks off production onto dev.

I installed the first stick that was not working and behold!!!! It started working (at least initalizing)

any idea what it could be?

10:49:35:374 [0] UseRouteCache: Yes
10:49:37:376 [0] main: Before InitStatCounters
10:49:37:495 [0] main: After InitStatCounters
10:49:37:495 [0] main: IPV6 Disabled
10:49:37:602 [0] main: Before CheckDatabaseIntegrity
10:49:37:603 [0] main: After CheckDatabaseIntegrity
10:49:39:604 [0] main: Now SMS/MMS Gateway v2015.06.24 Web server started on port number 8800
10:49:39:619 [13] ThreadProcessModem: HUAWEI Mobile Connect - Modem
10:49:39:620 [14] ThreadScanAlerts: Before CheckDatabaseIntegrity
10:49:39:620 [14] CheckDatabaseIntegrity: C:\PROGRA~2\NowSMS\SMPPData\MMSRoute-Remote\20150721.DB
10:49:39:623 [14] ThreadScanAlerts: After CheckDatabaseIntegrity
10:49:44:619 [13] ThreadProcessModem: Before ModemAllocate - HUAWEI Mobile Connect - Modem
10:49:44:619 [13] ThreadProcessModem: After ModemAllocate - HUAWEI Mobile Connect - Modem - OK
10:49:44:619 [13] ThreadProcessModem: Re-initializing modem: HUAWEI Mobile Connect - Modem ...
10:49:44:744 [13] ProcessTAPIMessage: Processed TAPI Message 12
10:49:44:794 [13] ThreadProcessModem: ATI0
10:49:44:794 [13] ThreadProcessModem:
Manufacturer: huawei
Model: E3276
Revision: 21.430.03.01.464
IMEI: 866xxxx12302024
+GCAP: +CGSM,+DS,+ES

OK

10:49:44:804 [13] ThreadProcessModem: ATI1
10:49:44:804 [13] ThreadProcessModem:
Manufacturer: huawei
Model: E3276
Revision: 21.430.03.01.464
IMEI: 866xxxx12302024
+GCAP: +CGSM,+DS,+ES

OK

10:49:44:814 [13] ThreadProcessModem: ATI2
10:49:44:814 [13] ThreadProcessModem:
Manufacturer: huawei
Model: E3276
Revision: 21.430.03.01.464
IMEI: 866xxxx2302024
+GCAP: +CGSM,+DS,+ES

OK

10:49:44:824 [13] ThreadProcessModem: ATI3
10:49:44:824 [13] ThreadProcessModem:
Manufacturer: huawei
Model: E3276
Revision: 21.430.03.01.464
IMEI: 866xxxx2302024
+GCAP: +CGSM,+DS,+ES

OK

10:49:44:834 [13] ThreadProcessModem: ATI4
10:49:44:834 [13] ThreadProcessModem:
Manufacturer: huawei
Model: E3276
Revision: 21.430.03.01.464
IMEI: 866xxxx2302024
+GCAP: +CGSM,+DS,+ES

OK

10:49:44:844 [13] ThreadProcessModem: ATI5
10:49:44:844 [13] ThreadProcessModem:
Manufacturer: huawei
Model: E3276
Revision: 21.430.03.01.464
IMEI: 8665xxxx302024
+GCAP: +CGSM,+DS,+ES

OK

10:49:44:964 [13] ModemTest: HUAWEI Mobile Connect - Modem
10:49:45:823 [0] UseRouteCache: Yes
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 17
Registered: 05-2014
Posted on Thursday, July 23, 2015 - 07:08 pm:   

Modem worked FIND on a differnt pc (no init error message!)

im trying it without having the compaion software running, 2 hours and still stable.


Do you know how long it took before the modem crashed w/o the companion software runing? i think the blog said 3 hours
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5379
Registered: 08-2008
Posted on Saturday, July 25, 2015 - 04:19 pm:   

Receiving SMS seemed to be the activity that triggered the modem crash without the companion software.

Our best guess was a timing issue, the modem receiving an SMS while it was in process sending an SMS. Sending SMS with delivery reports was the best way to force a problem, because it generated such high receive activity.
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 19
Registered: 05-2014
Posted on Thursday, July 30, 2015 - 02:58 pm:   

Came in this morning on a NEW stick with NEW firmware and a NEW sim card.

40 messages sitting in the inbox.. none of the touched
aftera a stretch for a week of it working flawlessly...

Same issue.. shows no error or ok!

Is there anyway to decode the MMS messages manually?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5385
Registered: 08-2008
Posted on Thursday, July 30, 2015 - 10:00 pm:   

Hi,

First the new question:


quote:

Is there anyway to decode the MMS messages manually?




Not really...the SMS part is just a trigger providing a URL on the MMSC to fetch the content.

i'll have more comment on your situation shortly, as I've been reading back through the messages, and I see a few points that need more clarification. I may have jumped to conclusions without considering all possibilities.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 21
Registered: 05-2014
Posted on Thursday, July 30, 2015 - 10:09 pm:   

If i move ALL the messages in the companion software form the SIM card to LOCAL DATABASE the device starts working again.

then if i move all the SMS messages BACK to the sim they all get processed

If i move the SMS trigger for the MMS messags however get processed as SMS messagse not MMS Triggers making them usless.

So can i manually download the MMS messags with the content in the SMS trigger?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5387
Registered: 08-2008
Posted on Thursday, July 30, 2015 - 10:37 pm:   


quote:

So can i manually download the MMS messags with the content in the SMS trigger?




Not easily...and not something I can explain. Especially as I'd rather look at SMSDEBUG.LOG to better understand a few things...(to be continued shortly)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5388
Registered: 08-2008
Posted on Thursday, July 30, 2015 - 10:37 pm:   

Hi,

I've been reviewing your information, especially the SMSDEBUG.LOG excerpts...and I am intrigued by a few things.

NowSMS encountered a modem error at 21:43:24:002. A shutdown was initiated at 22:12:46:119...almost 30 minutes later, but NowSMS appeared to make no attempt to reconnect to the modem.

That is not normal. Does that same pattern occur at other times the problem is observed?

I also find it interesting that you are able to connect to the modem and issue AT+CMGL=0, which seems to work? In this same scenario, does restarting the NowSMS service also restore access to the messages?

Does rebooting the PC recover the lost connectivity?

I am very concerned that NowSMS is not repeatedly trying to recover access to this modem. There should be repeated retries...and there is an option we can enable to trigger a system reboot if the problem cannot be resolved. But it seems to me that for some reason, NowSMS is not trying.

Do you still have SMSDEBUG.LOG and/or SMSDEBUG.BAK from today's problem? If so, email to nowsms@nowsms.com with Attention: Des in the subject line. Also post a note here so I know to look for the files.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 24
Registered: 05-2014
Posted on Thursday, July 30, 2015 - 11:04 pm:   

I have sent what i have in..

however i think the initial error has been overwritten.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5389
Registered: 08-2008
Posted on Friday, July 31, 2015 - 08:16 pm:   

Hi,

Thank you for those logs. If the problem reoccurs, please use the same process to get the logs to me.

I have reviewed the logs with two of our developers. There was nothing unusual in the most recent logs, only a recoverable error. As you indicated, it appears the original problem was already overwritten.

The log excerpt posted earlier in this thread is the one that has us confused. The developers see no explanation for the sequencing of log entries. We'd like to get a closer look at a more complete log that covers a problem event.

If the problem reoccurs, save the log. Then restart the service to see if the missing messages are processed. Give it a minute or two. Save the log again. If not resolved, reboot to see if this fixes.

One idea that might make a difference. Edit SMSGW.INI, and under the [SMSGW] header, add:
AltModemTimeouts=Yes


Restart the service after applying this setting.

This might increase CPU overhead. If it causes problems, remove it.

This is an experimental setting attempting to improve stability with some modems.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 25
Registered: 05-2014
Posted on Monday, August 24, 2015 - 03:48 pm:   

So it happened again last week, didn't notice it till today and it seems the backups files only last from midnight.

e-mailed you the file i have but its odd it seems to always start with index 30 right now (there are 30 messages on the sim card)

oddly enough all but 2 are from the same person in a short period of time (about 10-15 minutes) everything else seemed to work. it does not seem these messages where processed by nowsms (cant find it in sms-in)

ill setup the system to backup the logs at like 11:00 pm every day so i have a copy of when it actually happens!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5414
Registered: 08-2008
Posted on Monday, August 24, 2015 - 04:45 pm:   

I've got an idea...

Can you try some manual modem commands again?

Start with what I had you do before:


quote:

Set PDU mode for syntax used in other commands:

AT+CMGF=0

Check what memory types are available:

AT+CPMS=?

Should return "SM", might also show "ME", "SR" and/or "MT"

Set default memory type:

AT+CPMS="SM"

Query read and unread messages in memory type:

AT+CMGL=0
AT+CMGL=1




Also do AT+CPMS? ... which I think is going to report 30 messages ... even though AT+CMGL commands return no messages. (All your new messages arrive at index 30.)

Next try:

AT+CMGR=0
AT+CMGR=1
AT+CMGR=2
AT+CMGR=3

Do these commands return any data?

I'm theorizing that there is a modem firmware bug where AT+CMGL loses some messages, but if AT+CMGR works, we could devise a work-around.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 26
Registered: 05-2014
Posted on Monday, August 24, 2015 - 05:04 pm:   

FYI, looks like there is a message in the sim card beyond the 31 position

OK
AT+CMGF=0

OK
AT+CPMS=?

+CPMS: ("SM","ME"),("SM","ME"),("SM","ME")

OK
AT+CPMS="SM"

+CPMS: 31,40,31,40,31,40

OK
AT+CMGL=0

+CMGL: 30,0,,49
07916174850071F4040A81469.............14769341F972189404DDC36E3A888E2E83E0EFB49B 3E079DDFEE3208

OK
AT+CMGL=1
(no resposnse)
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 27
Registered: 05-2014
Posted on Monday, August 24, 2015 - 05:06 pm:   

PS: after restarting the nowsms service the 31st message was read.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5415
Registered: 08-2008
Posted on Monday, August 24, 2015 - 05:09 pm:   

The 31st was probably a new one...AT+CMGL reports it, so it is not stuck.

But what about the other 30? Does AT+CMGR show them?
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 28
Registered: 05-2014
Posted on Tuesday, August 25, 2015 - 03:52 am:   

So there are now 38 messages stuck in the sim.

AT+CMGR
returns
+CMS ERROR: 302


AT+CMGL
returns NOTHING

im going to send you a log of when it happend
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5416
Registered: 08-2008
Posted on Tuesday, August 25, 2015 - 05:16 pm:   

Clarification...did you try this syntax:

AT+CMGR=0
AT+CMGR=1
AT+CMGR=2
AT+CMGR=3

Do these commands return any data? Or just this error 302?

If those commands return data, it may be possible for us to implement a work-around...

If not, it just adds more confirmation that there is a serious firmware bug in the modem.

If we can find a way to work-around this bug, that would be great...but I don't see any clues. I think the best solution is a different modem or Android device.

It might be worth trying the latest Mobile Partner version for that modem... http://consumer.huawei.com/en/support/products/downloads/e3276-en.htm ...the newer version for Windows 8.1 is what I would try, even if running a different version of Windows.

Mobile Partner is using a proprietary interface to talk to the modem, and it is doing something to the messages that keeps them hidden from the GSM modem interface. Perhaps an update to that software would fix this bug.


--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 31
Registered: 05-2014
Posted on Tuesday, August 25, 2015 - 06:53 pm:   

so it happened again

AT+CMGL=0 return NOTHING

last time I didn't go cmgr=1

so when trying it I get messages

+CMGR: 0,,46
07916174850071F044048174100004.............DC900202392F616D6D73633F6B504574332D6 9587500

but nowsms does not process them
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5418
Registered: 08-2008
Posted on Tuesday, August 25, 2015 - 08:04 pm:   

NowSMS does not use AT+CMGR=1 (or any version of that command). NowSMS only uses AT+CMGL=0 and AT+CMGL=1.


My reason for asking is that if AT+CMGR works (as it seems to), then it is possible for us to make an update that uses the AT+CMGR commands when AT+CMGL is not working.

I need to go over this with our team.

Can you confirm that when the problem happens, AT+CMGL=0 returns no response at all, not even OK?

My thought is that if we detect this error, we could try AT+CMGR instead.

This will take a few days.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 32
Registered: 05-2014
Posted on Tuesday, August 25, 2015 - 08:23 pm:   

That is correct.
AT+CMGL=0 produced NO result what so ever.

Hmm looking into this more since CMGL lists ALL the messages and CMHR does message by message, i wonder if there is a certain message that "crashes" the CMHL and even CMHR would not be able to read.

Unfortunatly since this was the 3rd failure in 2 days I have swapped the sim card out again.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5421
Registered: 08-2008
Posted on Wednesday, August 26, 2015 - 06:42 pm:   

Possibly.

We may find that there is a particular message that remains stuck with AT+CMGR. Even if that is the case, one stuck message shouldn't stop all messages.

But time will tell. We can only guess about what the actual bug is in the modem.

My theory is a timing issue of some sort, triggered by a new message being received at the same time that NowSMS is polling the modem with AT+CMGL.

So with that in mind, here's the deal with the update...

The update will try using AT+CMGR to retrieve messages if AT+CMGL is not reporting any messages, but AT+CPMS says there are messages on the SIM.

There is also a setting to skip using AT+CMGL...and because of my theory, I'd suggest trying that. To try this, with the update, in SMSGW.INI, under [Modem - HUAWEI Mobile Connect - Modem], add ForceCMGR=Yes

I've posted a Lite update at http://www.nowsms.com/download/lite20150826.zip
And a full version update at http://www.nowsms.com/download/nowsms20150826.zip

All this said, keep in mind that something is failing in the modem itself...so this work-around may not be enough.

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 33
Registered: 05-2014
Posted on Thursday, September 17, 2015 - 03:02 am:   

Well it happened again. 34 messages stuck in the stick.

I updated the new software. and configured as you suggested.

And ALL the messages got processed. SMS and MMS
!!!So it looks like this may work!!!
Thank you

---SNIP FROM LOG---


21:52:56:017 [14] ModemReceiveMessages: Debug: 36 messages in 40 locations in storage
21:52:56:018 [14] ModemReceiveMessages: AT+CMGL=0

21:53:26:000 [14] ModemReceiveMessages: AT+CMGR=1

21:53:26:099 [14] ModemReceiveMessages:
+CMGR: 0,,158
.......
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 34
Registered: 05-2014
Posted on Thursday, September 17, 2015 - 01:04 pm:   

Update:

After the upgrade I checked this morning and found that one message was still "STUCK"

Debug log shows iterations through all the memory spaces using CMGR with results as OK until it gets to 40

AT+CMGR=40 yields
+CMS ERROR 500

Interesting. Any idea what 500 is

but its not clogging up any of the new messages coming in so its defiantly a WIN!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5452
Registered: 08-2008
Posted on Thursday, September 17, 2015 - 04:43 pm:   

That is good news!

It does confirm that the modem is getting stuck on particular messages, and does suggest a modem firmware issue.

+CMS ERROR 500 means unknown error, so that doesn't tell us much.

If you manually issue the command AT+CMGD=40 ... can it be deleted?

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 35
Registered: 05-2014
Posted on Friday, September 18, 2015 - 05:23 pm:   

No id didn't work

after further testing i found the issues was with message #1 not #40

I replaced the sim and i found that message #1 is "stuck" in the queue... while still getting error on #40

I can only deduce that the messages are numbered 0-39 not 1-40, nowsms check 1-40 and since 40 is not a valid space i got 500 and it misses message 0.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5453
Registered: 08-2008
Posted on Friday, September 18, 2015 - 08:07 pm:   

Are you sure?

Does AT+CMGR=0 return a message?

I just tried an Option modem, and AT+CMGR=0 always returns an error. The index definitely starts at 1 for this modem.

Maybe Huawei's implementation is different?

I checked the specification, but it does not address this issue. All of the examples seem to use an index that starts at 1, but this does not seem to be defined in the specification.

We could change our logic to start at 0 for this setting...but before we do that, it would help to know that AT+CMGR=0 actually works on that device.


--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 41
Registered: 05-2014
Posted on Wednesday, October 14, 2015 - 08:04 pm:   

Correct

can you add a value to define first index (that way I can specify to start with 0 not 1)

seems my cpu usage is 80% atm.

OK
at

OK
AT+CMGR=0

+CMGR: 1,,23
07916174850071F4240A81149668416400005190812191556905C270381C06

OK
AT+CMGR=1

OK
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 42
Registered: 05-2014
Posted on Wednesday, October 14, 2015 - 08:07 pm:   

Additional question

When running HEWUYI without companion, how long till the device became unresponsive.

i've run two for 48 hours now and it seems to still be working.

but not allot of sms/mms load on them
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 44
Registered: 05-2014
Posted on Monday, October 19, 2015 - 02:25 pm:   

Side note, the issue occurued again even without the companion software running.

Still getitng errors on position 40, please let me know when you can find a way of shifting the index from 1-40 to 0-39
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8124
Registered: 10-2002
Posted on Monday, October 19, 2015 - 07:33 pm:   

Hi,

Des is out for a few days...but we are planning to adjust the logic for that setting (ForceCMGR=Yes) so that it checks 0 thru 40 (or how ever many locations are supported). Some modems will always report an error at AT+CMGR=0, but that will be ignored.


quote:

Side note, the issue occurued again even without the companion software running.




Do you mean a stuck message on the modem that gives an error when trying to process?

Most likely a modem firmware bug. Have you checked the Huawei site for updates?

-bn

Bryce Norwood
Now SMS/MMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 46
Registered: 05-2014
Posted on Monday, October 19, 2015 - 07:36 pm:   

The issue is most definatly a modem bug but support for the modem have been next to 0. provider sticks to the "its not meant for texting" story while Huawei bounces me around and always end up on an email thats not answered.

I was thinking it may have been an issue with the companion software writing stuff tot he sim card but obviously thats not the case.


But other then the one issue (that the workaround seems to work great for) everything else seems to work fine! we been running a 3 stick trial over the past few day and after updating to the patched version with great results!!!

thanks guys!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8126
Registered: 10-2002
Posted on Monday, October 19, 2015 - 07:47 pm:   

An update for that setting should be ready by Wednesday.

-bn

Bryce Norwood
Now SMS/MMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5485
Registered: 08-2008
Posted on Thursday, October 22, 2015 - 03:36 pm:   

Sorry for the delay in response...I was out for a few days.

As Bryce mentioned,we have adjusted the ForceCMGR=Yes logic to start at 0. Interestingly enough, I tried with 2 different Huawei modems, and they both started at 1...so there is definitely something different about the model you have.

We've posted a Lite update at http://www.nowsms.com/download/lite20151021.zip
And a full version update at http://www.nowsms.com/download/nowsms20151021.zip

--
Des
NowSMS Support
Dark Dragon
New member
Username: Darkdrgn2k

Post Number: 47
Registered: 05-2014
Posted on Thursday, October 22, 2015 - 04:59 pm:   

The good news is i'm running 3 concurrent sticks right now and they seem to be working pretty well!

Just installed the update.

First thing i noticed is in the previous version i would see all the cmgr msgs (from 1-40) int he log

Now i only saw the one cmgr=0
is this becuase it was just looking for 1 message?

also a question about MMSINQ folder

When there are files in the folder D2a and D2I are they pending MMS downloads that have not occurred.


1 set from yesterday 1 from this morning.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5486
Registered: 08-2008
Posted on Thursday, October 22, 2015 - 05:11 pm:   

The AT+CPMS command tells us how many messages are waiting on the modem, and how many memory locations.

The logic is to start at the low number index and stop when the number of messages waiting is reached, as usually new messages go into the lowest available slot. (If a message comes in during the polling cycle, it won't be seen until the next poll, and it may be necessary to work through empty slots until the message is found.)

Previously, slot 0 was never checked, so to try to find that message, all locations 1 thru 40 were checked.

The D2A/D2I files are indexes that are used to track and discard duplicate MMS notifications.

--
Des
NowSMS Support

Add Your Message Here, or click here to start a new topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message
Action: