HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

[hylafax-users] hasV34trouble



Version 4.2.0-cvs20041001,  multitech v92 mba external

I looked at some v34 logs.

In one case hasv34trouble was flagged into info/<faxno>:
Feb 25 20:01:47.93: [17166]: Control channel selected
Feb 25 20:01:47.93: [17166]: Primary channel rate now 7200 bit/s
Feb 25 20:01:47.93: [17166]: <-- data [7]
Feb 25 20:01:47.93: [17166]: <-- data [2]
Feb 25 20:01:47.93: [17166]: SEND send PPS (partial page signal)
Feb 25 20:01:47.93: [17166]: SEND send EOP (no more pages or documents)
Feb 25 20:01:48.51: [17166]: SEND recv PPR (partial page request)
Feb 25 20:01:48.51: [17166]: Failure to transmit clean MMR image data.
Feb 25 20:01:48.51: [17166]: SEND end page
Feb 25 20:01:48.51: [17166]: The destination appears to have trouble with
V.34-Fax.
Feb 25 20:01:48.51: [17166]: <-- data [3]


Then I have another case where in the last month, I got 9 times the same
error on 13 jobs, this was not flagged as trouble in info/<faxno>.
Feb 02 17:06:43.03: [ 4777]: --> [9:+F34:13,1]
Feb 02 17:06:43.03: [ 4777]: V.8 handshaking succeeded, V.34-Fax (SuperG3)
capab
ility enabled.
Feb 02 17:06:43.03: [ 4777]: Primary channel rate: 31200 bit/s, Control
channel
rate: 1200 bit/s.
Feb 02 17:06:43.03: [ 4777]: --> [7:CONNECT]
Feb 02 17:06:43.03: [ 4777]: Control channel selected
Feb 02 17:06:43.16: [ 4777]: REMOTE NSF "00 00 56 55 55 00 8C 90 80 6E 03"
Feb 02 17:06:43.16: [ 4777]: NSF remote fax equipment: Brother
Feb 02 17:06:43.34: [ 4777]: REMOTE CSI "0000 000000"
Feb 02 17:06:43.45: [ 4777]: REMOTE best rate 33600 bit/s
Feb 02 17:06:43.45: [ 4777]: REMOTE max A4 page width (215 mm)
Feb 02 17:06:43.45: [ 4777]: REMOTE max unlimited page length
Feb 02 17:06:43.45: [ 4777]: REMOTE best vres 15.4 line/mm
Feb 02 17:06:43.45: [ 4777]: REMOTE best format 2-D MMR
Feb 02 17:06:43.45: [ 4777]: REMOTE supports T.30 Annex A, 256-byte ECM
Feb 02 17:06:43.45: [ 4777]: REMOTE best 10 ms/scanline
Feb 02 17:06:43.45: [ 4777]: USE 31200 bit/s
Feb 02 17:06:43.45: [ 4777]: USE error correction mode
Feb 02 17:06:43.45: [ 4777]: USE 0 ms/scanline
Feb 02 17:06:43.45: [ 4777]: SEND file "docq/doc38524.ps;c2"
...
Feb 02 17:06:48.44: [ 4777]: <-- data [2]
Feb 02 17:06:48.44: [ 4777]: <-- data [3]
Feb 02 17:06:48.44: [ 4777]: <-- data [2]
Feb 02 17:06:48.44: [ 4777]: <-- data [3]
...
Feb 02 17:06:48.44: [ 4777]: <-- data [2]
Feb 02 17:06:48.44: [ 4777]: <-- data [2]
Feb 02 17:06:55.62: [ 4777]: EOT received (end of transmission)
Feb 02 17:06:55.62: [ 4777]: Failed to properly open control V.34 channel.
Feb 02 17:06:55.62: [ 4777]: SEND end page
Feb 02 17:06:55.62: [ 4777]: <-- data [3]

However, I have another receiver where the same error (Failed to properly
open control V.34 channel) happened just 1 time in 55 tries (54 tries OK). 

So, this error is quite complicated to handle.

Is this a case where we should edit by hand info/<faxno> and force 34trouble
case by case?

Do you have experience that Brother are a bit troublesome?

Thanks

-- 
giulioo@xxxxxxxxx

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




Project hosted by iFAX Solutions