Re: [hylafax-users] Single Canon 2060 fax machine COMREC DCN-ing

[Marcin Giedz <giedz@xxxxxxxx>]

Lee Howard wrote:
> Alternative Diasporas wrote:
Canon 2060 you said...haaa ...I had the same problem, however in my case 
we send usually 200+ per day and before that I  had Class2.1 set it 
config files. The mode is Mainpine QUATRO+. After I switched to Class 1 
the above problem disappeared completely. I now this is not solution for 
your issue, but I wanted to point that fact on the list.

Anyway, I will check my logs to find out if I had the same situation 
like to what Lee says.

Regards,
Marcin
> > Feb 20 19:02:21.87: [ 2170]: SEND send PPS (partial page signal)
> > Feb 20 19:02:21.87: [ 2170]: SEND send EOP (no more pages or documents)
> > Feb 20 19:02:21.87: [ 2170]: <-- [9:AT+FRH=3\r]
> > Feb 20 19:02:22.35: [ 2170]: --> [7:CONNECT]
> > Feb 20 19:02:23.21: [ 2170]: --> [2:OK]
> > Feb 20 19:02:23.21: [ 2170]: SEND recv DCN (disconnect)
> > Feb 20 19:02:23.21: [ 2170]: DELAY 70 ms
> > Feb 20 19:02:23.28: [ 2170]: COMREC invalid response received to PPS.
> >  
>
> Most Phase D COMREC-DCN situations occur when...
>
> 1) the Phase C image data being sent does not agree with what the 
> receiver understood from our DCS signal
>
> 2) the receiver is unwilling to tolerate some other kind of error in 
> the Phase C image data
>
> 3) the receiver is unwilling to tolerate the modulation that the 
> modem's DSP is using
>
> You're using 4.2.5.  Before you go too far I would recommend 
> "upgrading" (and I quote that word as some here will undoubtedly 
> challenge me on that usage) to HylaFAX+ 5.0.4 
> (http://hylafax.sourceforge.net).  Or at least testing with another 
> machine using that same modem and that version of HylaFAX+.  If you 
> can't do that then please let me know if I can send a few test faxes 
> to that number.  (You'll need to privately give me the fax number.)
>
> If I can reproduce the error here with my modems - or if you can 
> reproduce the error there with 5.0.4 - then it's much more likely a 
> bona fide bug on HylaFAX's part.
>
> It's possible that the problem is really with the modem - albeit a 
> slight possibility only.  You may want to try some other Class 1 
> modem.  USR modems are always suspect in my book.
>
> 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*