Re: [hylafax-users] Dreaded phase C errors

["Glen B" <webmaster@xxxxxxxxxxxx>]

 Even though Lee has already noted the firmware issue, I'll post my questions just for giggles.


1) Is the mingetty program running properly on the device?

2) Why not run @ 38400 on the port? Any 56K modem should be able to operate at a 38400 line rate. 19200 is fine, but it will notably
slow down larger fax jobs.

3) Did you train the modem to the line rate you specified in the Hylafax config?

cu -l /dev/[ttyname] -s [speed]
at&w
~.

4) Are you having this problem with a specific brand of fax on the other side, or is it on all transmissions?

5) Have you tested your fax line noise level?

This is for ConnectWare, so I assume it will work for your 56K Digi RAS modem.
Go into minicom, or another terminal program, and dial a local fax or modem number that you know will answer.

ATDTXXXXXXX

 <-  CONNECT XXXXXX

+++
AT%L

 <-  010    (-10dBm recieve level)
 <-  OK

ATH

 <- NO CARRIER

A number between 018 and 025 is ideal. The lower the number, the more noise on the line. Most modem AT command sets have a line
quality report command. Some show it as a line under an ATI command, but you need to be connected. You don't have to use your RAS
modem to test the line, but it helps to use the problematic device first. Compare that level with the level reported by another
brand modem. You never know. The connector could be dirty on one modem and a comparison may point that out.

Regards,

Glen
http://mvdevcentral.com


> -----Original Message-----
> From: hylafax-users-bounce@xxxxxxxxxxx
> [mailto:hylafax-users-bounce@xxxxxxxxxxx]On Behalf Of Jeff DeFord
> Sent: Thursday, April 21, 2005 4:46 PM
> To: hylafax-users@xxxxxxxxxxx
> Subject: [hylafax-users] Dreaded phase C errors
>
>
> All:
>
> I am still seeing the dreaded phase C errors in spite of the various
> configuration settings I have tried.
>
> Log sample:
> Apr 21 13:37:13.21: [16973]: <-- data [165]
> Apr 21 13:37:13.23: [16973]: SENT 36005 bytes of data
> Apr 21 13:37:13.23: [16973]: <-- data [2]
> Apr 21 13:37:13.23: [16973]: SEND end page
> Apr 21 13:40:13.23: [16973]: MODEM TIMEOUT: reading line from modem
> Apr 21 13:40:13.23: [16973]: MODEM <Timeout>
> <<<<next log>>>>
> Apr 21 13:47:45.01: [17622]: REMOTE HANGUP: Unspecified Transmit Phase
> C error (code 40)
> Apr 21 13:47:45.01: [17622]: --> [2:OK]
> Apr 21 13:47:45.01: [17622]: SEND: Unspecified Transmit Phase C error;
> Giving up after 3 attempts to send same page "d
> ocq/doc380.ps;31", dirnum 0
>
>
> I am running HylaFAX Version 4.2.1 on Redhat 7.1 (kernel 2.4.2-2) with
> Digi INTERNATIONAL RAS modem 56000/V80006691_M2-K56_DS as the
> hardware. <<<BTW, this is an outbound fax server only>>>
>
> I have tried to force class1, class 2.0, and now I'm back to class2.
> Note: running cu & issuing at+fclass=? yields
> 0,1,2,2.0,8
>
>
> Here is my *current* config
> # Modem-related stuff: should reflect modem command interface
> # and hardware connection/cabling (e.g. flow control).
> #
> # prototype config for Digi AccelePort RAS
> # It uses a K56 chip, but is similar in behavior to Lucents.
> #
> # Note that because the devices are named as "ttyG0_00" (which on some
> # systems indicates a subdirectory, i.e. "ttyG0/00") you must:
> # `ln -s /dev/ttyG0_00 /dev/ttyG000`
> # for each device and refer to the symlink.  Otherwise various HylaFAX
> # functions will fail.
>
> # CONFIG: CLASS2:"Digi"*-"RAS modem"*-*
> #
> # BEGIN-SERVER
> # END-SERVER
>
> ModemType:             Class2         # use this to supply a hint
> ModemRate:             19200
> ModemFlowControl:      rtscts
> ModemNoFlowCmd:        AT&K0
> ModemSoftFlowCmd:      AT&K4
> ModemHardFlowCmd:      AT&K3
>
> Class2APQueryCmd:      none           # not available
>
> # If your line supports Caller-ID, you may want to uncomment this...
> # ModemResetCmds:      "AT#CID=1"
> # CallIDPattern:       "NMBR="
> # CallIDPattern:       "NAME="
>
> # unfortunately, HylaFAX can't currently receive in MMR
> ModemAnswerCmd:        AT+FCC=,,,,1;A
>
> Any ideas?  I am tired of beating my head against the wall and our
> customer is *very* tired of failed jobs :-/
>
> -=jeff
>
> ____________________ 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*