[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hylafax
Subject:    Re: [hylafax-users] (T.30 T1 timeout) (code 11)
From:       shouldbe q931 <shouldbeq931 () gmail ! com>
Date:       2012-03-22 16:13:37
Message-ID: CAP1_MOBh-RmNWZmyOTAtAAZ3MXWj0H5yDr39k=b=q5rK7cK8Eg () mail ! gmail ! com
[Download RAW message or body]

On Thu, Mar 22, 2012 at 12:10 AM, Lee Howard <faxguy@howardsilvan.com> wrote:
> Mauro Geroldi [fabbricadigitale] wrote:
>>
>>
>> Hi all,
>>
>> I am running Hylafax 6.0.4 on the following platform:
>>
>> OS: Linux Red Hat Enterprise 4
>>
>> Modem: Eicon Diva Pri
>>
>> I have some trouble with the error “(T.30 T1 timeout) (code 11)”; here’s
>> an example:
>>
>> Mar 20 12:10:54.98: [31843]: SESSION BEGIN 002006661 XXXXXXXXXXX
>>
>> Mar 20 12:10:54.98: [31843]: HylaFAX (tm) Version 6.0.4
>>
>> Mar 20 12:10:54.98: [31843]: SEND FAX: JOB 830953 DEST XXXXXXX COMMID
>> 002006661 DEVICE '/dev/ttyds09' FROM 'XXXXXXXXX' USER XXXXXXX
>>
>> Mar 20 12:10:54.98: [31843]: <-- [10:AT+FBOR=0\r]
>>
>> Mar 20 12:10:54.98: [31843]: --> [2:OK]
>>
>> Mar 20 12:10:54.98: [31843]: <-- [3:AT\r]
>>
>> Mar 20 12:10:54.98: [31843]: --> [2:OK]
>>
>> Mar 20 12:10:54.98: [31843]: <-- [24:AT+FDCC=7,5,2,2,0,2,0,0\r]
>>
>> Mar 20 12:10:54.98: [31843]: --> [2:OK]
>>
>> Mar 20 12:10:54.98: [31843]: DIAL XXXXXXXXX
>>
>> Mar 20 12:10:54.98: [31843]: <-- [15:ATDT0810485190\r]
>>
>> Mar 20 12:11:20.40: [31843]: --> [9:+FHNG: 11]
>>
>> *Mar 20 12:11:20.40: [31843]: REMOTE HANGUP: No answer (T.30 T1 timeout)
>> (code 11)*
>>
>>
>> Mar 20 12:11:20.40: [31843]: SEND FAILED: JOB 830953 DEST XXXXXXXXXX ERR
>> [7] Carrier established, but Phase A failure
>>
>> Mar 20 12:11:21.41: [31843]: <-- [5:ATH0\r]
>>
>> Mar 20 12:11:21.41: [31843]: --> [2:OK]
>>
>> Mar 20 12:11:21.41: [31843]: SESSION END
>>
>> Is there a parameter that increases the “T.30 T1 timeout”?
>>
>> I tried to set “FaxT1Timer: 60000” but the timeout is always after 26 sec.
>
>
> It's not FaxT1Timer.
>
> ModemWaitTimeCmd defaults to ATS7=60, so unless you've changed that modem
> configuration option it should not be giving you a "no answer" condition at
> 26 seconds. But since you're using a T1 instead of analogic lines it's
> certainly possible that there was a fatal call indication at 26 seconds.
> You'd probably need to get into debugging levels with the Eicon Diva to know
> for-sure what's going on.
>
> Thanks,
>
> Lee.
>
>


You can enable call tracing on the Diva card, this should show the
ISDN disconnect cause.

Have you been able to pass _any_ test calls using the Diva ?


____________________ 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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@ifax.com.*

[prev in list] [next in list] [prev in thread] [next in thread]