Modem not responding, have to reboot (icon 322)

Modem not responding, have to reboot (icon 322) SearchSearch
Author Message
Ray Pitmon
New member
Username: Ray

Post Number: 1
Registered: 12-2009
Posted on Saturday, December 05, 2009 - 09:38 pm:   

Hi,

I'm evaluating Now SMS, and it seems that it likes to stop working randomly. The only way to fix it is to physically reboot the machine. I can pull the GSM modem out, I can stop/start the Now SMS services, but it won't work until a reboot.

I enabled debug, and here's what is at the end of my log file. It looked like everything was fine until around 13:55. (I included the end of a successful transaction at around 2:43.)

02:43:03:187 [7] ThreadProcessModem: Processing 4AFF6E50.req...
02:43:03:187 [7] ThreadProcessModem: OUT: AT+CMGS=108

02:43:03:265 [7] ThreadProcessModem: IN:
>
02:43:03:265 [7] ThreadProcessModem: OUT: 0001230B816121487067F800006C41361BF43683F2EFBA1C7496BFEBF039081DB69741E272D90D92 97DB6F7B99EC0221C3F632280C72A7C76510399C07B540627A1D24CE83DA797A194F6F975DE377DB 05A2E2E92074990D07D14069B7F9CD02BDE5A039FD0D07C940F17A9A0E
02:43:05:015 [7] ThreadProcessModem: +CMGS: 60

OK

02:43:17:046 [11] WaitForSocketClose: WinSock reported ioctlsocket complete
03:00:00:015 [0] main: 41 Days remaining in trial version
04:00:00:062 [0] main: 41 Days remaining in trial version
05:00:00:062 [0] main: 41 Days remaining in trial version
06:00:00:062 [0] main: 41 Days remaining in trial version
07:00:00:078 [0] main: 41 Days remaining in trial version
08:00:00:078 [0] main: 41 Days remaining in trial version
09:00:00:125 [0] main: 41 Days remaining in trial version
10:00:00:125 [0] main: 41 Days remaining in trial version
11:00:00:125 [0] main: 41 Days remaining in trial version
12:00:00:125 [0] main: 41 Days remaining in trial version
13:00:00:125 [0] main: 41 Days remaining in trial version
13:55:40:140 [7] SendModemCommand: Error - 3E3 -
13:55:40:140 [7] SendModemCommand: CancelIo
13:55:40:140 [7] SendModemCommand: Wrote 0 bytes, expected 9 bytes
13:55:40:140 [7] SendModemCommand: AT+CPMS?

13:55:52:140 [7] SendModemCommand: Error - 3E3 -
13:55:52:140 [7] SendModemCommand: CancelIo
13:55:52:140 [7] SendModemCommand: Wrote 0 bytes, expected 7 bytes
13:55:52:140 [7] SendModemCommand: ATE0V1

13:55:52:140 [7] ThreadProcessModem: OUT: 
13:56:02:140 [7] SendModemCommand: Error - 3E3 -
13:56:02:140 [7] SendModemCommand: CancelIo
13:56:02:140 [7] SendModemCommand: Wrote 0 bytes, expected 1 bytes
13:56:02:140 [7] SendModemCommand: 
13:56:02:250 [7] ThreadProcessModem: OUT: \r
13:56:12:250 [7] SendModemCommand: Error - 3E3 -
13:56:12:250 [7] SendModemCommand: CancelIo
13:56:12:250 [7] SendModemCommand: Wrote 0 bytes, expected 1 bytes
13:56:12:250 [7] SendModemCommand:

13:56:12:250 [7] ThreadProcessModem: OUT: AT
13:56:22:250 [7] SendModemCommand: Error - 3E3 -
13:56:22:250 [7] SendModemCommand: CancelIo
13:56:22:250 [7] SendModemCommand: Wrote 0 bytes, expected 3 bytes
13:56:22:250 [7] SendModemCommand: AT

13:56:34:000 [7] SendModemCommand: Error - 3E3 -
13:56:34:000 [7] SendModemCommand: CancelIo
13:56:34:000 [7] SendModemCommand: Wrote 0 bytes, expected 7 bytes
13:56:34:000 [7] SendModemCommand: ATE0V1

13:56:34:000 [7] ThreadProcessModem: modem test failed
13:56:34:000 [7] ThreadProcessModem: OUT: AT+CFUN=1,1
13:56:44:000 [7] SendModemCommand: Error - 3E3 -
13:56:44:000 [7] SendModemCommand: CancelIo
13:56:44:000 [7] SendModemCommand: Wrote 0 bytes, expected 12 bytes
13:56:44:000 [7] SendModemCommand: AT+CFUN=1,1

13:56:48:000 [7] ThreadProcessModem: AT+CNMI=2,0
13:56:58:000 [7] SendModemCommand: Error - 3E3 -
13:56:58:000 [7] SendModemCommand: CancelIo
13:56:58:000 [7] SendModemCommand: Wrote 0 bytes, expected 12 bytes
13:56:58:000 [7] SendModemCommand: AT+CNMI=2,0

14:00:00:234 [0] main: 41 Days remaining in trial version
15:00:00:281 [0] main: 41 Days remaining in trial version
16:00:00:281 [0] main: 41 Days remaining in trial version
17:00:00:281 [0] main: 41 Days remaining in trial version
18:00:00:281 [0] main: 41 Days remaining in trial version
19:00:00:281 [0] main: 41 Days remaining in trial version
20:00:00:281 [0] main: 41 Days remaining in trial version
21:00:00:281 [0] main: 41 Days remaining in trial version
22:00:00:281 [0] main: 41 Days remaining in trial version
23:00:00:281 [0] main: 41 Days remaining in trial version

I'm using an Option Icon 322 on AT&T.

Any ideas?
Thanks,

-Ray
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1501
Registered: 08-2008
Posted on Monday, December 07, 2009 - 09:17 pm:   

Hi Ray,

Unfortunately it appears that the modem driver is crashing.

What's odd is that we have several Option ICON 322 modems in the office. I use them all the time for testing in different machines, and I've never had a problem with one.

Did you download the modem drivers from http://support.option.com instead of using the the carrier branded drivers that are on the flash drive associated with the modem? If you didn't, I'd uninstall the carrier branded software and install the drivers from support.option.com.

Also, try a different USB port to see if that makes a difference.

Your debug log also seems a little weird in that NowSMS seems to stop trying to talk to the modem. What version of NowSMS is it?

We did recently add a "last resort" option to reboot if a modem is non-responsive (it is not enabled by default, it is enabled by a checkbox in the modem properties under the SMSC list in NowSMS). However, this reboot does not get triggered if the modem driver hangs completely ... which looks like might be the case on your system.

Here's what I'd suggest:

1.) Try the modem drivers from the Option web site.

2.) Try a different USB port.

3.) Try editing SMSGW.INI, and under the [SMSGW] section header, add ModemMaxBytesPerSend=1

#3 is somewhat of a longshot. Without actually having an active configuration where the modem driver is crashing like this, there's no way for us to simulate it.

If the version of NowSMS you are using does not have the "Reboot System if modem is not accessible" option, you can also try the update at http://www.nowsms.com/download/nowsmsupdate.zip, and apply that setting. It's not an ideal solution, but when this type of problem occurs, unless a way can be found to prevent the problem, it's the only recourse.

--
Des
NowSMS Support