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] Line broken on remote fax (Gestetner-RICOH)



On 2004.08.18 01:32 Sipho Mothobi wrote:
Hi all,

A couple of months ago a raised an issue with the Gestetner fax
machine
having problem with sucessfully completing the communication with
hylafax.
I have since noticed that this is not problem solely atributed to
Gestetner's but also Rightfax and it recieves that fax but the report
states as follows :

-------------------REMOTE SESSION LOG ----------------------------
2004-08-17 17:13:16 Transmission Record

     Transfer Type:    Receive fax
     Remote CSID:      [Rand Merchant Bank i]
     Unique ID:        [SIP41223CFA602C]
     Time to Transfer: 1:12
     Sent on Channel:  0
    Inbound user ID: SIPHOMOTHOBI, Routing Code: 4031
     AOC:              [0][0][0][0]
     Result:           Line broken (no loop current)
     Brooktrout Res:   Call [0:352]; Fax [4:3]
     Pages Sent:       1 - 2


The "Line broken (no loop current)" indicates that the receiver is using digital equipment and thus knows exactly when the connection drops. Looking at the log, however, it's not clear what it's complaining about, because the receiver transmits MCF as expected following both pages.


Aug 17 17:14:18.84: [ 8693]: <-- [9:AT+FRH=3\r]
Aug 17 17:14:19.10: [ 8693]: --> [7:CONNECT]
Aug 17 17:14:20.28: [ 8693]: --> [2:OK]
Aug 17 17:14:20.28: [ 8693]: SEND recv MCF (message confirmation)
Aug 17 17:14:20.28: [ 8693]: SEND FAX (000000588): FROM null TO
########### (page 2 of 2 sent in 0:14)
Aug 17 17:14:20.28: [ 8693]: SEND FAX (000000588): FROM null TO
########### (docq/doc1716.ps;01 sent in 0:39)
Aug 17 17:14:20.28: [ 8693]: <-- [9:AT+FTH=3\r]
Aug 17 17:14:20.36: [ 8693]: --> [7:CONNECT]
Aug 17 17:14:20.36: [ 8693]: <-- data [3]
Aug 17 17:14:20.36: [ 8693]: <-- data [2]
Aug 17 17:14:21.66: [ 8693]: --> [2:OK]
Aug 17 17:14:21.66: [ 8693]: <-- [5:ATH0\r]
Aug 17 17:14:21.78: [ 8693]: --> [2:OK]
Aug 17 17:14:21.78: [ 8693]: SESSION END

However, there is a possibility, I guess, that the BrookTrout modem in the RightFax receiver didn't detect the DCN signal that HylaFAX transmitted at the end of the fax session (the HDLC signal just before ATH0), and thus it detected a disconnection.


In HylaFAX 4.2.0 there is a suggested period of silence (AT+FRS=7) between the reception of the MCF signal and the transmission of the DCN signal. This may fix your problem.

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*




Project hosted by iFAX Solutions