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

["Manuel H." <thrashthrashthrash@xxxxxx>]

Hi Andrew!


Today i upgraded to Hylafax 4.2.4 and i still have the same problems. Is
the Agere Venus a internal or extern modem? Is it difficult to install,
or just plug in and it works, so that i just have to run faxaddmodem?
I think I have to try another modem :-/

I'll come back with other questions, when i have another modem :D



Am Donnerstag, den 05.01.2006, 16:10 +0000 schrieb andrew rinaldi:
> Hi Manuel.
> 
> It 'could' be the problem... but then so could the Fritz card and/or the
> Fritz fax software and/or 4.2.1, etc. etc.
> 
> I would recommend that you try another modem based on the Agere Venus
> chipset because this is simple.  This will also give you V.34 Super-G3 fax
> and arguably the most stable hardware modem available.  
> 
> Regards
> 
> ANDREW RINALDI
> Mainpine Support
> USA +1 718 701 2422 | Asia/Europe +44 1225 436137 
> andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com
> -----Original Message-----
> From: hylafax-users-bounce@xxxxxxxxxxx
> [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of Manuel H.
> Sent: 05 January 2006 16:01
> To: hylafax-users@xxxxxxxxxxx
> Subject: Re: [hylafax-users] CL-MD56XX: Some faxe could be reveived, somenot
> 
> I found something about my CirrusLogic Modem: Could this be the problem, so
> i don't get faxes from some machines(mainly pc's with fritzfax isdn cards)?
> Handshake/phasing problem? Could this affect the "NO CARRIER"
> error?
> 
> http://help.sitestar.net/modemissues/knownproblem.htm
> Cirrus Logic Handshake/phasing problem. Similar to the AOpens. Will not
> connect. (chipset CL-MD56xx typically) Needs latest firmware 6.04 or later.
> If worse comes to worse, I've been able to get the Cirrus Logics to connect
> with this init string
> 
> Thank you all so much, best wishes
> m.
> 
> Am Donnerstag, den 05.01.2006, 15:54 +0100 schrieb Manuel H.:
> > Hi Andrew.
> > 
> > Thank you for your adivse! I 'll search for a different modem. I think 
> > i have some left at my work ;)
> > 
> > But i found something out, belonging to my problem:
> > It seems that i could receive faxes from faxmachines, but i have 
> > problems with the faxes which are sent from computers with ISDN Fritz 
> > PCI Cards and their FritzFax Software. Are their known problems?
> > My distributor is gentoo linux and as soon as hylafax 4.2.4 is in 
> > portage i 'll upgrade.
> > 
> > Thank you, best wishes.
> > m.
> > 
> > 
> > 
> > Am Donnerstag, den 05.01.2006, 14:35 +0000 schrieb andrew rinaldi:
> > > Hi Manuel.
> > > 
> > > If you have a different modem then please try it and report the results.
> > > 
> > > You should also consider an upgrade to 4.2.4 because of the ongoing 
> > > work in the Class 1 driver (and recent security fixes).
> > > 
> > > Regards
> > > 
> > > ANDREW RINALDI
> > > Mainpine Support
> > > USA +1 718 701 2422 | Asia/Europe +44 1225 436137 
> > > andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com
> > > 
> > > -----Original Message-----
> > > From: hylafax-users-bounce@xxxxxxxxxxx 
> > > [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of Manuel H.
> > > Sent: 05 January 2006 14:04
> > > To: Lee Howard
> > > Cc: hylafax-users@xxxxxxxxxxx
> > > 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*
> > 
> 
> 
> ____________________ 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*