Re: [hylafax-users] Wrong fax number used after a "No carrier detected" error

[nick <nick@xxxxxxxxxx>]

erich.iseli@xxxxxxxxxxxxxxxx wrote:
> Hello,
>
> I've already posted this problem before
> (http://www.hylafax.org/archive/2005-06/msg00098.php
> <http://www.hylafax.org/archive/2005-06/msg00098.php> ) but in the mean
> time I've found out more: Whenever the modem detects no carrier and the
> communication lasts 0:01 to 0:02 (1-2 seconds), the following fax will go
> out to the number where no carrier was detected. See the transcripts below.
> Note that hylafax thinks it's sending to the right number, but the remote
> fax shows through ist CSI that it's clearly not the case.
>
> Now I've noticed that there are 2 kinds of "no carrier detected": one when
> there's no tone on the line (that would be the case if the communication
> lasts 1-2 seconds) and one when the modem dials but the fax is answered by a
> human and doesn't communicate with the caller fax, then hangs up. In this
> case, my logs show that the communication usually lasts about 20 seconds.
>
> So now I'm wondering: why would the modem get no dial tone? I don't know
> about our phone line, but I've never picked up the phone without getting a
> tone. So that should be the same with the faxmodem.
>
> And also: why would the modem remember the previous phone number instead of
> dialling the new one? Doesn't it listen to the commands sent by hylafax? Is
> there a way to reset the modem through hylafax, whenever it begins a new
> session?
>
> Thanks for your insights,
>
> Erich
>
>
> P.S. Our Modem is an ELSA MicroLink ISDN/TL V.34
>
>
>
>
>
>
> Jun 14 08:58:44.63: [20993]: SESSION BEGIN 000009983 41123456789
> Jun 14 08:58:44.63: [20993]: HylaFAX (tm) Version 4.2.0
> Jun 14 08:58:44.63: [20993]: SEND FAX: JOB 9077 DEST 0123456789 COMMID
> 000009983 DEVICE '/dev/ttyS0'
> Jun 14 08:58:44.63: [20993]: <-- [9:AT+FLO=1\r]
> Jun 14 08:58:44.78: [20993]: --> [2:OK]
> Jun 14 08:58:44.78: [20993]: <-- [9:AT+FPP=0\r]
> Jun 14 08:58:44.93: [20993]: --> [2:OK]
> Jun 14 08:58:44.93: [20993]: <-- [9:AT+FBO=0\r]
> Jun 14 08:58:45.08: [20993]: --> [2:OK]
> Jun 14 08:58:45.08: [20993]: <-- [10:AT+FCT=30\r]
> Jun 14 08:58:45.23: [20993]: --> [2:OK]
> Jun 14 08:58:45.23: [20993]: <-- [15:AT+FNR=1,1,1,1\r]
> Jun 14 08:58:45.38: [20993]: --> [2:OK]
> Jun 14 08:58:45.38: [20993]: <-- [9:AT+FIE=0\r]
> Jun 14 08:58:45.53: [20993]: --> [2:OK]
> Jun 14 08:58:45.53: [20993]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
> Jun 14 08:58:45.68: [20993]: --> [2:OK]
> Jun 14 08:58:45.68: [20993]: DIAL 0123456789
> Jun 14 08:58:45.68: [20993]: <-- [15:ATDT0123456789\r]
> Jun 14 08:58:45.87: [20993]: --> [10:NO CARRIER]
> Jun 14 08:58:45.87: [20993]: SEND FAILED: JOB 9077 DEST 0123456789 ERR No
> carrier detected
> Jun 14 08:58:45.87: [20993]: <-- [5:ATH0\r]
> Jun 14 08:58:45.99: [20993]: --> [2:OK]
> Jun 14 08:58:45.99: [20993]: SESSION END
> ===================================
> Jun 14 08:58:58.06: [21136]: SESSION BEGIN 000009984 4198765432
> Jun 14 08:58:58.06: [21136]: HylaFAX (tm) Version 4.2.0
> Jun 14 08:58:58.06: [21136]: SEND FAX: JOB 9079 DEST 098765432 COMMID
> 000009984 DEVICE '/dev/ttyS0'
> Jun 14 08:58:58.06: [21136]: <-- [9:AT+FLO=1\r]
> Jun 14 08:58:58.22: [21136]: --> [2:OK]
> Jun 14 08:58:58.22: [21136]: <-- [9:AT+FPP=0\r]
> Jun 14 08:58:58.36: [21136]: --> [2:OK]
> Jun 14 08:58:58.36: [21136]: <-- [9:AT+FBO=0\r]
> Jun 14 08:58:58.50: [21136]: --> [2:OK]
> Jun 14 08:58:58.50: [21136]: <-- [10:AT+FCT=30\r]
> Jun 14 08:58:58.64: [21136]: --> [2:OK]
> Jun 14 08:58:58.64: [21136]: <-- [15:AT+FNR=1,1,1,1\r]
> Jun 14 08:58:58.79: [21136]: --> [2:OK]
> Jun 14 08:58:58.79: [21136]: <-- [9:AT+FIE=0\r]
> Jun 14 08:58:58.94: [21136]: --> [2:OK]
> Jun 14 08:58:58.94: [21136]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
> Jun 14 08:58:59.10: [21136]: --> [2:OK]
> Jun 14 08:58:59.10: [21136]: DIAL 098765432
> Jun 14 08:58:59.10: [21136]: <-- [15:ATDT098765432\r]
> Jun 14 08:59:17.13: [21136]: --> [4:+FCO]
> Jun 14 08:59:20.52: [21136]: --> [53:+FNF: 00 00 66 01 10 0B B2 6A 10 00 00
> 00 00 00 00 24]
> Jun 14 08:59:20.52: [21136]: REMOTE NSF " 00 00 66 01 10 0B B2 6A 10 00 00
> 00 00 00 00 24"
> Jun 14 08:59:20.52: [21136]: NSF remote fax equipment: Utax/Mita 
> Jun 14 08:59:20.66: [21136]: --> [83:+FNF: 00 00 66 02 15 4E 4F 4B 49 46 46
> 45 41 46 50 20 47 41 20 52 45 52 45 48 43 53]
> Jun 14 08:59:20.66: [21136]: REMOTE NSF " 00 00 66 02 15 4E 4F 4B 49 46 46
> 45 41 46 50 20 47 41 20 52 45 52 45 48 43 53"
> Jun 14 08:59:20.66: [21136]: NSF remote fax equipment: Utax/Mita 
> Jun 14 08:59:20.66: [21136]: NSF remote station ID: "ABC"
> Jun 14 08:59:20.66: [21136]: --> [27:+FCI:"    +41 12 345 67 89"]
> Jun 14 08:59:20.66: [21136]: REMOTE CSI "+41 12 345 67 89"
> (...)
>
>
> Mit freundlichen Grüssen - kind regards - Meilleures salutations -
> Vriendelijke groeten
>
> Erich Iseli

I don't know if this will help or not, but we had a similar problem at a 
client site, where they used a hylafax server for sending and recieving, 
and a had a normal fax machine around for sending off documents that had 
to be signed, etc. What would happen was the fax machine would be 
sending a fax, and be finished, but hadn't yet hung up the line, and 
hylafax would open a connection, supposedly to a different number, but 
would actually send to the number the regular fax machine had called (as 
the connection was still open).

We got rid of this problem by adding a second line, but it was 
definitely a weird problem. Above all because it didn't happen very 
frequently, so it was hard to figure out what was happening.

Nick



____________________ 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*