| Stabilize GPRS modem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| lars mservice |
I have ben running nowsms 5.0 beta since you released it. I am running it with at Siemens MC35-T. I talked to Siemens and they say that in windows i install a default 19.200 modem. I have done that and it works perfectly, almost... After about 20 to 24 hours it begins to hang in nowsms. If i open nowsms and press test on the smsc page, nowsms returns an error saying something like "LineOpen error 0811xx222" Looks like it hangs after some time, but i am not sure. Does anyone have ideas to optimize and keep the modem-connection stabile? Comport spedd etc. ? Here is a little clip of my smsdebug.log: 14:33:25:084 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem 14:33:25:084 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK 14:33:25:084 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ... 14:33:25:164 [2] OpenDevice: Unable to initialize modem: Error 80000048 from lineOpen 14:33:25:174 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem 14:33:25:174 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem 14:33:45:183 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem 14:33:45:183 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK 14:33:45:183 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ... 14:33:45:213 [2] OpenDevice: Unable to initialize modem: Error 80000048 from lineOpen 14:33:45:213 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem 14:33:45:213 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem 14:34:25:391 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem 14:34:25:391 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK 14:34:25:391 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ... 14:34:25:411 [2] OpenDevice: Unable to initialize modem: Error 80000048 from lineOpen 14:34:25:411 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem 14:34:25:411 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem 14:37:25:990 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem 14:37:25:990 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK 14:37:25:990 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ... 14:37:26:000 [2] OpenDevice: Unable to initialize modem: Error 80000048 from lineOpen 14:37:26:000 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem 14:37:26:000 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem 14:41:02:732 [0] HandlerRoutine: Initiating shutdown... 14:41:04:475 [0] main: Shutdown: Closing log files | |||
| lars |
here is the popup form nowsms when pressing test on the smsc page: unable to initialize modem: Error 80000048 from lineOpen | |||
| Bryce Norwood - NowSMS Support |
Hi Lars, Sorry that I have had to be unexpectedly away from the forum for so long. When this occurs, which of the following actions can recover the error: 1.) Stopping and restarting the NowSMS service. 2.) Rebooting the PC. 3.) Restarting the modem. If the problem can be resolved by either #1 or #2 (that is, without restarting the modem itself), then we might have a hope of figuring out a way to handle this via software. We've had problems in past releases, where each time we would re-init a modem, if the modem was using a TAPI driver (instead of a direct to COM port driver), we had a bug that would leak a handle, and eventually the TAPI driver would run out of handles and start returning unusual error codes. Having to use RAS for GPRS in v5.0 means a lot of releasing and re-init of the modem. So we found this bug pretty quickly. But maybe we didn't find it completely. It would be helpful if you could monitor with Task Manager the "Handle Count" for the application. When this error occurs, has the "Handle Count" risen significantly? Another question. When the problem occurs, and you go to the "test" option on the SMSC page ... what if you stop the service ... and try to add and test the COM port entry directly. What does that return? -bn | |||
