Sudden carrier drop for GPRS Wavecom fasttrack modem

[j***@gmail.com]

Hi,

I have some strange behavior with a Wavecom fasttrack M1304B GPRS
modem.

I have an open GPRS connection to my ISP (Vodafone) where a sometimes
send some data.
The modem works fine for 11 hours and after that (at exactly 22.00
hours) the modem shuts down.

All redial attempt fail with the message "Error 797:.. modem not found
or busy..."

The modem will have to work stand alone, so there is no user to click
'redial' or cycle the power.


See the modem log:

01-13-2009 21:57:54.171 - Read: Total: 7069, Per/Sec: 0, Written:
Total: 2988, Per/Sec: 0
01-13-2009 21:59:54.171 - Read: Total: 7541, Per/Sec: 3, Written:
Total: 3118, Per/Sec: 1
01-13-2009 22:01:07.812 - CD dropped--Remote modem hung up.
ModemStatus=000000b0
01-13-2009 22:01:07.812 - While processing CD event, CD is reported as
high when it should be low
01-13-2009 22:01:07.812 - Hanging up the modem.
01-13-2009 22:01:07.812 - Hardware hangup by lowering DTR.
01-13-2009 22:01:07.812 - WARNING: After lowering DTR to hangup, the
modem did not drop CD with in 10 seconds, Attempting software hangup.
01-13-2009 22:01:07.812 - Send: +++
01-13-2009 22:01:08.250 - Send: ATH<cr>
01-13-2009 22:01:13.250 - Timed out waiting for response from modem
01-13-2009 22:01:13.265 - Send: ATH<cr>
01-13-2009 22:01:13.265 - Recv: ATH<cr>
01-13-2009 22:01:13.265 - Command Echo
01-13-2009 22:01:13.265 - Recv: <cr><lf>OK<cr><lf>
01-13-2009 22:01:13.265 - Interpreted response: OK
01-13-2009 22:01:13.265 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-13-2009 22:01:13.265 - Initializing modem.
01-13-2009 22:01:13.265 - DSR is low while initializing the modem.
Verify modem is turned on.
01-13-2009 22:01:13.281 - Send: AT<cr>
01-13-2009 22:01:13.281 - Recv: AT<cr>
01-13-2009 22:01:13.281 - Command Echo
01-13-2009 22:01:13.281 - Recv: <cr><lf>OK<cr><lf>
01-13-2009 22:01:13.281 - Interpreted response: OK
01-13-2009 22:01:13.296 - Send: ATE0V1<cr>
01-13-2009 22:01:13.296 - Recv: ATE0V1<cr>
01-13-2009 22:01:13.296 - Command Echo
01-13-2009 22:01:13.296 - Recv: <cr><lf>OK<cr><lf>
01-13-2009 22:01:13.296 - Interpreted response: OK
01-13-2009 22:01:13.312 - Send: AT<cr>
01-13-2009 22:01:13.312 - Recv: <cr><lf>OK<cr><lf>
01-13-2009 22:01:13.312 - Interpreted response: OK
01-13-2009 22:01:13.312 - Sending user initialization commands.
01-13-2009 22:01:13.328 - Send: AT
+CGDCONT=1,"IP","office.vodafone.nl"<cr>
01-13-2009 22:01:13.328 - Recv: <cr><lf>OK<cr><lf>
01-13-2009 22:01:13.328 - Interpreted response: OK
01-13-2009 22:01:13.328 - Waiting for a call.
01-13-2009 22:01:13.343 - Send: ATS0=0<cr>
01-13-2009 22:01:13.343 - Recv: <cr><lf>OK<cr><lf>
01-13-2009 22:01:13.343 - Interpreted response: OK
01-13-2009 22:01:13.343 - Detected DSR drop while monitoring for
calls. Likely modem turned off.
01-13-2009 22:01:13.390 - Session Statistics:
01-13-2009 22:01:13.390 - Reads : 40 bytes
01-13-2009 22:01:13.390 - Writes: 59 bytes
ATQ0V1E0 - OK
AT+GMM - MULTIBAND 900E 1800
AT+FCLASS=? - +FCLASS: (0,1,2)
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - OK
ATI2 - OK
ATI3 - 641b09gg.Q2406B 1339080 041604 16:04
ATI4 - Q:0 V:1 S0:000 S2:043 S3:013 S4:010 S5:008
+CR:0 +CRC:0 +CMEE:0 +CBST:0,0,1
+SPEAKER:1 +ECHO:0,1 &C:1 &D:2 %C:0
+IPR:115200 +ICF:3,4 +IFC:2,2
ATI5 - Q:0 V:1 S0:000 S2:043 S3:013 S4:010 S5:008
+CR:0 +CRC:0 +CMEE:0 +CBST:0,0,1
+SPEAKER:1 +ECHO:0,1 &C:1 &D:2 %C:0
+IPR:115200 +ICF:3,4 +IFC:2,2
ATI6 - DATA RATES: AUTOBAUD,300,1200,1200/75,2400,4800,9600,14400
DATA MODES: T/NT,ASYNCHRONOUS
FAX CLASS: 1,2
ATI7 - SPEECH CODINGS: FR,EFR,HR

[John Henderson]

Post by j***@gmail.com
Hi,
I have some strange behavior with a Wavecom fasttrack M1304B
GPRS modem.
I have an open GPRS connection to my ISP (Vodafone) where a
sometimes send some data.
The modem works fine for 11 hours and after that (at exactly
22.00 hours) the modem shuts down.
All redial attempt fail with the message "Error 797:.. modem
not found or busy..."
The modem will have to work stand alone, so there is no user
to click 'redial' or cycle the power.

I'm not sure about that model, but given the regularity, my
first thought is that you're seeing "Wavecom reset" in action.

Only the French would make a piece of equipment which fails
periodically and predictably by design and by default :)

Try turning "Wavecom reset" off by putting

AT+WRST=0

into your modem initialization.

John