CMS: 500 Error with Siemens MC35 on Win2003 64Bit

CMS: 500 Error with Siemens MC35 on Win2003 64Bit SearchSearch

SMS & MMS Technical Forum » NowSMS Lite (Product Support Only) » CMS: 500 Error with Siemens MC35 on Win2003 64Bit « Previous || Next »
Author Message
Tobias Ratschkowski
New member
Username: Newandis

Post Number: 1
Registered: 02-2011
Posted on Saturday, February 19, 2011 - 07:59 am:   

Hello!
Iam currently evaluating NowSMS Lite and it would perfectly fit to our needs...but it seems that it doesnt like our hardware.

NowSMS Lite is install on Windows 2003 R2 64Bit Server, using a Siemens MC35 Serieal GSM Modem.

We tried the Modem though Serial terminal and we are able to send SMS.

Since we dont have a modem driver, we used the standrad 33.6 modem. But we are unable to send an SMS, everytime we got an CMS500 Error.

Maybe someone have a tip for us?

Many, many thanks!!

SMSDEBUG:
11:43:32:609 [0] UseRouteCache: No
11:43:34:625 [0] main: Now SMS/MMS Gateway v2010.11.04 Web server started on port number 8800
11:43:34:625 [8] ThreadProcessModem: Standard 33600 bps Modem
11:43:34:625 [0] main: 29 Days remaining in trial version
11:43:34:625 [8] ThreadProcessModem: Before ModemAllocate - Standard 33600 bps Modem
11:43:34:625 [8] ThreadProcessModem: After ModemAllocate - Standard 33600 bps Modem - OK
11:43:34:625 [8] ThreadProcessModem: Re-initializing modem: Standard 33600 bps Modem ...
11:43:44:265 [8] ThreadProcessModem: ATI0
11:43:44:265 [8] ThreadProcessModem:
OK

11:43:44:484 [8] ModemTest: Standard 33600 bps Modem
11:43:44:828 [8] ModemTest: OK
11:43:44:828 [8] ThreadProcessModem: AT+CGSMS=3
11:43:44:906 [8] ThreadProcessModem:
OK

11:43:44:968 [8] ThreadProcessModem: AT+CNMI?
11:43:45:046 [8] ThreadProcessModem:
+CNMI: 0,0,0,0,1

OK

11:43:45:046 [8] ThreadProcessModem: AT+CNMI=?
11:43:45:109 [8] ThreadProcessModem:
+CNMI: (0-3),(0,1),(0,2,3),(0,2),(1)

OK

11:43:45:109 [8] ThreadProcessModem: AT+COPS?
11:43:45:187 [8] ThreadProcessModem:
+COPS: 0,0,"o2 - de"

OK

11:43:45:187 [8] ThreadProcessModem: AT+CSQ
11:43:45:250 [8] ThreadProcessModem:
+CSQ: 14,99

OK

11:43:45:250 [8] ThreadProcessModem: AT+CNUM
11:43:45:328 [8] ThreadProcessModem:
ERROR

11:43:45:328 [8] ThreadProcessModem: Modem initialization complete: Standard 33600 bps Modem
11:43:45:328 [8] ThreadProcessModem: Processing TEST75CD.REQ...
11:43:45:390 [8] ThreadProcessModem: OUT: AT+CMGS=31

11:43:45:468 [8] ThreadProcessModem: IN:
>
11:43:45:468 [8] ThreadProcessModem: OUT: 0001010D81945121577578F6000013CEF77DDA9C82A8E5391DD42CCFE7E17319
11:43:48:390 [8] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 500
11:43:48:390 [8] ThreadProcessModem: OUT: 
11:43:48:500 [8] ThreadProcessModem: OUT: \r
11:43:48:500 [8] ThreadProcessModem: OUT: AT
11:43:48:578 [8] ThreadProcessModem: IN:
OK

11:43:49:078 [8] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 500
11:43:50:078 [8] ModemTest: Standard 33600 bps Modem
11:43:50:421 [8] ModemTest: OK
11:43:52:000 [8] ThreadProcessModem: Processing TEST75CD.REQ...
11:43:52:062 [8] ThreadProcessModem: OUT: AT+CMGS=31

11:43:52:140 [8] ThreadProcessModem: IN:
>
11:43:52:140 [8] ThreadProcessModem: OUT: 0001020D81945121577578F6000013CEF77DDA9C82A8E5391DD42CCFE7E17319
11:43:55:234 [8] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 500
11:43:55:234 [8] ThreadProcessModem: OUT: 
11:43:55:343 [8] ThreadProcessModem: OUT: \r
11:43:55:343 [8] ThreadProcessModem: OUT: AT
11:43:55:421 [8] ThreadProcessModem: IN:
OK

