Re: [hylafax-users] CL-MD56XX: Some faxe could be reveived, somenot

["Ivan Petrov" <ivanp@xxxxxxxxxxxxx>]

Hi Manuel,

I'm pretty sure the problem is the modem you're using. Try with another 
modem if possible. One suggestion - avoid US Robotics (I used to have big 
respect to this company in the past - sorry but not anymore!). Rockwell or 
Lucent based modem would be your best choice.

Regards,
Ivan


----- Original Message ----- 
From: "Manuel H." <thrashthrashthrash@xxxxxx>
To: "Lee Howard" <faxguy@xxxxxxxxxxxxxxxx>
Cc: <hylafax-users@xxxxxxxxxxx>
Sent: Thursday, January 05, 2006 9:03 AM
Subject: Re: [hylafax-users] CL-MD56XX: Some faxe could be reveived, somenot


> Hello, thank you for your answer!
>
> I tried it with ATA and had the same results (some work but the most
> faxes didn not receive. You said that the modem is not detecting any
> HDLC signals from the sender? How could i check this? I don't understand
> why i get some faxes and others can't be receive? This must be a setting
> in the config.ttyS0???? Why do i get an "NO CARRIER" message in the log?
> Would be a different modem a solution, or whats your advise?
>
> Thank you, best wishes
> m.
>
>
>
>
> Am Mittwoch, den 04.01.2006, 09:53 -0800 schrieb Lee Howard:
> > Manuel H. wrote:
> >
> > >>Jan 03 13:00:22.31: [ 8402]: SESSION BEGIN 000000035 495312842085
> > >>Jan 03 13:00:22.31: [ 8402]: HylaFAX (tm) Version 4.2.1
> > >>Jan 03 13:00:22.31: [ 8402]: <-- [6:ATAX3\r]
> > >>Jan 03 13:00:27.30: [ 8402]: --> [7:CONNECT]
> > >>Jan 03 13:00:27.30: [ 8402]: ANSWER: FAX CONNECTION  DEVICE 
> > >>'/dev/ttyS0'
> > >>Jan 03 13:00:27.30: [ 8402]: RECV FAX: begin
> > >>Jan 03 13:00:27.30: [ 8402]: <-- data [32]
> > >>Jan 03 13:00:27.30: [ 8402]: <-- data [2]
> > >>Jan 03 13:00:28.67: [ 8402]: --> [7:CONNECT]
> > >>Jan 03 13:00:28.67: [ 8402]: <-- data [23]
> > >>Jan 03 13:00:28.67: [ 8402]: <-- data [2]
> > >>Jan 03 13:00:29.43: [ 8402]: --> [7:CONNECT]
> > >>Jan 03 13:00:29.43: [ 8402]: <-- data [10]
> > >>Jan 03 13:00:29.43: [ 8402]: <-- data [2]
> > >>Jan 03 13:00:29.88: [ 8402]: --> [2:OK]
> > >>Jan 03 13:00:29.88: [ 8402]: <-- [9:AT+FRH=3\r]
> > >>Jan 03 13:00:30.04: [ 8402]: --> [7:CONNECT]
> > >>Jan 03 13:00:31.54: [ 8402]: --> [10:NO CARRIER]
> > >>
> >
> > (log repeats the same thing over and over)
> >
> > Firstly, what's the ATAX3 for?  Why do you have ModemAnswerCmd set to
> > ATAX3 and not just ATA?  My modem manuals indicate that all of the ATXn
> > commands are intended for dialing (sending) and not answering
> > (receiving).  So I'd guess that the behavior they'd cause in the wrong
> > application would be unexpected.
> >
> > Anyway, the rest of the log tells us that the modem is unable to detect
> > any HDLC signalling from the sender... which surely isn't the fault of
> > the sender.  So the modem isn't doing what it's supposed to... possibly
> > because of that X3.  Possibly due to other things.
> >
> > If you have a different modem try that if removing the X3 doesn't help.
> >
> > Lee.
>
>
> ____________________ HylaFAX(tm) Users Mailing List 
> _______________________
>  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
> On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
>  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*