Error processing incoming SMS | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 10, 2005 ⬆ |
◄ ► |
Author | Message | |||
quickstart Unregistered guest |
I'm a newbie to nowsms, and am really impressed to be able to successfuly install, configure, and send sms in about 1 hour, and even using url to submit send requests! I start to encounter problem when I try to use 2-way SMS to receive sms. I used the "*" command prefix and set an http command to run a simple asp page: http://{mysite}/incoming.asp?x1=@@SENDER@@&x2=@@sms@@ which just returns a string (in plain/text format): <% Response.ContentType = "plain/text" Response.Write("Thank you!") %> The modem seem to have captured the request but ended in error somewhere. The event was not reflected in the NowSMS statistics on the Serial # tab. Here is the debug info: 21:21:48:281 [0] main: Now SMS/MMS Gateway Web server started on port number 32003 21:21:50:296 [0] main: Now SMS/MMS Gateway SMPP server started on port number 32005 21:21:50:296 [0] main: 60 Days remaining in trial version 21:21:50:343 [3] ThreadProcessModem: Before ModemAllocate - COM1: 21:21:50:343 [3] ThreadProcessModem: After ModemAllocate - COM1: - OK 21:21:50:343 [3] ThreadProcessModem: Re-initializing modem: COM1: ... 21:21:52:593 [3] TestModemSpeed: Initialised modem at 115200 bps 21:21:52:906 [3] ThreadProcessModem: AT+CPMS? 21:21:52:968 [3] ThreadProcessModem: +CPMS: "SM",1,10,"SM",1,10 OK 21:21:52:968 [3] ThreadProcessModem: AT+CNMI? 21:21:53:031 [3] ThreadProcessModem: +CNMI: 0,1,0,0,0 OK 21:21:53:031 [3] ThreadProcessModem: AT+CPMS=? 21:21:53:093 [3] ThreadProcessModem: +CPMS: (("SM","BM","SR"),("SM")) OK 21:21:53:156 [3] ThreadProcessModem: AT+CGSMS=2 21:21:53:265 [3] ThreadProcessModem: OK 21:21:53:265 [3] ThreadProcessModem: Modem initialization complete: COM1: 21:21:53:656 [3] ModemReceiveMessages: +CMGL: 1,0,,21 07915892945897F5040B945892871220F9000050304112126423024136 OK 21:21:53:656 [3] ModemReceiveMessages: Decoding received message index 1 from message storage ME 21:21:53:656 [3] ModemReceiveMessages: 07915892945897F5040B945892871220F9000050304112126423024136 21:21:53:656 [3] ModemReceiveMessages: SMSC address len = 7 21:21:53:656 [3] ModemReceiveMessages: SMSC Address = +85294985795 21:21:53:656 [3] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 21:21:53:656 [3] ModemReceiveMessages: Sender address len = 11 21:21:53:656 [3] ModemReceiveMessages: Sender Address = 85297821029 21:21:53:656 [3] ModemReceiveMessages: PID = 00 21:21:53:656 [3] ModemReceiveMessages: DCS = 00 21:21:53:656 [3] ModemReceiveMessages: Anticipated user data length = 2 21:21:53:656 [3] ModemReceiveMessages: Message = Al 21:21:53:656 [3] ModemReceiveMessages: AT+CMGD=1 21:21:54:250 [3] ModemReceiveMessages: OK 21:21:54:359 [5] ThreadProcessInboundSMS: Processing 42358FF1.in... 21:30:59:406 [3] ThreadProcessModem: Processing 42357A4B.req... 21:30:59:406 [3] ThreadProcessModem: OUT: AT+CMGS=24 21:30:59:468 [3] ThreadProcessModem: IN: > 21:30:59:468 [3] ThreadProcessModem: OUT: 00410008817928019200F50D06050415811581332a32a3920d0 21:30:59:531 [3] ThreadProcessModem: ERROR - Modem Response (2): ERROR 21:30:59:531 [3] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 21:40:59:609 [3] ThreadProcessModem: Processing 42357A4B.req... 21:40:59:609 [3] ThreadProcessModem: OUT: AT+CMGS=24 21:40:59:671 [3] ThreadProcessModem: IN: > 21:40:59:671 [3] ThreadProcessModem: OUT: 00410008817928019200F50D06050415811581332a32a3920d0 21:40:59:734 [3] ThreadProcessModem: ERROR - Modem Response (2): ERROR 21:40:59:734 [3] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 22:00:00:125 [0] main: 60 Days remaining in trial version Kindly advise what have I missed. Many thanks! Dave | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4170 Registered: 10-2002 |
Hi Dave, Can I see your SMSGW.INI file, which will tell me what the "2-way" command is that you have configured. I suspect the "2-way" command is not configured properly, as I see NowSMS recognising the received message, and writing it to the SMS-IN queue, but it does not see that there is a matching "2-way" command defined to process it. -bn |