Re: receiving problems
Lee Howard <[email protected]> Thu, 16 Feb 2017 11:52:31 -0800
| Newsgroups | gmane.comp.telephony.fax.hylafax.user |
|---|---|
| Message-ID | <[email protected]> |
On 02/14/2017 01:55 AM, Piviul wrote: > Hi all, I have some problem receiving faxes. These are the logs from > the same sender that tried to send the fax 4 times: > > # cat /var/spool/hylafax/log/c000000010 > Feb 13 15:01:20.69: [ 711]: SESSION BEGIN 000000010 xxxx > Feb 13 15:01:20.69: [ 711]: HylaFAX (tm) Version 6.0.6 > Feb 13 15:01:20.69: [ 711]: DynamicConfig: bin/dynconf.php "/dev/ttyS0" > Feb 13 15:01:21.03: [ 711]: <-- [4:ATA\r] > Feb 13 15:01:21.16: [ 711]: --> [10:NO CARRIER] What kind of modem is this? ITU T.31 7.1.1 essentially mandates that the only response to the ATA command can be CONNECT once the modem has initiated V.21 HDLC signaling. The "NO CARRIER" indication is either an error by the modem or the modem's indication that it knows the call cannot proceed (like a disconnection). However, normally an analog modem is not going to be aware of any such events. > # cat /var/spool/hylafax/log/c000000011 > Feb 13 15:02:52.47: [ 711]: SESSION BEGIN 000000011 xxxx > Feb 13 15:02:52.47: [ 711]: HylaFAX (tm) Version 6.0.6 > Feb 13 15:02:52.47: [ 711]: DynamicConfig: bin/dynconf.php "/dev/ttyS0" > Feb 13 15:02:52.69: [ 711]: <-- [4:ATA\r] > Feb 13 15:03:07.07: [ 711]: --> [7:CONNECT] > Feb 13 15:03:07.07: [ 711]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS0' > Feb 13 15:03:07.07: [ 711]: RECV FAX: begin > Feb 13 15:03:07.07: [ 711]: <-- data [32] > Feb 13 15:03:07.07: [ 711]: <-- data [2] > Feb 13 15:03:07.08: [ 711]: --> [7:CONNECT] > Feb 13 15:03:07.08: [ 711]: <-- data [23] > Feb 13 15:03:07.08: [ 711]: <-- data [2] > Feb 13 15:03:07.09: [ 711]: --> [7:CONNECT] > Feb 13 15:03:07.09: [ 711]: <-- data [13] > Feb 13 15:03:07.09: [ 711]: <-- data [2] > Feb 13 15:03:09.37: [ 711]: --> [2:OK] > Feb 13 15:03:09.37: [ 711]: <-- [9:AT+FRH=3\r] > Feb 13 15:03:16.37: [ 711]: --> [0:] > Feb 13 15:03:16.37: [ 711]: MODEM <Empty line> > Feb 13 15:03:16.37: [ 711]: <-- data [1] > Feb 13 15:03:16.38: [ 711]: --> [2:] > Feb 13 15:03:16.38: [ 711]: --> [2:OK] This means that after answering the call and sending the DIS signal that the modem did not hear any response from the caller for 7 seconds. So, HylaFAX will have the modem retransmit DIS... > Feb 13 15:03:16.38: [ 711]: <-- [9:AT+FRS=7\r] > Feb 13 15:03:16.45: [ 711]: --> [2:OK] > Feb 13 15:03:16.45: [ 711]: <-- [9:AT+FTH=3\r] > Feb 13 15:03:17.41: [ 711]: --> [7:CONNECT] > Feb 13 15:03:17.41: [ 711]: <-- data [32] > Feb 13 15:03:17.41: [ 711]: <-- data [2] > Feb 13 15:03:17.42: [ 711]: --> [7:CONNECT] > Feb 13 15:03:17.42: [ 711]: <-- data [23] > Feb 13 15:03:17.42: [ 711]: <-- data [2] > Feb 13 15:03:17.43: [ 711]: --> [7:CONNECT] > Feb 13 15:03:17.43: [ 711]: <-- data [13] > Feb 13 15:03:17.43: [ 711]: <-- data [2] > Feb 13 15:03:19.71: [ 711]: --> [2:OK] > Feb 13 15:03:19.71: [ 711]: <-- [9:AT+FRH=3\r] > Feb 13 15:03:21.93: [ 711]: --> [7:CONNECT] > Feb 13 15:03:23.73: [ 711]: --> [10:NO CARRIER] This indicates that the modem did detect a carrier (supposedly V.21 HDLC, but many modems will not be so specific) but that the carrier was lost 1.8 seconds later. > Feb 13 15:03:23.74: [ 711]: MODEM No carrier > Feb 13 15:03:23.74: [ 711]: <-- [10:AT+FRS=21\r] > Feb 13 15:03:23.95: [ 711]: --> [2:OK] > Feb 13 15:03:23.95: [ 711]: <-- [9:AT+FTH=3\r] > Feb 13 15:03:24.91: [ 711]: --> [7:CONNECT] > Feb 13 15:03:24.91: [ 711]: <-- data [3] > Feb 13 15:03:24.91: [ 711]: <-- data [2] > Feb 13 15:03:25.30: [ 711]: --> [2:OK] > Feb 13 15:03:25.30: [ 711]: RECV send CRP (command repeat) > Feb 13 15:03:25.30: [ 711]: <-- [9:AT+FRH=3\r] > Feb 13 15:03:27.51: [ 711]: --> [7:CONNECT] > Feb 13 15:03:29.32: [ 711]: --> [10:NO CARRIER] Same thing happens here as above, so I would guess that this "carrier" is not V.21 HDLC but a busy signal. > Feb 13 15:03:29.32: [ 711]: MODEM No carrier > Feb 13 15:03:29.32: [ 711]: <-- [10:AT+FRS=21\r] > Feb 13 15:03:29.53: [ 711]: --> [2:OK] > Feb 13 15:03:29.53: [ 711]: <-- [9:AT+FTH=3\r] > Feb 13 15:03:30.49: [ 711]: --> [7:CONNECT] > Feb 13 15:03:30.49: [ 711]: <-- data [3] > Feb 13 15:03:30.49: [ 711]: <-- data [2] > Feb 13 15:03:30.88: [ 711]: --> [2:OK] > Feb 13 15:03:30.88: [ 711]: RECV send CRP (command repeat) > Feb 13 15:03:30.88: [ 711]: <-- [9:AT+FRH=3\r] > Feb 13 15:03:33.09: [ 711]: --> [7:CONNECT] > Feb 13 15:03:34.89: [ 711]: --> [10:NO CARRIER] See? The "carrier" is very consistently 1.8 seconds long. > Have you any idea how to troubleshoot the problem? What kind of phone line are you using? What kind of modem are you using? Is the phone line being "shared" with a fax machine or something? If this only happens with calls from the one sender, then the problem could be on their end and not yours. Thanks, Lee. ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe [email protected] < /dev/null *To learn about commercial HylaFAX(tm) support, mail [email protected].*