PDU SMS

PDU SMS Search Search

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through April 08, 2009 » PDU SMS « Previous || Next »
Author Message
Igor Vuksanović
New member
Username: Rogibabarogi

Post Number: 2
Registered: 02-2009
Posted on Thursday, March 19, 2009 - 12:14 pm:   

Hi,
I am receiving some PDU smss, suppose from SMSC and I don't know what is their content. I tried to read them with Pduspy, but nothing with sence came out.
Same time my modem stuck, error cms 535, Protocol stack busy. What does it means.
I would appreciate some help
There are attached logs.
Thanks in advance
Igor
application/octet-streamSMSIn log
SMSIN-20090319.log (21.3 k)
text/plainsmsout log
smsout_20090319.txt (1.7 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 617
Registered: 08-2008
Posted on Thursday, March 19, 2009 - 07:11 pm:   

Hi Igor,

Which messages are you referring to?

The ones that start with: 0B05040B8423F0?

That is a WAP push header. I didn't do a full decode, but I'm guessing those are MMS notification messages.

For the CMS ERROR 535, you might want to try the NowSMS 2009 release candidate @ http://www.nowsms.com/download/nowsms2009rc.zip. I seem to recall an issue where some modems got stuck with this error if a message came in at a critical time while a message was in the process of being sent out. We made some changes to NowSMS to help the modem recover before it became hopelessly confused. I think this was with the Multitech EDGE modems that use the Siemens chipset.

--
Des
NowSMS Support
Igor Vuksanović
New member
Username: Rogibabarogi

Post Number: 3
Registered: 02-2009
Posted on Friday, March 20, 2009 - 01:17 pm:   

Hi Des,
I just installed this patch, but now I got CMS ERROR 538 - Invalid parameter.
There is part of smsdebug log:
13:03:36:765 [0] main: Now SMS/MMS Gateway v2009.03.07 Web server started on port number 8801
13:03:38:765 [0] main: preferred sender = +385995847406,Standard 33600 bps Modem
13:03:38:765 [2] ThreadProcessModem: Standard 33600 bps Modem
13:03:43:765 [2] ThreadProcessModem: Before ModemAllocate - Standard 33600 bps Modem
13:03:43:765 [2] ThreadProcessModem: After ModemAllocate - Standard 33600 bps Modem - OK
13:03:43:765 [2] ThreadProcessModem: Re-initializing modem: Standard 33600 bps Modem ...
13:03:44:562 [2] ThreadProcessModem: ATI0
13:03:44:562 [2] ThreadProcessModem:
OK

13:03:44:968 [2] ThreadProcessModem: AT+CPMS?
13:03:45:109 [2] ThreadProcessModem:
+CPMS: "SM",0,30,"MT",3,55,"MT",3,55

OK

13:03:45:109 [2] ThreadProcessModem: AT+CNMI=2,2,2,1,0
13:03:45:234 [2] ThreadProcessModem:
+CMS ERROR: 538

13:03:45:234 [2] ThreadProcessModem: AT+CNMI=2,2
13:03:45:359 [2] ThreadProcessModem:
OK

13:03:45:359 [2] ThreadProcessModem: AT+CNMI=,,,1
13:03:45:484 [2] ThreadProcessModem:
+CME ERROR: 21

13:03:45:484 [2] ThreadProcessModem: AT+CNMI?
13:03:45:609 [2] ThreadProcessModem:
+CNMI: 2,2,0,0,1

OK

13:03:45:609 [2] ThreadProcessModem: AT+CPMS=?
13:03:45:750 [2] ThreadProcessModem:
+CPMS: ("ME","SM","MT"),("ME","SM","MT"),("SM","MT")

OK

13:03:45:750 [2] ThreadProcessModem: AT+CPMS="ME","ME","ME"
13:03:45:890 [2] ThreadProcessModem:
+CMS ERROR: 538

13:03:46:015 [2] ThreadProcessModem: Modem initialization complete: Standard 33600 bps Modem

I can't receive any sms.
Thanks
Igor
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 625
Registered: 08-2008
Posted on Friday, March 20, 2009 - 07:24 pm:   

Hi Igor,

The CMS ERROR 538 is not fatal. At least, it's not triggering any problem.

We've just had problems with some modems that default to receiving messages to the SIM, and having the modems lockup under load.

So if a preferred storage is not set in the configuration, we try to set it to "ME".

However, there is severe problem in this update that effects any modems that require polling for message retrieval. (The earlier "CME ERROR: 21" is an indication that the modem does not support this mode.)

We made a change in the default receive messages settings to try to enable direct routing of received messages over the modem interface without polling. The intent was a hybrid interface that had the performance of direct routing if available, plus polling. However, in many configurations, polling the modem for received messages was disabled.

I believe you can work around this by explicitly setting "SMS Message Storage" to be either "Device Memory" or "SIM".

However, a better solution is an update that fixes the problem.

Download http://www.nowsms.com/download/nowsms20090317.zip for a replacement version.

--
Des
NowSMS Support

Login Login / Register Search Search   Home Home
Logout Logout Topics Topics Search Last 1|3|7|30 Days   Previous Page Previous Next Next Page