CMS ERROR: 500s ???

CMS ERROR: 500s ??? SearchSearch
Author Message
francis
Unregistered guest
Posted on Wednesday, May 12, 2004 - 06:33 pm:   

Hello, there. I have been getting this error a lot of times!

2004-05-09 00:03:45,409D4AE5.req,127.0.0.1,7408798,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 500S ??? -- Sony Ericsson T300 Series IR Modem


Does anybody know what it means and what's the cause of this problem?

Any help will be gladly appreciated,
francis
Unregistered guest
Posted on Wednesday, May 12, 2004 - 07:31 pm:   

Dear Mr. Norwood,

I've read in a POST that it seems to have something to do with the signal strength of the carrier. But they mentioned specifically ERROR 500, and not ERROR 500s. Do u know what's the difference, or perhaps it's more useful if I can read a error library, although I can't seem to find one on the NOWSMS website.

Sincerely yours,
Francis L.
francis
Unregistered guest
Posted on Wednesday, May 12, 2004 - 08:08 pm:   

Dear Mr. Norwood,

This is the POST/THREAD that I was refering to:
http://support.nowsms.com/discus/messages/1/258.htm l

So, my question is, if the ERROR 500 is the same as ERROR 500s.

Thanks again,
Francis L
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2580
Registered: 10-2002
Posted on Wednesday, May 12, 2004 - 08:10 pm:   

Hi Francis,

I've never seen 500S as a documented error code. CMS ERROR codes are numeric. There is a list of the different codes here:

http://support.nowsms.com/discus/messages/1/829.html

500S might mean something specific to your modem manufacturer, or it may just be a typo within their firmware.

Basically 500 errors are a headache to troubleshoot, because they just mean "unknown error". The developers of modem firmware often just use this code as a catch-all error because none of the other defined error codes seemed to apply.

How often are you seeing them?

I've noticed with a Sierra Aircard 750 that I get a lot of these if the modem is receiving messages while I am attempting to send them out. The messages always get sent on a subsequent retry, but the modem just does not handle sending and receiving at the same time very well. (In my case, my operator supports SMS over GPRS, and if I configure NowSMS to send using SMS over GPRS with that device, I do not see this problem, or this error code.)

So I guess the question is ... how often are you seeing them?

It could be a signal strength issue. That is very common for this type of problem.

It could also be a case like I described. (Try enabling the SMS over GPRS setting in NowSMS under properties for the modem. If you try this, and the messages are not sent out, go back and set it for SMS over GSM.)

How often do you see the error, and do the messages get sent out after a retry, or do particular messages seem to consistently fail?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2583
Registered: 10-2002
Posted on Wednesday, May 12, 2004 - 08:47 pm:   

CMS ERROR 500 can also be caused by invalid formatted messages.

Generally I'd only expect to see that, however, if you are creating your own binary messages. And it often points to a UDH problem.
francis
Unregistered guest
Posted on Wednesday, May 12, 2004 - 09:16 pm:   

Hi Mr. Norwood,

Where do I begin.
I'm seeing it alot of times. And I mean alot!
My Eventviewer is jam-packed with those messages.

This is my environment. One Digicel phone Sony T300, with IrDA capability. It al worked fine in the beginning. But after a while I've noticed that a few people were trying to send messages via email with the number 555. And after that, everything went crazy. To see if the phone could still send SMS to a few users, I've tried making a while-loop in PHP to send every phone a message. It didn't work. I must also say that I am using a GSM network, and not GPRS. But the network supports GPRS. Do I need to change the settings for GPRS in NOWSMS and my phone? Or just NOWSMS?

I've also tried comparing the timestamp of a few SMS coming from the same number. In other words, If I can see a similar pattern in both log-files, that means that the phone is sending even when it sends the error 500s. But that wasn't the case. So I guess it doesn't send.

Maybe it's because the phone cannot handle so many messages at once. The SMS rate over a GSM network with a single thread is about 3 to 4 times a minute, right? Well, I think that I have surpassed that.

Below are two records of the SMSIN/SMSOUT log-files:
<<SMS OUT>>
2004-05-08 04:43:10,409C88D1.req,127.0.0.1,555,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 500S ??? -- Sony Ericsson T300 Series IR Modem

<<SMS IN>>
2004-05-08 04:43:11,555,Text,Could not send to Pa. Please enter full email as the first word in the message.

(The SMS that you see above(SMS IN from number 555), just keeps coming and coming.)

If this is just a classic case of too much traffic, then I guess I must switch to multi-threading and buy NOWSMS v5.5. What is the first thing that I must do to support multithread? extra phone? with the same SIM? Or how does the re-routing work?

An answer on any of these question will be gladly appreciated.

Sincerely yours,
Francis L.
francis
Unregistered guest
Posted on Wednesday, May 12, 2004 - 09:25 pm:   

I don't think that I am making my own binary messages. LoL

But I do receive some, once a while. I think it's kind of odd. Here's an example:

2004-05-08 17:55:08,7430570,Binary,00C5007200FA00DF00E4002700240020004600ED00F100EB00A70074 003A002000570068006100740020007500700020006D00790020006E006900670067006500720073

I don't have any clue why it's binary.

BTW: What I meant in the previous post was that the phone doesn't send a message when an error is reported.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2587
Registered: 10-2002
Posted on Wednesday, May 12, 2004 - 11:03 pm:   

Francis,

Are all of these "500S" errors occurring on attempts to send a message to "555"?

If so, you probably don't want to send to that number, right?

I'm starting to think 555 is looping back to you somehow.

Let's do a trick to effectively kill traffic going out to 555.

In NowSMS, go into the "SMS Users" dialog. Create a user account. Give it an obscure account name and password.

Check "Enable SMPP Login for this User".

Check "Route Received messages to user via SMPP".

In "Recipient address(es) to route to this user", add "555".

This will effectively trap the 555 messages, and stop them from going out.

Before you look at adding another modem, I'd try to get a cable instead of the IrDA link.

And don't worry about the binary message received. That is just a message in Unicode format. The log logs it as a binary message, but we convert it to text before processing, as we recognise it is in Unicode format.
francis
Unregistered guest
Posted on Thursday, May 13, 2004 - 10:02 am:   

No, I don't want to receieve any mess. from 555.

Thanks again for the tip. Hopefully that will stop the problem.
I will also try to change the cable to a serial one.

Thanks again, I'll let u know if it doesn't work.