SMS Gateway down

SMS Gateway down SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2004 » SMS Gateway down « Previous || Next »
Author Message
Wes Nam
Unregistered guest
Posted on Monday, May 10, 2004 - 07:18 pm:   

I am running two SMS gateways(5.01) each with a GSM modem. Also, I use web interface from a server program(PHP) to send out SMS and WAP Push messages.

Yesterday, both gateways interface to the modems quietly went down but kept returning "Message Submitted". So the client program didn't know
anything was wrong.

Upon inspecting the Event Logs, found the following:

Sony Ericsson GC82 EGRRS Modem:
Warning: SMS message could not be sent to XXXXXXXXXX, ERROR - Modem Response(2): +CMS ERROR: 30
Warning: SMS message could not be sent to XXXXXXXXXX, ERROR - Modem Response(2): +CMS ERROR: 513
Warning: SMS message could not be sent to XXXXXXXXXX, ERROR - Modem Response(2): +CMS ERROR: 382

Sierra Wireless AirCard GPRS Modem:
Warning: SMS message could not be sent to XXXXXXXXXX, ERROR - Modem Response(2): +CMS ERROR: 500
Error: Error Initializing SMSC Interface 'Sierra Wireless GPRS Modem'. Interface is not available.

How could these error occur without intervention? And why is the web interface always returning OK?

What can I do to improve the reliability of the service? Or at least find out easily if the service is down?

Thank you very much
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2582
Registered: 10-2002
Posted on Wednesday, May 12, 2004 - 06:45 pm:   

Wow, that is a lot of errors.

There is an error code list of CMS errors returned by GSM modems at the following link:

I have never seen CMS ERROR 30 show up sporadically. I have seen situations where a user account did not have SMS access enabled, and all attempts to send from this SIM returned that error code.

But like I say, I have never seen this as a sporadic error. I wonder if perhaps it is happening when trying to send to a particular number, and the provider is rejecting messages sent to a particular phone number. Do you get the same error each time you try to send to that phone number.

CMS ERROR 513 is a manufacturer specific value. I've checked what SonyEricsson documents that I could find, and I cannot find any documentation for it. Again, I'd ask if this is happening when sending to a particular phone number, and whether any messages can be sent to that phone number.

And I can't find any specifications that mention an error code 382. So that one is a definite mystery.

I guess with all of these errors, I am curious if they are happening sending out to specific numbers.

Also, there is a setting in the Properties for NowSMS ... SMS Access can be set to "GSM", "GPRS", or "Default".

Perhaps the device is defaulting to using "GPRS" ... and perhaps your carrier has a flaky system for SMS over GPRS. SMS over GSM might be more reliable.

"CMS ERROR 500" is an unknown error. (This is the error code reported back from the modem.) It is often caused by a weak signal strength. But I have also seen it on a Sierra Wireless Aircard 750 when messages are being received by the modem at the same time as they are being sent. NowSMS gives at least 10 retries (with delay) before it would give up sending such a message. (The default retry count is now 20 in v5.50.)

Regarding the "interface not available" message, it indicates that the modem was not accessible. NowSMS keeps retrying, but it could point to a configuration error in the PC.

So unfortunately, I'm not sure what is going on with the actual errors. The CMS ERROR codes from the GC82 are very unusual, and mostly undocumented. But maybe my advice will help some there.

Normally you just don't see too many errors like this. 500 errors occur from time to time, but retries usually handle that. The error codes from the GC82 make me wonder if perhaps it is trying to use the EDGE network (SMS over GPRS/EDGE), and maybe that is still a bit unstable.

I take your point that we need to make these error messages available through the web interface. We should probably have a system status option that indicates if one of the interfaces is down (like a modem), and that indicates if a queue is backed up, etc. We've got a maintenance release coming up pretty soon, so I'm going to see if we can some of this included in the web interface, as it is long overdue.

Wes Nam
Unregistered guest
Posted on Wednesday, May 12, 2004 - 10:48 pm:   

Thanks for your reply.

Indeed I was using Default for 'GSM/GPRS' option.
I will set it to GSM to see if it'll be more

About Error 30, this actually happened when operator's SMS was down system-wide(Cingular in LA area).


Login Login / Register Logout Logout Search Last 30 Days Topics Topics