11:43:56:171 [8] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 500
11:43:57:171 [8] ModemTest: Standard 33600 bps Modem
11:43:57:515 [8] ModemTest: OK
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2929
Registered: 08-2008
Posted on Monday, February 21, 2011 - 01:39 pm:   

Hi Tobias,

You say that you were able to send an SMS message successfully through serial terminal?

Do you mean direct AT commands? I assume you used text mode, instead of the binary PDU mode that you see in the NowSMS debug logs, correct?

You can configure NowSMS to use text mode by editing SMSGW.INI and under the [Modem - Standard 33600 bps Modem] header, adding:

ModemTextMode=Yes

(Restart the service after making this change.)

I normally wouldn't suggest trying this, but since you say you can send ok from a serial terminal, I'm curious if this makes a difference.

Of course, setting this value is not a great solution, as it prevents you from sending any binary messages ... or long text messages.

So, I'm curious what else the issue could be.

"CMS ERROR: 500" is officially documented as an unknown error. Usually when we see these errors it is a signal strength issue. From what I can see in the logs, the modem is trying to do something with the message. It takes 3 seconds before the modem comes back with the error message.

The init commands show NowSMS sending an AT+CSQ command to the modem to test the signal strength. A value of 14 should be OK ... not great, but it should be acceptable.

Anything you could do to boost the signal into the range where AT+CSQ returns a value in the first number of 20 or higher would be good.

--
Des
NowSMS Support
Tobias Ratschkowski
New member
Username: Newandis

Post Number: 2
Registered: 02-2011
Posted on Monday, February 21, 2011 - 02:51 pm:   

Thanks for your quick response. You are right, this setting doesnt help.

I have also tried to set the baudrate to lower speed..9600..cause thats the speedrate that works using textterminal.

I use this command to send me an sms:
ATZ
AT+CMGF=1 (switch to Textmode)
AT+CMGS="+49myhandy"
>Test Test

Than: CTL-Z to send the message.

Have you any other INI Settings i could try?

Thanks a lot!!
tobias
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2932
Registered: 08-2008
Posted on Monday, February 21, 2011 - 03:40 pm:   

Hi Tobias,

That is very odd.

The only thing I can think of that might be different is that AT+CGSMS=3 setting that we are sending.

We use this as a default setting in NowSMS Lite, whereas we don't in the regular NowSMS.

It sets the SMS sending mode to circuit-switched ... most modems default to packet-switched with fallback to circuit-switched, but most operators have packet-switched SMS support turned off.

Try changing the "SMS Access" to "GSM" (circuit switched) and see if this makes a difference.

When you had "ModemTextMode=Yes" in the settings, did you see NowSMS using text mode like in your serial mode test?

--
Des
NowSMS Support
Tobias Ratschkowski
New member
Username: Newandis

Post Number: 3
Registered: 02-2011
Posted on Tuesday, February 22, 2011 - 06:51 am:   

Good Morning ;)

I test it again, but we got the same error. Yes, it use the text mode, please see the debug.


And, why gave the AT+CNUM an error?


*************************************************
08:44:20:402 [0] UseRouteCache: No
08:44:22:418 [0] main: Now SMS/MMS Gateway v2010.11.04 Web server started on port number 8800
08:44:22:418 [4] ThreadProcessModem: Standard 9600 bps Modem
08:44:22:418 [0] main: 25 Days remaining in trial version
08:44:22:418 [4] ThreadProcessModem: Before ModemAllocate - Standard 9600 bps Modem
08:44:22:418 [4] ThreadProcessModem: After ModemAllocate - Standard 9600 bps Modem - OK
08:44:22:418 [4] ThreadProcessModem: Re-initializing modem: Standard 9600 bps Modem ...
08:44:23:137 [4] ThreadProcessModem: ATI0
08:44:23:137 [4] ThreadProcessModem:
OK

08:44:23:434 [4] ModemTest: Standard 9600 bps Modem
08:44:23:918 [4] ModemTest: OK
08:44:23:918 [4] ThreadProcessModem: AT+CGSMS=3
08:44:23:996 [4] ThreadProcessModem:
OK

08:44:24:074 [4] ThreadProcessModem: AT+CNMI?
08:44:24:184 [4] ThreadProcessModem:
+CNMI: 0,0,0,0,1

OK

08:44:24:184 [4] ThreadProcessModem: AT+CNMI=?
08:44:24:293 [4] ThreadProcessModem:
+CNMI: (0-3),(0,1),(0,2,3),(0,2),(1)

OK

08:44:24:293 [4] ThreadProcessModem: AT+COPS?
08:44:24:402 [4] ThreadProcessModem:
+COPS: 0,0,"o2 - de"

