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] hylafax-4.4.4-1rhel3 and US Robotics 56 EXT faxmodem model 5631 recieve FCS error
Ok. I understand your points, but lets go ahead. I assure you that I have not any other device on same line with fax. Today in the morning I borrow fax machine from other office and put it on same PBX on another extension and last log which I sent to you in 8:19 I get in this configuration. So, no other fax on same line, no critical delay ( because only office PBX between faxes ), modem documented as up to class2 fax. To support of theory that this not line related problem I already sent to you log where modem was in class2 mode and had successful connection with fax but on any reason could not finish image file. Please see it again:
Session log follows:
Feb 25 19:52:33.94: [16976]: SESSION BEGIN 000000051 380444955324
Feb 25 19:52:33.94: [16976]: HylaFAX (tm) Version 4.4.4
Feb 25 19:52:33.94: [16976]: <-- [4:ATA\r]
Feb 25 19:52:50.58: [16976]: --> [5:+FCON]
Feb 25 19:52:50.58: [16976]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyACM0'
Feb 25 19:52:50.58: [16976]: RECV FAX: begin
Feb 25 19:52:50.91: [16976]: --> [28:+FTSI:" 80444955320"]
Feb 25 19:52:50.91: [16976]: REMOTE TSI "80444955320"
Feb 25 19:52:50.91: [16976]: --> [8:+FDCS:0,]
Feb 25 19:52:50.91: [16976]: MODEM protocol botch, can not parse "0,"
Feb 25 19:52:50.91: [16976]: REMOTE HANGUP: COMREC error (code 72)
Feb 25 19:52:50.92: [16976]: --> [21:+FDCS:0,3,0,2,1,0,0,0]
Feb 25 19:52:50.92: [16976]: REMOTE wants 9600 bit/s
Feb 25 19:52:50.92: [16976]: REMOTE wants A4 page width (215 mm)
Feb 25 19:52:50.92: [16976]: REMOTE wants unlimited page length
Feb 25 19:52:50.92: [16976]: REMOTE wants 3.85 line/mm
Feb 25 19:52:50.92: [16976]: REMOTE wants 2-D MR
Feb 25 19:52:50.92: [16976]: --> [2:OK]
Feb 25 19:52:50.92: [16976]: <-- [7:AT+FDR\r]
Feb 25 19:52:54.16: [16976]: --> [5:+FCFR]
Feb 25 19:52:54.94: [16976]: --> [21:+FDCS:0,3,0,2,1,0,0,0]
Feb 25 19:52:54.94: [16976]: REMOTE wants 9600 bit/s
Feb 25 19:52:54.94: [16976]: REMOTE wants A4 page width (215 mm)
Feb 25 19:52:54.94: [16976]: REMOTE wants unlimited page length
Feb 25 19:52:54.94: [16976]: REMOTE wants 3.85 line/mm
Feb 25 19:52:54.94: [16976]: REMOTE wants 2-D MR
Feb 25 19:52:54.94: [16976]: --> [7:CONNECT]
Feb 25 19:52:54.94: [16976]: RECV: begin page
Feb 25 19:52:54.94: [16976]: RECV: send trigger 021
Feb 25 19:52:54.94: [16976]: <-- data [1]
Feb 25 19:52:54.94: [16976]: Copy quality checking performed by host
Feb 25 19:54:15.21: [16976]: <-- data [1]
Feb 25 19:54:15.21: [16976]: RECV: Missing EOL after 5 seconds
Feb 25 19:54:15.21: [16976]: REMOTE HANGUP: Missing EOL after 5 seconds (section
3.2/T.4) (code 91)
Feb 25 19:54:15.21: [16976]: RECV FAX (000000051): recvq/fax000000036.tif from
80444955320, route to <unspecified>, 0 pages in 1:25
Feb 25 19:54:15.21: [16976]: RECV FAX:
Feb 25 19:54:15.21: [16976]: <-- [6:AT+FK\r]
Feb 25 19:54:45.21: [16976]: MODEM <Timeout>
Feb 25 19:54:45.21: [16976]: RECV FAX: bin/faxrcvd "recvq/fax000000036.tif"
"ttyACM0" "000000051" ""
Feb 25 19:54:45.21: [16976]: RECV FAX: end
Feb 25 19:54:45.21: [16976]: SESSION END
Best regards,
Konstantin
26.02.09, 10:45, "Lee Howard" <faxguy@xxxxxxxxxxxxxxxx>:
> Konstantine,
> The NSF and DIS signals (you showed a receive-side log with NSF being
> received and Robert showed a receive-side log with DIS being received)
> are both signals that are only transmitted by the fax receiver.
> The only way that I can imagine a fax receiver receiving NSF or DIS
> would either be if there was a very badly delayed echo/sidetone on the
> line, or if there were another fax receiver on the same line. In my
> experience it is almost always the latter.
> Thanks,
> Lee.
> voznjuk konstantin wrote:
> > Dear Lee,
> > Sorry, but let me propose other point of view. Problem at my site and at the site of Robert Becskei appeared on different location, diferent OS, and diferent hardware and of cource cant have same strange reason like another fax on same line. I think that problem is in cammand sets for particular modem class.
> >
> > Best regards,
> > Konstantin
> >
> >
> > Robert Becskei <robert.becskei@xxxxxxxxxxxxxx>
> >
> > 25.02.09, 18:55, "Lee Howard" <faxguy@xxxxxxxxxxxxxxxx>:
> >
> >
> >> Robert Becskei wrote:
> >>
> >>> Feb 25 14:39:45.81: [ 1248]: RECV recv NSF (non-standard facilities)
> >>> Feb 25 14:39:45.81: [ 1248]: <-- [9:AT+FRH=3\r]
> >>> Feb 25 14:39:45.86: [ 1248]: --> [7:CONNECT]
> >>> Feb 25 14:39:46.21: [ 1248]: --> [2:OK]
> >>> Feb 25 14:39:46.21: [ 1248]: RECV recv DIS (identification signal)
> >>>
> >> There is another fax device answering this same call on the same line.
> >> Turn that device off.
> >> 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*
> >>
> >
> >
> ____________________ 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*
--
Яндекс.Почта. Поищите спам где-нибудь еще http://mail.yandex.ru/nospam
____________________ 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*