Re: [hylafax-users] No receiver protocol (T.30 T1 timeout) Asterisk/IAXmodem/Hylafax

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Mark Seamans wrote:
>   1.
>       Oct 20 14:00:00.69: [29222]: SESSION BEGIN 000004080 14444445558001
>   2.
>       Oct 20 14:00:00.69: [29222]: HylaFAX (tm) Version 6.0.3
>   3.
>       Oct 20 14:00:00.69: [29222]: SEND FAX: JOB 723 DEST 4445558001
>       COMMID 000004080 DEVICE '/dev/ttyIAX3' FROM 'mark
>       <mark@xxxxxxxxx>' USER root
>   4.
>       Oct 20 14:00:00.69: [29222]: STATE CHANGE: RUNNING -> SENDING
>   5.
>       Oct 20 14:00:00.69: [29222]: <-- [14:AT+FCLASS=1.0\r]
>   6.
>       Oct 20 14:00:00.70: [29222]: --> [2:OK]
>   7.
>       Oct 20 14:00:00.70: [29222]: MODEM set XON/XOFF/FLUSH: input
>       ignored, output disabled
>   8.
>       Oct 20 14:00:00.70: [29222]: DIAL 4445558001
>   9.
>       Oct 20 14:00:00.70: [29222]: <-- [15:ATDT4445558001\r]
>  10.
>       Oct 20 14:00:04.39: [29222]: --> [7:CONNECT]
>  11.
>       Oct 20 14:00:06.03: [29222]: --> HDLC<35:FF C0 02 5A 80 55 09 4F
>       1B 43 31 60 86 81 05 0B AD A5 01 19 54 C9 D9 D2 DE CE C0 8D 8F
>       40 C7 4C CE DE 07>
>  12.
>       Oct 20 14:00:06.03: [29222]: --> [5:ERROR]
>  13.
>       Oct 20 14:00:06.03: [29222]: MODEM Command error
>  14.
>       Oct 20 14:00:06.03: [29222]: FCS error

Corrupted audio received.  So we can't use this data.

>   1.
>       Oct 20 14:00:06.03: [29222]: <-- [10:AT+FRS=21\r]
>   2.
>       Oct 20 14:00:07.59: [29222]: --> [2:OK]
>   3.
>       Oct 20 14:00:07.59: [29222]: <-- [9:AT+FTH=3\r]
>   4.
>       Oct 20 14:00:07.61: [29222]: --> [7:CONNECT]
>   5.
>       Oct 20 14:00:07.61: [29222]: <-- HDLC<3:FF C8 D8>
>   6.
>       Oct 20 14:00:07.61: [29222]: <-- data [3]
>   7.
>       Oct 20 14:00:07.61: [29222]: <-- data [2]
>   8.
>       Oct 20 14:00:08.69: [29222]: --> [2:OK]
>   9.
>       Oct 20 14:00:08.69: [29222]: SEND send CRP (command repeat)

Older protocol as found in hylafax.org 6.0.3 asks the receiver to 
repeat.  I believe that newer protocol as found in HylaFAX+ 5.4.3 will 
not do this and will simply wait for the receiver to repeat itself on 
its own (since the CRP signal apparently can confuse some).

>   1.
>       Oct 20 14:00:08.69: [29222]: <-- [9:AT+FRH=3\r]
>   2.
>       Oct 20 14:00:44.45: [29222]: --> [10:NO CARRIER]
>   3.
>       Oct 20 14:00:44.45: [29222]: MODEM No carrier
>   4.
>       Oct 20 14:00:44.45: [29222]: <-- [9:AT+FRH=3\r]
>   5.
>       Oct 20 14:00:44.45: [29222]: --> [5:ERROR]

The call was lost, but no fax signal was detected for 26 seconds there.  
Did faxdetection occur and steal-away the call.  Are you really using 
PSTN interfaces?  Or are you using VoIP channels for your fax audio?

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*