Unable to Send SMS using SMS Gateway

Unable to Send SMS using SMS Gateway SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 20, 2013 » Unable to Send SMS using SMS Gateway « Previous || Next »
Author Message
Wycliffe Seda
New member
Username: Wseda

Post Number: 1
Registered: 10-2012
Posted on Thursday, October 04, 2012 - 08:21 am:   

Software: Now SMS/MMS Gateway v2012.06.28
Setup: Modem connected to computer
SMSC Status: All Connections OK
OS: Win 7 home premium
Error Seen in Gateway:
LastErrorInfo=ERROR - Modem Response (2): +CMS ERROR: 500 -- COM15:

Error from SMSOUT file:
2012-10-04 02:05:33,506C245C.req,127.0.0.1,+14254428003,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 500 -- COM15:,SubmitUser=wseda

I have been unable to send any text messages since installing the gateway. Is there something blocking the COM port? Is there a way for me to determine this, resolve the issue and start sending SMS messages?

Help!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4108
Registered: 08-2008
Posted on Thursday, October 04, 2012 - 12:42 pm:   

Hi,

What is the modem that you are using?

The error code that is coming back from the modem when NowSMS tries to send a message is "+CMS ERROR: 500", which means "Unknown Error".

Some modems return this error if the modem has no service or very poor signal strength. If you enable the SMSDEBUG.LOG, we record some information in there about other diagnostic commands that can tell us more about this. Specifically you'll see AT+COPS? and AT+CSQ in the SMSDEBUG.LOG during modem initialisation after startup.

So as a starting point, I'd ask the following questions:

1.) What modem is it?

2.) Does the modem have an active SIM card? (An easy way to verify is to move the SIM to a phone and verify that the phone can connect to the operator and send text.)

3.) Enable the SMSDEBUG.LOG and restart the NowSMS service. Try sending again and attach that log as a reply post to this message, or just extract the AT+COPS? and AT+CSQ info that I asked about.

--
Des
NowSMS Support
Wycliffe Seda
New member
Username: Wseda

Post Number: 2
Registered: 10-2012
Posted on Friday, October 05, 2012 - 01:40 pm:   

Hi Des,

Thank you for your help. I hope we can rectify this soon.

1) The modem I am using is a Wavecom Modem from China
2) There is an active sim card in one slot
3) Attached is the SMSDebug log.

Let me know your thoughts. The SMSDebug file is below.

Wycliffe

01:53:06:942 [0] UseRouteCache: Yes
01:53:25:709 [1] ThreadListenForConnections: Before accept
01:53:25:709 [1] ThreadListenForConnections: After accept
01:53:25:709 [1] ThreadListenForConnections: Before accept
01:53:25:709 [1] ThreadListenForConnections: After accept
01:53:25:709 [17] ThreadProcessConnection: Processing connection from 127.0.0.1:25795...
01:53:25:724 [18] ThreadProcessConnection: Processing connection from 127.0.0.1:26051...
01:53:25:724 [17] TheadProcessConnection: Updating cached user info
01:53:25:724 [17] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=%2B14254428003&Sender=&Text=Modem+Test&In foCharCounter=&PID=&DCS=&ReceiptRequested=No&DestPort=&DelayUntil=&Submit=Submit
01:53:25:724 [17] Debug: 1 recipient entries
01:53:25:724 [17] MessageRoutesAdd: wseda\506C245C.req
01:53:25:724 [17] MessageRoutesAdd: COM15:
01:53:26:021 [12] ThreadProcessModem: Processing 506C245C.req...
01:53:26:052 [12] ThreadProcessModem: OUT: AT+CMGS=2201:53:26:083 [12] ThreadProcessModem: IN:
>
01:53:26:083 [12] ThreadProcessModem: OUT: 0001020B914152448200F300000ACD37B9DC0651CB733A
01:53:26:130 [12] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 500
01:53:26:130 [12] ThreadProcessModem: OUT: 
01:53:26:239 [12] ThreadProcessModem: OUT: \r
01:53:26:239 [12] ThreadProcessModem: OUT: AT
01:53:26:286 [12] ThreadProcessModem: IN:
OK

01:53:37:097 [12] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 500
01:53:38:158 [12] ModemTest: COM15:
01:53:38:329 [12] ModemTest: OK
01:53:40:217 [12] ThreadProcessModem: Processing 506C245C.req...
01:53:40:248 [12] ThreadProcessModem: OUT: AT+CMGS=2201:53:40:279 [12] ThreadProcessModem: IN:
>
01:53:40:279 [12] ThreadProcessModem: OUT: 0001030B914152448200F300000ACD37B9DC0651CB733A
01:53:40:326 [12] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 500
01:53:40:326 [12] ThreadProcessModem: OUT: 
01:53:40:435 [12] ThreadProcessModem: OUT: \r
01:53:40:435 [12] ThreadProcessModem: OUT: AT
01:53:40:482 [12] ThreadProcessModem: IN:
OK

01:53:51:016 [12] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 500
01:53:52:019 [12] ModemTest: COM15:
01:53:52:206 [12] ModemTest: OK
01:53:52:206 [12] ModemTest: COM15:
01:53:52:378 [12] ModemTest: OK
01:53:56:169 [12] ThreadProcessModem: Processing 506C2074.req...
01:53:56:200 [12] ThreadProcessModem: OUT: AT+CMGS=2501:53:56:231 [12] ThreadProcessModem: IN:
>
01:53:56:231 [12] ThreadProcessModem: OUT: 0001040B814152448200F300000DD4F29C9E769F41ED37B9DC06
01:53:56:278 [12] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 500
01:53:56:278 [12] ThreadProcessModem: OUT: 
01:53:56:387 [12] ThreadProcessModem: OUT: \r
01:53:56:387 [12] ThreadProcessModem: OUT: AT
01:53:56:434 [12] ThreadProcessModem: IN:
OK

01:54:07:243 [12] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 500
01:54:08:038 [12] ModemTest: COM15:
01:54:08:210 [12] ModemTest: OK
01:54:22:032 [12] ThreadProcessModem: Processing 506C245C.req...
01:54:22:063 [12] ThreadProcessModem: OUT: AT+CMGS=2201:54:22:094 [12] ThreadProcessModem: IN:
>
01:54:22:094 [12] ThreadProcessModem: OUT: 0001050B914152448200F300000ACD37B9DC0651CB733A
01:54:22:141 [12] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 500
01:54:22:141 [12] ThreadProcessModem: OUT: 
01:54:22:250 [12] ThreadProcessModem: OUT: \r
01:54:22:250 [12] ThreadProcessModem: OUT: AT
01:54:22:297 [12] ThreadProcessModem: IN:
OK

01:54:25:807 [18] ProcessRead: End of socket
01:54:25:807 [17] ProcessRead: End of socket
01:54:25:807 [18] WaitForSocketClose: WinSock reported ioctlsocket complete
01:54:25:807 [17] WaitForSocketClose: WinSock reported ioctlsocket complete
01:54:25:807 [18] ThreadProcessConnection: Request processing complete
01:54:25:807 [17] ThreadProcessConnection: Request processing complete
01:54:33:100 [12] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 500
01:54:34:161 [12] ModemTest: COM15:
01:54:34:364 [12] ModemTest: OK

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