HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

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




Project hosted by iFAX Solutions