OK

08:44:24:402 [4] ThreadProcessModem: AT+CSQ
08:44:24:496 [4] ThreadProcessModem:
+CSQ: 14,99

OK

08:44:24:496 [4] ThreadProcessModem: AT+CNUM
08:44:24:574 [4] ThreadProcessModem:
ERROR

08:44:24:574 [4] ThreadProcessModem: Modem initialization complete: Standard 9600 bps Modem
08:44:44:090 [4] ThreadProcessModem: Processing TESTF5F8.REQ...
08:44:44:184 [4] ThreadProcessModem: OUT: AT+CMGS="+49151xxxxxx"

08:44:44:293 [4] ThreadProcessModem: IN:
>
08:44:44:293 [4] ThreadProcessModem: OUT: NowSMS Test Message
08:44:47:402 [4] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 500
08:44:47:402 [4] ThreadProcessModem: OUT: 
08:44:47:512 [4] ThreadProcessModem: OUT: \r
08:44:47:512 [4] ThreadProcessModem: OUT: AT
08:44:47:574 [4] ThreadProcessModem: IN:
OK
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2936
Registered: 08-2008
Posted on Tuesday, February 22, 2011 - 08:09 pm:   

Hi Tobias,

I can't understand why your serial terminal test would work, but NowSMS would consistently fail with "CMS ERROR: 500".

I wish I had a quick answer, but this is not anything I've encountered before. Usually I would suspect "CMS ERROR: 500" to point to low signal strength, or less likely, a SIM card that is out of credits for sending SMS.

But if it works consistently from a serial terminal (and you are not sending anything unusual in that instance), then this suggests that something different is happening when NowSMS sends the message.

The first thing I'd suggest is double checking the port number associated with the Windows modem driver. Make sure it is the same COM port number that you are using when you send from the serial terminal. Especially check this if you are using a USB port for the modem as many USB modems expose multiple COM ports, where some virtual COM ports support SMS related commands in syntax, but not in actual operation.

Also, please confirm again that you can still send an SMS via serial terminal commands without any problem. For some USB devices, if there is some other manufacturer supplied software installed, that software might be talking to the modem via another protocol and preventing the normal AT commands from being able to work properly.

Out of curiosity, what are you using for serial terminal access?

The only other thing that I can think of is that if you are sending the commands via serial terminal, the speed at which the characters are sent to the terminal is obviously much slower. While there is no configuration setting to slow NowSMS down that much, there is a configuration setting to send characters to the modem one at a time instead of buffering. This is enabled by adding ModemMaxBytesPerSend=1 under the [SMSGW] header in SMSGW.INI. I'm skeptical that this would make a difference. I'm hopeful it's a port issue or conflict with some other modem software.

--
Des
NowSMS Support
Tobias Ratschkowski
New member
Username: Newandis

Post Number: 4
Registered: 02-2011
Posted on Friday, February 25, 2011 - 02:35 pm:   

Hi, finaly its working!

The Problem was a wrong SMSC...i put in the right one with AT+CSCA="+491760000433" using the terminal and works now!

I wish to say Thank you verry much for your help!!

All i need to know is now, how to license the Lite Version..cause its working wonderfull now with our Application.

Have a nice Weekend,
tobias
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2958
Registered: 08-2008
Posted on Friday, February 25, 2011 - 05:32 pm:   

Hi Tobias,

Under the [Modem - Standard 33600 bps Modem] header in SMSGW.INI, I would recommend removing the following statement that I had you add previously:

ModemTextMode=Yes

In its place, add:

SMSC=+491760000433

This will put NowSMS back in its preferred PDU mode and send the SMSC address in the PDU mode equivalent to the AT+CSCA command.

For licensing info, contact our sales department via one of the methods listed at http://www.nowsms.com/contact. I will also forward them this message thread to them, and ask them to e-mail you details on Monday.

--
Des
NowSMS Support
Paul Mullett
New member
Username: Pmullett

Post Number: 1
Registered: 03-2013
Posted on Tuesday, March 26, 2013 - 02:14 pm:   

Hi Tobias,

I'm looking for compatible modem driver for the Siemens MC35 so that I can connect and use it on Windows 2003 / 2008 R2 systems. It looks like you had it working on 2003 R2.

Can you point me in the direction of the driver you used to connect and use the MC35 device?

Many thanks,

Paul.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4340
Registered: 08-2008
Posted on Tuesday, March 26, 2013 - 02:56 pm:   

Hi Paul,

As long as the modem already shows up as a COM port, you can just use the Standard 33600 bps Modem driver from Windows.

(Despite the speed reference, it will not be limited to 33600 bps. This is just the most generic modem driver in Windows.)

--
Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

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