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] failure to train remote modem at 2400 bps



cvb@xxxxxxxxxxx wrote:
Hi - now that I got my USR 56k USB Modem to talk to faxgetty, it seems
I can't send faxes because I always get the error message mentioned in
the subject.
What's happening on the receive-side? Do you have any logs from the
receiver?

Yes, since the receiving side is my system as well - though with a different software - I do have logs; not as excessive as hylafax's logs, but hopefully helpful:

20 Dec 10:24:07.27 BINK FAX AT+FDR [faxmodem_receive_page]
20 Dec 10:24:07.27 BINK FAX Waiting for CONNECT [faxmodem_receive_page]
20 Dec 10:24:07.51 BINK FAX +FCS:0,5,0,2,0,0,0,0
20 Dec 10:24:07.51 BINK Response from peer: +FCS:0,5,0,2,0,0,0,0

This is where the receiving modem is supposed to have sent CFR. We don't know for sure if it sent it because the sending modem didn't get it, but we can assume that it did because it appears that you are using this for receiving other faxes.


20 Dec 10:24:17.16 BINK FAX +FPS:1,15,0,0,0
20 Dec 10:24:17.16 BINK FAX [get_modem_result_code]
20 Dec 10:24:21.26 BINK FAX [get_modem_result_code]
20 Dec 10:24:21.95 BINK FAX +FTI:"XXX"
20 Dec 10:24:21.95 BINK FAX [get_modem_result_code]
20 Dec 10:24:22.19 BINK FAX +FCS:0,3,0,2,0,0,0,0
20 Dec 10:24:22.19 BINK FAX [get_modem_result_code]

I'm probably the only one here who will find this amusing, but this is funny that the receiving modem thought that the sender's retraining was Phase C image data consisting of 15 lines and wants to confirm it as a page receipt. :-)


This is why Class 1 is so much better to use. ;-)

Okay, so here's what the problem likely is. This is from your send-side log that you sent before:

Dez 20 23:17:50.23: [18162]: <-- [9:AT+FRS=1\r]
Dez 20 23:17:51.32: [18162]: --> [2:OK]
Dez 20 23:17:51.32: [18162]: <-- [9:AT+FRH=3\r]
Dez 20 23:17:54.42: [18162]: --> [0:]
Dez 20 23:17:54.42: [18162]: MODEM <Empty line>
Dez 20 23:17:54.42: [18162]: MODEM TIMEOUT: waiting for v.21 carrier
Dez 20 23:17:54.42: [18162]: <-- data [1]
Dez 20 23:17:54.42: [18162]: --> [2:]
Dez 20 23:17:54.42: [18162]: --> [2:OK]

It's obvious now what is the problem. That AT+FRS=1 is bad form. It shouldn't be there. It's causing the sender to miss the receiver's CFR signal. Please remove Class1ResponseWaitCmd from your modem config file.


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