Re: [hylafax-users] Unspecified Transmit Phase C error with Class 1

["Andrew Rinaldi" <andrew.rinaldi@xxxxxxxxxxxx>]

Hi Andrea,

We have found multiple sources of 'wedging' on HylaFAX.  The most common
cause is a modem firmware 'malfunction' which results in the Controller
and/or DSP crashing.  However, other sources exist including hardware issues
(Agere Venus has an interrupt status bug for instance), and even serial
driver 'bugs' (yes, I know it's hard to believe but a lot is changing in the
Linux serial driver world).

The first thing to try is a modem firmware upgrade.  Second is to try a
different version of HylaFAX (this will subtly change the system timing and
has been observed to make a difference).  Third is to change the OS version.
Forth is to change the host hardware.  Fifth is to change the modem.

If none of these fix the issue then (and here's my plug) using a Mainpine
modem you can automatically reset the port from the 'wedged' process.

Regards

ANDREW RINALDI
Mainpine Limited - Support
USA +1 503 822 9944 | Asia/Europe +44 1225 869439  
andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com

-----Original Message-----
From: hylafax-users-bounces@xxxxxxxxxxxxxxxxxxxxx
[mailto:hylafax-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Lee Howard
Sent: 01 May 2007 01:42
To: Andrea.Un@xxxxxxxxxxxxxx
Cc: hylafax-users@xxxxxxxxxxx; hylafax-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [hylafax-users] Unspecified Transmit Phase C error with Class 1

Andrea.Un@xxxxxxxxxxxxxx wrote:

> We have just installed HylaFAX+ version 5.1.2 on our test/R&D server 
> but have not began testing yet.  Does this version have the modem 
> reset routine you mentioned or is it only available in the latest 
> 5.1.3 version?


It's in 5.1.2 also, yes.  That feature was last refined in 5.0.4... so 
you're okay with 5.1.2.

> Do you have any suggestions on how we can test this properly to see if 
> the modem reset routine would work?


Not really.  You'll need to try to reproduce the problem scenario and 
see if it still wedges or not.  I would recommend testing 5.1.2 to see 
if it will work for you in production and move it there where you're 
getting the problems.  If you never get a wedged modem for several times 
the frequency of its current wedging, then you can assume that it did 
the trick.

That said, it really does look like a modem problem.  Although it's 
possible that the HylaFAX+ reset routine may recover it, I wouldn't hold 
out large amounts of hope for that.  Nonetheless, it is my opinion that 
you will benefit, anyway, from the 5.1.2 deployment.

Lee.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
hylafax-users mailing list
hylafax-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/hylafax-users



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