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] patton 2977 : COMREC received DCN



I would definitely consider hylafax+ as it has new  releases more frequently but we need sometime to test and change.

The current situation is that the sender transmits 20 pages. The fax session is aborted at 10th page. The sender retransmits the fax from 11th page. The 20-page fax is separated as 2 or more fax sessions. The recipient has to merge the 2 or 3 fax files together.

Could we do something to reject the whole fax so that the sender could retransmit all pages?

Pls kindly advise.

Lee Howard <faxguy@xxxxxxxxxxxxxxxx> wrote:
ACL wrote:
> Patton 2977 is setup to receive fax from many different fax machines
> without problem.
>
> Occasionally, faxes received are aborted when sending from panafax uf-590.
>
> Mar 04 15:15:27.13: [21785]: RECV received RCP frame
> Mar 04 15:15:27.13: [21785]: --> HDLC<5:FF C0 61 96 D3>
> Mar 04 15:15:27.13: [21785]: MODEM input buffering disabled
> Mar 04 15:15:28.63: [21785]: --> [18:]
> Mar 04 15:15:28.63: [21785]: --> [10:NO CARRIER]
> Mar 04 15:15:28.63: [21785]: <-- [9:AT+FRH=3\r]
> Mar 04 15:15:31.74: [21785]: --> [7:CONNECT]
> Mar 04 15:15:32.88: [21785]: --> HDLC<3:FF FF FF>
> Mar 04 15:15:32.88: [21785]: --> [5:ERROR]
> Mar 04 15:15:32.88: [21785]: MODEM Command error
> Mar 04 15:15:32.88: [21785]: FCS error
> Mar 04 15:15:32.88: [21785]: <-- [10:AT+FRS=21\r]
> Mar 04 15:15:33.17: [21785]: --> [2:OK]
> Mar 04 15:15:33.17: [21785]: <-- [9:AT+FTH=3\r]
> Mar 04 15:15:34.36: [21785]: --> [7:CONNECT]
> Mar 04 15:15:34.36: [21785]: <-- HDLC<3:FF C8 58>
> Mar 04 15:15:34.36: [21785]: <-- data [3]
> Mar 04 15:15:34.36: [21785]: <-- data [2]
> Mar 04 15:15:35.16: [21785]: --> [2:OK]
> Mar 04 15:15:35.17: [21785]: RECV send CRP (command repeat)
> Mar 04 15:15:35.17: [21785]: <-- [9:AT+FRH=3\r]
> Mar 04 15:15:35.36: [21785]: --> [7:CONNECT]
> Mar 04 15:15:35.40: [21785]: --> [2:10 03]
> Mar 04 15:15:35.40: [21785]: --> [10:NO CARRIER]
> Mar 04 15:15:35.40: [21785]: MODEM No carrier
> Mar 04 15:15:35.40: [21785]: <-- [10:AT+FRS=21\r]
> Mar 04 15:15:37.12: [21785]: --> [2:OK]
> Mar 04 15:15:37.12: [21785]: <-- [9:AT+FTH=3\r]
> Mar 04 15:15:38.33: [21785]: --> [7:CONNECT]
> Mar 04 15:15:38.33: [21785]: <-- HDLC<3:FF C8 58>
> Mar 04 15:15:38.33: [21785]: <-- data [3]
> Mar 04 15:15:38.33: [21785]: <-- data [2]
> Mar 04 15:15:39.11: [21785]: --> [2:OK]
> Mar 04 15:15:39.11: [21785]: RECV send CRP (command repeat)
> Mar 04 15:15:39.11: [21785]: <-- [9:AT+FRH=3\r]
> Mar 04 15:15:39.94: [21785]: --> [7:CONNECT]
> Mar 04 15:15:40.99: [21785]: --> HDLC<5:FF C8 DF 59 6F>
> Mar 04 15:15:41.01: [21785]: --> [2:OK]
> Mar 04 15:15:41.01: [21785]: RECV recv DCN (disconnect)

I am not sure that anything can be done here. The sender does seem to
consistently do some weird things (like send the FF FF FF FF FF frames).
The difference between the successful session and the failed session is
that the failed session did not properly "hear" PPS after the first CRP
signal.

HylaFAX+ 5.2.2 behavior here will vary slightly. I would advise you to
try HylaFAX+ 5.2.2 to see if it improves things at all for you. If not,
then let me see those logs.

Thanks,

Lee.


Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.


Project hosted by iFAX Solutions