![]() |
Hi Peter. I can't give you an exact failure rate that you can expect but one of our customers recently undertook some comparison tests in the US which had 2 fax's fail and 114390 fax's complete successfully during a one month period. The application was Windows based, Class 1, send only, and the fax's varied from 1 to 13 pages in length. Our in-house testing gives similar levels of reliability for HylaFAX and we have tested against 50 or so fax machines and many competitors products in our lab. We have seen problems in the past and had one example of a fax machine that would crash an Agere DSP at will. If your problems are repeatable then a log will probably help identify who's at fault and then whether HylaFAX can do anything about it.... the difficulty comes when it's the fax machine thats 'broken'.... trying to get these guys to sort out problems is a joy ! Regards Andrew Rinaldi Mainpine Support e: support@xxxxxxxxxxxx w: http://www.mainpine.com t: +44(0) 1373 830888 f: +44(0) 1373 830768 -----Original Message----- From: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of Peter Schoenster Sent: 02 September 2005 05:28 To: hylafax-users@xxxxxxxxxxx Subject: [hylafax-users] What is your percentage of hard failures Hi, I am getting over 50% failures in outgoing faxes. It doesn't make sense to me. It would make sense if I got 100% failure. I'm not talking about busy signals etc. I'm talking about when hylafax connects to a remote fax machine but fails to commmnicate, time and time again. I get these 2 errors: ERR No carrier detected = when using Class 1 No answer (T.30 T1 timeout) = when using Class 2.0 The same destination fax will return those 2 errors depending on what I set for ModemType in config.modem I've searched the archives and the web and I found 2 guys in the last 4 years who seemed to have the same problem as me. I sent an email to both. One guy said it was never resolved and he just used mgetty+sendfax on freebsd and has been fine with that. Perhaps this is normal? Are there fax machines with which hylafax cannot communicate? I have been testing with one fax number. The person who owns the fax says that they see "Receiving ..." but then nothing happens and the call just terminates. If using my Savin fax machine I can send a fax to this fax machine. I looked in some old logs from our fax server and it seems like it has always been this way. I recently had to rebuild our linux box which serves as the fax gateway and so I've been testing. In the past the previous admin would ask me if our apps were sending faxes. I'd test it against our local fax machine and if it worked I said all was well. I never though to test against other types of fax machines. Our previous admin would send out results which showed successful faxes sent but not failures. Yet in the logs from the previous linux configuration I see the same number of errors. Anyone got a clue on this one? I did try adding the commas as someone suggested as I was just curious but it made no difference. Thanks. ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ____________________ 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* ____________________ 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*