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] Faxes over 2 pages fail.



Mark Ratering wrote:

Jan 10 15:14:41.14: [15114]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyIAX1'


Ah, an iaxmodem. I know about this. :-)

Jan 10 15:15:29.23: [15114]: RECV received frame number 15
Jan 10 15:15:29.45: [15114]: RECV received frame number 16
Jan 10 15:15:29.45: [15114]: RECV frame FCS check failed
Jan 10 15:15:29.45: [15114]: Bad HDLC terminating flag received.


(gobbledy-gook for 0.81+ seconds... ~1024 bytes lost)

This is due to some error, disruption in the audio. Possibly not your fault. ECM should correct this, after triggering a PPR.

Jan 10 15:15:30.26: [15114]: HDLC frame not byte-oriented. Trailing byte: 0
Jan 10 15:15:30.68: [15114]: RECV received frame number 21
Jan 10 15:15:30.88: [15114]: RECV received frame number 22


Here's the PPR signal sent, and we expect to get frames 17 through 20 resent to us...

Jan 10 15:15:48.08: [15114]: RECV send PPR (partial page request)
Jan 10 15:15:48.08: [15114]: <-- [10:AT+FRM=96\r]
Jan 10 15:15:48.88: [15114]: --> [6:+FRH:3]
Jan 10 15:15:54.46: [15114]: --> [7:CONNECT]
Jan 10 15:15:54.46: [15114]: --> HDLC<9:FF C8 FD F2 80 00 F2 80 3C>
Jan 10 15:15:54.46: [15114]: --> [2:OK]
Jan 10 15:15:54.46: [15114]: RECV recv PPS (partial page signal)
Jan 10 15:15:54.46: [15114]: RECV recv MPS (more pages, same document)
Jan 10 15:15:54.46: [15114]: RECV received 80 frames of block 1 of page 2


But what happens is that after 0.80 seconds the modem claims to detect the V.21 carrier, but the HDLC frame is not received in it's entirety for 5.58 seconds more... so something seems fishy about that... especially since this same sequence repeats from here on out until the session fails.

I've included Steve Underwood on this thread. If you're unaware, he authored the spandsp library that iaxmodem uses.

This issue is probably better-suited to be handled on the iaxmodem-users mailing list, and I've added it to this thread. You should probably do hylafax-users a favor and remove it from any replies.

It appears to me that iaxmodem is mistakenly reporting a V.21 carrier at 15:15:48.88 (with the +FRH:3 message) when it should be picking up the V.29 carrier instead. The sender certainly seems to be insisting that it is doing things correctly.

So this is what I need you to do. Go to:

http://soft-switch.org/downloads/snapshots/spandsp/

and download the most recent spandsp snapshot. Install it just like you did the spandsp that came with iaxmodem. Then try again. If it still has the same problems illustrated above then please add "record" to your /etc/iaxmodem-cfg.ttyIAX1 file and try again. That will put two *.raw files in your /tmp/ directory. Send those to me and also to Steve.

I assume that this problem doesn't occur with all senders. (?) I can send many, many page fax jobs to HylaFAX receiving with iaxmodem with no problems. If it does happen with every single sender then it's possible that the problem is unique to your system.

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*




Project hosted by iFAX Solutions