3 questions | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 02, 2006 ⬆ |
◄ ► |
Author | Message | |||
Levan Khutsishvili New member Username: Spilo101 Post Number: 2 Registered: 01-2006 |
1. I got motorolla razr v3 and followed instructions as mentioned in "supported phones" post, sometimes it is ok, but sometimes I get that famoue lineget error of some sort.. what can i do? 2. even though when i test and get no error and service is running nice and smooth I can not send sms. I ws successful only the very first time I set this thing up.. but never again.. I reonfigured/reselected phone connection.. and all that.. still no luck.. please help.. 2. I also got a erricson R520m from a friend. I do not have cable to connect it to the PC yet, but I know it also supports Bluetooth.. will nowSMS work with bluetooth connection? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5496 Registered: 10-2002 |
Hi, 1.) I'd need to know the specific error. Is it "80000048 lineOpen"? This error generally means that the device is either already open by another application ... or for some other reason Windows cannot initialise the modem. I generally suggest going into Phone and Modem options in the Windows Control Panel, select Modems, Diagnostics, and then use the "Query Modem" function. Make sure that Windows isn't reporting any problems here, and if it is reporting problems, it should report a more informative error than the one that NowSMS reports. 2.) Enable the SMSDEBUG.LOG (easiest to do this on the "Serial #" page of the configuration dialog). Try again ... then post the content of the SMSDEBUG.LOG ... that will give us a pretty good indication of what you are trying, and what errors are ocurring. 3.) I used to use an R520m as a modem years ago. It was one of the phones that we used a lot for testing NowSMS 3 or 4 years ago. However, I have to say that I always used it with a cable. By the time we started testing more with bluetooth modems, we had replaced the R520m in our test lab with a T68m. I would expect the R520m to work ok with Bluetooth, as I've certainly used the T68m, T68i and numerous successor models this way with success. However, the R520m was one of the very first Bluetooth phones, so I suppose there might be some issues. Definitely worth trying though. -bn | |||
Levan Khutsishvili New member Username: Spilo101 Post Number: 3 Registered: 01-2006 |
I plug in the phone. start nowSMS. test and saies it's good. go to phones and modems, query and everything seems right. I start nowSMS service, test it and it saies everything ok. test several times, still ok. Then I try to send an sms from localhost:8080 after submitting there comes other page and after clicking the link takes me back to message sending form. Never is message sent though. I test modme again and after a while error displays: "Unable to initialize modem: Error 80000018 from LineGetID" here is the logfile: 22:56:08:328 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 22:56:10:453 [0] main: preferred sender = 6473389898,Motorola USB Modem 22:56:10:453 [0] main: 59 Days remaining in trial version 22:56:10:531 [4] ThreadProcessModem: Before ModemAllocate - Motorola USB Modem 22:56:10:531 [4] ThreadProcessModem: After ModemAllocate - Motorola USB Modem - OK 22:56:10:531 [4] ThreadProcessModem: Re-initializing modem: Motorola USB Modem ... 22:56:11:234 [4] ThreadProcessModem: AT+CPMS? 22:56:11:296 [4] ThreadProcessModem: +CPMS: "MT",11,254,"OM",3,254,"IM",8,254 OK 22:56:11:296 [4] ThreadProcessModem: AT+CNMI=,,,1 22:56:11:375 [4] ThreadProcessModem: ERROR 22:56:11:375 [4] ThreadProcessModem: AT+CNMI? 22:56:11:453 [4] ThreadProcessModem: +CNMI: 0,0,0,0,0 OK 22:56:11:453 [4] ThreadProcessModem: AT+CPMS=? 22:56:11:515 [4] ThreadProcessModem: +CPMS: ("MT","IM","OM","BM","DM"),("OM","DM"),("IM") OK 22:56:11:515 [4] ThreadProcessModem: AT+CGSMS=3 22:56:11:578 [4] ThreadProcessModem: OK 22:56:11:750 [4] ThreadProcessModem: Modem initialization complete: Motorola USB Modem 22:56:11:937 [4] ThreadProcessModem: Processing 43DF2FBD.req... 22:56:11:937 [4] ThreadProcessModem: OUT: AT+CMGS=93 22:56:12:031 [4] ThreadProcessModem: IN: > 22:56:12:031 [4] ThreadProcessModem: OUT: 0041000A81464720777500F5510605040B8423F0E70601AE02056A0045C60C0332342E34322E3237 2E3134342F5741502F74657374312E776D6C000701034365636B206F757420796F75722066697273 7420574D4C207061676521000101 22:56:28:000 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:28:000 [5] ThreadProcessConnection: Processing request / 22:56:28:187 [5] ThreadProcessConnection: Request processing complete 22:56:28:343 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:28:343 [5] ThreadProcessConnection: Processing request /TOCFrame.htm 22:56:28:375 [6] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:28:375 [6] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm 22:56:28:578 [5] ThreadProcessConnection: Request processing complete 22:56:28:578 [6] ThreadProcessConnection: Request processing complete 22:56:28:578 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:28:656 [5] ThreadProcessConnection: Processing request /background.gif 22:56:28:656 [6] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:28:656 [6] ThreadProcessConnection: Processing request /logo.gif 22:56:28:750 [5] ThreadProcessConnection: Request processing complete 22:56:28:781 [6] ThreadProcessConnection: Request processing complete 22:56:28:875 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:28:890 [5] ThreadProcessConnection: Processing request /favicon.ico 22:56:28:890 [5] ThreadProcessConnection: Request processing complete 22:56:28:984 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:28:984 [5] ThreadProcessConnection: Processing request /favicon.ico 22:56:29:000 [5] ThreadProcessConnection: Request processing complete 22:56:50:312 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 22:56:50:312 [5] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=6473389898&Text=hello+leo%2C+success%3F&I nfoCharCounter=&PID=&DCS=&Submit=Submit 22:56:50:343 [5] Debug: 1 recipient entries 22:56:50:343 [5] Debug: 6473389898 22:56:50:453 [5] ThreadProcessConnection: Request processing complete 22:58:13:218 [4] ThreadProcessModem: ERROR - Error waiting for response from modem (2) 22:58:13:218 [4] ThreadProcessModem: Error: ERROR - Error waiting for response from modem (2) 22:58:44:046 [4] ThreadProcessModem: Releasing modem for other activities 22:58:44:046 [4] ThreadProcessModem: Releasing modem for other activities 22:58:50:093 [4] ThreadProcessModem: Before ModemRelease - Motorola USB Modem 22:58:50:093 [4] ThreadProcessModem: After ModemRelease - Motorola USB Modem 22:58:56:093 [4] ThreadProcessModem: Before ModemAllocate - Motorola USB Modem 23:00:00:843 [0] main: 59 Days remaining in trial version 23:02:48:921 [4] ThreadProcessModem: After ModemAllocate - Motorola USB Modem - OK 23:02:48:921 [4] ThreadProcessModem: Re-initializing modem: Motorola USB Modem ... 23:03:07:921 [4] OpenDevice: Unable to initialize modem: Error 80000018 from lineGetID 23:03:07:921 [4] HammerNonResponsiveModem: Begin 23:03:07:921 [4] HammerNonResponsiveModem: FAILED 23:03:07:937 [4] ThreadProcessModem: Before ModemRelease - Motorola USB Modem 23:03:07:937 [4] ThreadProcessModem: After ModemRelease - Motorola USB Modem 23:03:22:921 [0] main: Shutdown: Closing log files | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5511 Registered: 10-2002 |
Hi Levan, That's interesting. Basically, it looks like everything is ok with the modem until we try to send a message. When we submit the message, the modem essentially goes off-line. We wait up to 2 minutes for a success/failure response for sending the message ... but no response comes back. We try some other tests to see if we can still talk to the modem (performed, but not shown in the logs) by sending some simple commands and checking to see if the modem responds back. Evidently the modem does not respond, so we decide that we should release the modem connection and let Windows re-initialise the modem. But then Windows can't initialise the modem either (80000018 error in the log). So, then NowSMS tries some techniques to try to wake up a non-responsive modem ("HammerNonResponsiveModem" in the logs), but it can't wake it up. I'd be curious ... at this point, if you go into Phone and Modem options in the Windows Control Panel, select Modems, Diagnostics, and then use the "Query Modem" function, what does it say? I'm also suspicious because there is virtually no time delay in the logs between the "Begin" and "FAILED" under "HammerNonResponsiveModem". This suggests to me that the USB driver for the modem is hung. My suspicion is that something is wrong with the USB cable, or with the USB driver. Essentially, I believe the USB driver for the modem is locking up ... you might want to try other USB ports, or if you're going through a USB hub try connecting direct to see if that makes a difference. Beyond that, you might want to go into Phone and Modem options in the Windows Control Panel, select Properties for the modem driver, and try lowering the "Maximum Port Rate". Maybe it would work better at a lower speed? But it really sounds like something is wrong with the USB cable or the USB software driver. It might be worth checking the Motorola web site to see if there is updated driver. Something else that might be worth trying. Edit SMSGW.INI, and under the [Modem - Motorola USB Modem] header, add ModemTextMode=Yes ... see if that makes a difference. If that works ok, it suggests that this particular device is having a problem with SMS PDU mode. -bn |