Re: [hylafax-users] Courier I-Modem ISDN/V.34 Problem

[Christoph Scheeder <christoph.scheeder@scheeder.de>]

Hi again,
in this situation i would try two things in this order:
1.) look if i can find a firmware-update for the modem, often 
modems with old firmware get delivered. 
If this does not fix the problem I would guess it is damaged. 
2.) go to your dealer and let him replace the modem.
Either by transport or it is one of those devices dieing after 
a very short period of time due to bad components.
This happens more often than many people imagine.
Christoph

Cédric Bole-Richard schrieb:
> 
> Hi,
> 
> Before, thank for your help.
> 
> I have tried different baud-rate (19200,38400,56600) and the problem
> persist.
> In minicom, i type the same sequence that faxgetty, and the result is OK !
> And I can dial, all is OK !
> I would surprise if it is a Hardware problem ! My modem is new, i have
> received it Wednesday.
> It's very strange. Maybe i have a fault in my configuration ? I think that
> it'll be indicate in /var/log/messages or /var/log/syslog.
> Someone would have the same configuration that me ? Perhaps the same
> problem.
> But i have looked the Mailing List archive, but i haven't find the solution.
> At http://www.hylafax.org/archive/1999-08/msg00278.html, it has the same
> problem and i tested the solution (I have added E0 in the ATM0 sequence :
> ATM0E0 ATM1 ATM1 ATM1 ATM1), but, ...
> I have tested with an other modem (Olitec SmartMemory), all is OK.
> 
> ----- Original Message -----
> From: Christoph Scheeder <christoph.scheeder@scheeder.de>
> To: <hylafax-users@hylafax.org>
> Sent: Tuesday, Oct 24, 2000 10:11 AM
> Subject: Re: [hylafax-users] Courier I-Modem ISDN/V.34 Problem
> 
> Hi,
> That looks strange to me. Is it possible you have a hardwareproblem,
> perhaps bad V24-cabels, bad powerconnectiin for the modem, bad port?
> have you tried another baud-rate for communication?
> Christoph
> 
> Cédric Bole-Richard schrieb:
> >
> > In minicom, if i type ATE0V1Q0X4S0=0H0, the answer is OK
> >
> > I see sometimes the sequence is ok but after some minutes, i have the same
> > problem. (Faxgetty respawn and the problem come back).
> > I have tested to remove one command in the sequence, but always the
> problem.
> >
> > ----- Original Message -----
> > From: Christoph Scheeder <christoph.scheeder@scheeder.de>
> > To: hylafax <hylafax-users@hylafax.org>
> > Sent: Tuesday, Oct 24, 2000 9:03 AM
> > Subject: Re: [hylafax-users] Courier I-Modem ISDN/V.34 Problem
> >
> > Hi,
> > first, to clarify something, under newer versions of linux kernels
> > the old devices /dev/cuax shouldn't be used anymore, because they
> > lead to problems with locking the device correct, imagine
> > you have a ppp-connection set to use dev/ttyS0 and hylafax set to
> > use /dev/cua0. now if you are using the ppp-connection and hylafax
> > trys to send a fax your ppp-connection will be killed, cause hylafax
> > doesn't realize the modem is used by another process.
> >
> > but now to your problems.
> > what do you get as response in minicom if you type
> >
> > ATE0V1Q0X4S0=0H0
> >
> > (that is the string hylafax sends to your modem and does not get
> > a modemresponse for)
> >
> > if your modem times out on that string, try removing one command after
> > the other until you find the incorrect one.
> > hope it helps
> > Christoph
> >


____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null