Re: [hylafax-users] T.30 T1 timeout question

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

marthter wrote:

> Lee Howard wrote  on 17/03/05 05:09 PM:
>
> > marthter wrote:
> >
> > > Mar 17 08:30:13.74: [ 7547]: <-- [14:AT+FCLASS=1.0\r]
> > > Mar 17 08:30:13.84: [ 7547]: --> [2:OK]
> > > Mar 17 08:30:13.84: [ 7547]: <-- [14:AT+F34=14,1,2\r]
> > > Mar 17 08:30:13.95: [ 7547]: --> [2:OK]
> > > Mar 17 08:30:13.96: [ 7547]: DIAL 4161234567
> > > Mar 17 08:30:13.96: [ 7547]: <-- [15:ATDT4161234567\r]
> > > Mar 17 08:30:32.98: [ 7547]: --> [8:+F34:6,1]
> > > Mar 17 08:30:32.98: [ 7547]: V.8 handshaking succeeded, V.34-Fax 
> > > (SuperG3) capability enabled.
> > > Mar 17 08:30:32.98: [ 7547]: Primary channel rate: 14400 bit/s, 
> > > Control channel rate: 1200 bit/s.
> > > Mar 17 08:30:32.98: [ 7547]: --> [7:CONNECT]
> > > Mar 17 08:30:32.99: [ 7547]: Control channel selected
> > > Mar 17 08:30:32.99: [ 7547]: EOT received (end of transmission)
> >
> >
> >
> > > Mar 17 01:11:29.70: [ 4739]: SESSION BEGIN 000023371 14161234567
> > > Mar 17 01:11:29.71: [ 4739]: HylaFAX (tm) Version 4.2.1
> > > Mar 17 01:11:29.71: [ 4739]: SEND FAX: JOB 24829 DEST 416-123-4567 
> > > COMMID 000023371 DEVICE '/dev/ttyS5'
> > > Mar 17 01:11:29.71: [ 4739]: <-- [14:AT+FCLASS=1.0\r]
> > > Mar 17 01:11:29.82: [ 4739]: --> [2:OK]
> > > Mar 17 01:11:29.82: [ 4739]: <-- [14:AT+F34=14,1,2\r]
> > > Mar 17 01:11:29.93: [ 4739]: --> [2:OK]
> > > Mar 17 01:11:29.93: [ 4739]: DIAL 4161234567
> > > Mar 17 01:11:29.93: [ 4739]: <-- [15:ATDT4161234567\r]
> > > Mar 17 01:12:20.21: [ 4739]: --> [2:]
> > > Mar 17 01:12:20.22: [ 4739]: SEND FAILED: JOB 24829 DEST 
> > > 416-123-4567 ERR Unknown problem (check modem power)
> >
> > Does it work if you send without V.34-Fax?  ('sendfax -B 14400')
> >
> > Lee.
>
>
>
> Thank you for the suggestion.  Yes it seems to work (see log file below).


You may want to try updating the firmware on the modems.  If that 
doesn't help, then you should probably report the matter to the 
manufacturer.

> sendfax -B 14400 -t 1 -T 1 -vv -n -d 416-123-4567 ~/a.txt
>
> So is this likely a crappy Brother modem or noisy line to the destination?


Well, it's probably a V.8 handshaking problem with the modem.  But it 
could be a bad connection.

>   (I notice it even didn't like 14400 and retrained to 12000; is that 
> relevant?)


Maybe.  It seems indicative of connectivity problems, however the rest 
of the fax doesn't share that indication.  It's probably some other 
matter that we'd need to figure out.

>   I looked in /var/spool/hylafax/info/[destinationNumber] and it says:
>
> supportsVRes:3
> supports2DEncoding:yes
> supportsMMR:yes
> hasV34Trouble:no
> supportsPostScript:no
> supportsBatching:yes
> calledBefore:yes
> maxPageWidth:1728
> maxPageLength:65535
> maxSignallingRate:"33600"
> minScanlineTime:"10ms"
> remoteCSI:"4161234567"
> sendFailures:0
> lastSendFailure:"No answer (T.30 T1 timeout)"
> dialFailures:0
> lastDialFailure:"No carrier detected"
> &pagingProtocol:"ixo"
>
>
> Notably, whatever is setting "hasV34Trouble:no" seems to not have 
> interpreted the above errors as V34 trouble.


Some of the features in the info file are determined by direct 
interpretation of capabilities indications on the receiver.  Others, 
however, are determined by "experience".  So in the case of 
hasV34Trouble we haven't yet taught HylaFAX to recognize the kind of 
trouble that you've seen as being the kind of "experience" that 
qualifies for hasV34Trouble.

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*