| Problem Querying Modem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Jason Delport Unregistered guest |
Hi, We have been using the NOWSMS gateway for well over a year and have never had any problems but recently we have started getting an unsual issue. When the NOWSMS service is turned OFF I am successfully able to test the modem (Wavecom) but as soon as I start running NOWSMS as a service, connecting to the modem fails. ANy ideas? I am using version v5.50 build (20040503) Error is: 80000018 lineGetID LOG BELOW 11:02:33:606 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 11:02:35:619 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem 11:02:35:619 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK 11:02:35:619 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ... 11:02:36:009 [2] ThreadProcessModem: AT+CPMS? 11:02:36:080 [2] ThreadProcessModem: +CPMS: "SM",1,10,"SM",1,10 OK 11:02:36:080 [2] ThreadProcessModem: AT+CNMI? 11:02:36:140 [2] ThreadProcessModem: +CNMI: 0,1,0,0,0 OK 11:02:36:140 [2] ThreadProcessModem: AT+CPMS=? 11:02:36:210 [2] ThreadProcessModem: +CPMS: (("SM","BM","SR"),("SM")) OK 11:02:36:210 [2] ThreadProcessModem: Modem initialization complete: Standard 19200 bps Modem 11:09:18:338 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem 11:09:18:338 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem 11:09:25:208 [0] main: Shutdown: Closing log files Thanks. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3279 Registered: 10-2002 |
Hi Jason, Based upon the log file, everything looks ok. The service is not having a problem allocating the modem. The "80000018 lineGetID" error can happen for a variety of reasons. However, one of the most common reasons is because another application already has the modem open. Which leads me to the following theory ... When you test the modem from the configuration program, it has to signal the service to release the modem. Are you perhaps accessing the configuration program via Terminal Services or Remote Desktop? I believe this signaling does not work in that environment. As a result, the service never releases the modem. (If it did, I'd expect to see a note in the debug log that says "Releasing modem for other activities".) In that type of environment, you would need to stop the service before you could test the modem. -bn | |||
| Jason Delport Unregistered guest |
Bryce, Thanks for the help. It was just Remote Desktop that was causing the problems. Thanks, Jason Delport | |||
