ERROR - Modem Response (2): +CMS ERROR: 50

ERROR - Modem Response (2): +CMS ERROR: 50 SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 02, 2006 » ERROR - Modem Response (2): +CMS ERROR: 50 « Previous || Next »
Author Message
francisco ribeiro
New member
Username: Chico_kk

Post Number: 2
Registered: 04-2006
Posted on Tuesday, April 18, 2006 - 05:58 pm:   

I'm not hable to send any SMS.
Please take a look to the debug file

16:32:39:477 [0] main: Now SMS/MMS Gateway Web server started on port number 9900
16:32:41:477 [0] main: 52 Days remaining in trial version
16:32:41:493 [2] ThreadProcessModem: Before ModemAllocate - COM2:
16:32:41:493 [2] ThreadProcessModem: After ModemAllocate - COM2: - OK
16:32:41:493 [2] ThreadProcessModem: Re-initializing modem: COM2: ...
16:32:42:493 [2] ReceiveModemCommand: Error - 3E4
16:32:43:493 [2] ReceiveModemCommand: Error - 3E4
16:32:51:493 [2] ReceiveModemCommand: Error - 3E4
16:33:07:493 [2] ReceiveModemCommand: Error - 3E4
16:33:13:008 [6] ThreadProcessConnection: Processing connection from

16:33:13:008 [6] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=966346939&Text=bvmgjk&InfoCharCounter=&PI D=&DCS=&Submit=Submit
16:33:13:008 [6] Debug: 1 recipient entries
16:33:13:008 [6] Debug: 966346939
16:33:13:008 [6] ThreadProcessConnection: Request processing complete
16:33:15:930 [2] TestModemSpeed: Initialised modem at 9600 bps
16:33:17:415 [2] ThreadProcessModem: AT+CGSMS=2
16:33:17:665 [2] ThreadProcessModem:

16:33:17:915 [2] ThreadProcessModem: Modem initialization complete: COM2:
16:33:17:915 [2] ThreadProcessModem: Processing 443BCA64.req...
16:33:17:915 [2] ThreadProcessModem: OUT: AT+CMGS=18

16:33:18:118 [2] ThreadProcessModem: IN:
16:33:18:118 [2] ThreadProcessModem: OUT: 000101098169366439F9000006F8F3F86C1603
16:33:19:055 [2] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 50
16:33:19:055 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 50
16:33:19:180 [2] ThreadProcessModem: Processing 443BCC1A.req...
16:33:19:180 [2] ThreadProcessModem: OUT: AT+CMGS=18

16:33:19:430 [2] ThreadProcessModem: IN:
16:33:19:430 [2] ThreadProcessModem: OUT: 000102098169366439F9000006627BFBAC5E03
16:33:20:586 [2] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 50
16:33:20:586 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 50
16:33:21:696 [2] ThreadProcessModem: Processing 443BCC1A.req...
16:33:21:696 [2] ThreadProcessModem: OUT: AT+CM
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5809
Registered: 10-2002
Posted on Thursday, April 20, 2006 - 01:42 pm:   


This error code "CMS ERROR: 50" indicates that SMS is not enabled for your SIM.

Try putting the SIM card into a phone, and verify that you can send SMS using the SMS client built into the phone.

If you can't send SMS with the phone either, then the error code description sounds accurate.

If you can send SMS with the phone, then this sounds like a different issue. I can see from your log that you have "SMS Access" set to "GPRS". Try changing this to "GSM" ... if that works, then this suggests that your operator does not have SMS over GPRS enabled.

If it still doesn't work with "SMS Access" set to "GSM" (and the test with the SIM in a phone did work), then the next possibility is that your modem requires the SMSC to be explicitly set when sending a message. We normally only see this issue with older GSM modems, but I did just receive a tech support issue earlier this week regarding a 3G phone that required this setting.

This SMSC address varies depending upon what operator you are subscribed to.

You can set the SMSC address by manually editing the SMSGW.INI file. Under the section header for the modem configuration (e.g., [Modem - ...], add SMSC=+phonenumber, where "+phonenumber" is the address of the SMSC. Here's a link to a good list of SMSC phone numbers: A more reliable way of determining the correct SMSC number is to put your SIM into a phone, and go through the SMS configuration menus on the phone to determine the currently configured SMSC number. When you enter the SMSC phone number, always start it with a "+" and don't include any other non-numeric characters (no dashes or dots) in the address.

Always restart the gateway service after making a change to the SMSGW.INI file.

If you try setting the SMSC value by manually editing SMSGW.INI ... if the setting doesn't make a difference, always go back in and remove it immediately so that it doesn't confuse things down the road.


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