Problem receive sms (uRgent!!) | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
Author | Message | |||
newie New member Username: Bluekutuk Post Number: 6 Registered: 09-2006 |
hi, i'm trying 2-way sms. i use vb.net. i've problem with receive sms. i've success test with "command to execute" is "c:\winnt\system32\cmd.exe /c echo Echo @@FULLSMS@@”. and user can receive back the messages. but when i use my own code, there is nothing happen. "command to execute" : "E:\WindowsApplication1\bin\WindowsApplication1.exe @@SENDER@@ @@SMS@@" by the way, what is the problem? is my code? please help me!! are there another code? here is my vb.net code : =========== function getcommandline() Dim separators As String = " " Dim commands As String = Microsoft.VisualBasic.Command() If commands = "" Then commands = " " End If Dim args() As String = commands.Split(separators.ToCharArray) Dim param1 As String = args(0) Dim param2 As String = args(1) Label1.Text = param1 Label2.Text = param2 Return args end function ==================== Here is the SMSDEBUG ================== OK 10:06:24:421 [5] ThreadProcessModem: AT+CPMS=? 10:06:24:593 [5] ThreadProcessModem: +CPMS: ("ME","SM"),("ME","SM"),("ME","SM") OK 10:06:24:750 [5] ThreadProcessModem: Modem initialization complete: Sony Ericsson W550 USB WMC Data Modem 10:07:05:843 [5] ModemReceiveMessages: +CMGL: 10,0,,26 059126120000040C9126128638441100006011809065508007D3252828252601 OK 10:07:05:843 [5] ModemReceiveMessages: Decoding received message index 10 from message storage ME 10:07:05:843 [5] ModemReceiveMessages: 059126120000040C9126128638441100006011809065508007D3252828252601 10:07:05:843 [5] ModemReceiveMessages: SMSC address len = 5 10:07:05:843 [5] ModemReceiveMessages: SMSC Address = +62210000 10:07:05:843 [5] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 10:07:05:843 [5] ModemReceiveMessages: Sender address len = 12 10:07:05:843 [5] ModemReceiveMessages: Sender Address = +622168834411 10:07:05:843 [5] ModemReceiveMessages: PID = 00 10:07:05:843 [5] ModemReceiveMessages: DCS = 00 10:07:05:859 [5] ModemReceiveMessages: Anticipated user data length = 7 10:07:05:859 [5] ModemReceiveMessages: Message = SK TEST 10:07:05:859 [5] ModemReceiveMessages: AT+CMGD=10 10:07:06:078 [5] ModemReceiveMessages: OK 10:07:06:703 [2] ThreadProcessInboundSMS: Processing 455149D9.in... 10:07:06:703 [2] GetProgramToExecute: E:\WindowsApplication1\bin\WindowsApplication1.exe @@SENDER@@ @@SMS@@ 10:07:06:703 [2] GetProgramToExecute: Converting character set for received SMS message to utf-8 10:07:06:703 [2] smsData Before: SK TEST 10:07:06:718 [2] UTF8ToLocalString: Error 87 from WideCharToMultiByte 10:07:06:718 [2] UTF8ToLocalString: Error 87 from WideCharToMultiByte 10:07:06:718 [2] smsData After: SK TEST 10:07:06:718 [2] GetProgramToExecute: E:\WindowsApplication1\bin\WindowsApplication1.exe +622168834411 TEST 10:07:06:718 [2] ThreadProcessInboundSMS: Executing E:\WindowsApplication1\bin\WindowsApplication1.exe +622168834411 TEST thanks.. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6811 Registered: 10-2002 |
Hi, Does the log end there? What happens if you have sent more than 1 message in to the application? Does it take 5 minutes before the second message is processed in the SMSDEBUG.LOG? If so, then this indicates that your application is not exiting properly. What happens if you run this from the command prompt: E:\WindowsApplication1\bin\WindowsApplication1.exe +622168834411 TEST Does it run and then exit back to the command prompt? If it does not, make changes so that it will. If the command line test works ok, try changing the NowSMS 2-way command to be this instead: c:\winnt\system32\cmd.exe /c E:\WindowsApplication1\bin\WindowsApplication1.exe @@SENDER@@ @@SMS@@ This loads the application under the Windows command processor. Some applications could have problems parsing command line parameters unless they are running under the command processor, and this might make a difference. If you're still stuck ... we had a recent issue in another thread where someone was experiencing similar problems, and the problem seemed to be related to their virus scanner. So you may want to try temporarily disabling your virus scanner to see if this makes a difference. -bn | |||
Khusnul Fajri Rhomadon New member Username: Khusnul Post Number: 1 Registered: 11-2006 |
when I sent SMS to destination number as customer service for get any information from service provider, I GET REPLY SMS to continous(more than one) but i send my sms one only.how about way get a reply sms no more than one reply? please help me... | |||
Khusnul Fajri Rhomadon New member Username: Khusnul Post Number: 2 Registered: 11-2006 |
hi i'm trying 2-way sms. i use asp vbscript. i've problem with receive sms. i've success test with "command to execute" is "http::\localhost\2way\2way.asp?phonenumber=@@SENDER@@&text=@@FULLSMS@@”. and user can receive back the messages. but user get reply sms more than one. by the way, what is the problem? is my code? please help me, this is my code <% set conn = server.createobject("adodb.connection") Set Rs = Server.CreateObject("ADODB.Recordset") Conn.Open dsn1 SQL = "select * from SMS where msg='" & text & "' And id = id2 order by id desc" rs.Open SQL, conn, 3, 3 Response.ContentType = "text/plain" If Request.QueryString("phonenumber") = "" Then Response.Write ("ERROR : 'phonenumber' parameter missing!") Else If (Request.QueryString("text") = "") Then Response.Write ("ERROR : 'text' parameter missing!") Else Response.Write (rs("msganswer")) End If End If rs.close conn.close set rs=nothing set conn=nothing %> | |||
Malcolm - Now Support New member Username: Malcolm Post Number: 50 Registered: 12-2006 |
Try moving Response.ContentType = "text/plain" to be the first line of the script (after the opening <%). Then verify that your script works like you expect by manually issuing requests from within your web browser. For example, http://localhost/2way/2way.asp?phonenumber=1234&text=this+is+a+test Do you get the response that you expect when you issue these test requests directly from the browser? Assuming that you get the expected response from the browser, then let's go back to troubleshooting the script when it is called by NowSMS. I would suggest enabling the SMSDEBUG.LOG, which can be done by checking the checkbox on the "Serial #" page of the NowSMS configuration dialog. Send a message in, and then post the SMSDEBUG.LOG that shows the message being processed. -- Malcolm Now Wireless Support |