Re: [hylafax-users] Can't receive from one fax machine

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Michael Crider wrote:
> We have been running hylafax with a Multitech MT5634ZPX-PCI for three 
> years (currently at version 4.4.2 on CentOS 5) with almost no problem 
> (other than unrelated hardware problems). It was recently brought to 
> my attention that one company we deal with has never been able to 
> successfully send a fax to us. They told us they have a Samsung SCX 
> 4521F. It will typically call ten times before it gives up. I am 
> including a complete log file from one call below. Does anyone have 
> any suggestions on whether this can be resolved without changing 
> hardware?
>
> May 06 16:53:36.69: [ 2519]: RECV training at v.17 14400 bit/s
> May 06 16:53:36.69: [ 2519]: <-- [11:AT+FRM=145\r]
> May 06 16:53:36.80: [ 2519]: --> [8:+FCERROR]
> May 06 16:53:36.80: [ 2519]: <-- [11:AT+FRM=145\r]
> May 06 16:53:36.91: [ 2519]: --> [8:+FCERROR]
> May 06 16:53:36.91: [ 2519]: <-- [9:AT+FRH=3\r]
> May 06 16:53:37.38: [ 2519]: --> [7:CONNECT]
> May 06 16:53:38.45: [ 2519]: --> [10:NO CARRIER] 

It appears that the sender hangs on to the V.21 carrier for some time 
after the DCS signal ends... and then the Agere bug with V.21 HDLC 
detection kicks in there as well.

The main culprit here is that the modem is indicating "OK" after the DCS 
signal ends but before the V.21 carrier drops.  It makes it complicated 
for the subsequent AT+FRM command.

Three things to try:

1) make sure that you're running the latest firmware on that MT5634ZPX-PCI.

2) set Class1RMPersistence to 3 in your modem config file (etc/config.ttyS4)

3) try with HylaFAX+ 5.2.4

Do it in that order... let me know how it goes.

Thanks,

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*