Re: flexfax: phase B error and garbage from remote end

[Robert Colquhoun <rjc@trump.net.au>]

Hi Velocet,
Have a look at
	http://www.trump.net.au/~rjc/hylafax/usr.php

I even mention WinFax

-Robert

At 17:23 23/02/98 -0500, Velocet wrote:
>First post to the list, hope I really have exhausted online resources...
>(I've been toying with this for 2 hours and read every faq entry that
>matches the word 'phase' on http://www.vix.com/hylafax/FAQ/ - so am I
>still guilty? :)
>
>I am suprised someone else hasnt run into this, I am sure they have, which
>is why I think I didnt look hard enough at this.
>
>---------------------------------------------------------------------------
---
>Background info:
>
>Fax out only environment (tho we have dialup PPP on the same line for
>users, which is working fine.)
>
>
>Version: hylafax-v4.0pl1
>OS:	FreeBSD 2.2.2-RELEASE
>GCC:	gcc version 2.7.2.1
>Modem:	USR Sportster 33600/Fax V2.32 (faxaddmodem made it use usr-2.0 config,
>					and its a class 2.0 modem)
>
>Problem: Unspecified Transmit Phase B error (code 20)
>
>---------------------------------------------------------------------------
---
>My attempts: Tried setting Use2D: no and the 
>
>Class2DDISCmd:      AT+FDIS
>
> command in etc/config.cuaa2, but that made things worse (the modem got
> an ERROR trying to intialize and my fax was removed right away).
>
>I also changed the modem speed in config.cuaa2 to 19200 thinking 'garbage'
>meant wrong baud rate, but it shouldnt affect it if I think clearly about
>it, and well, it didnt help.
>
>---------------------------------------------------------------------------
---
>Checking Q.145 (list of error codes) on that FAQ list tells me that
> code 20 is.. an Unspecified Transmit Phase B error.  Great! :)
>
>I have no problems faxing to two other hylafax servers running on 
>another USR Sportster 33.6 Fax, and the other on a GVC fax modem
>(both also  same version of HylaFax and FreeBSD).
>
>However, I have problems sending to a USR v.34 everything (I think it is,
>another client's fax server) running WinFax, as well as 'real' fax machines.
>
>Typical logfile: you can see there looks  like garbage during the FIS or
>whatever handshake it is there, but then we get an "OK" from the remote
>end (if I am not mistaken as to where that OK came from). So, tho it looks
>like a speed problem or something to my many-years-of-modems eyes, I've
>also heard that some fax machines put a buncha garbage out during this
>phase of the connection, and this seems to be confusing our end, which
>is confusing their end. (Or something). Tho it says "remote hangup" the
>guy on the other end tells me that its still connected but not receiving
>anything, then eventually gives up (long after my modem has already
>hung up).
>
>Ideas?
>
>Thanks for the help.
>
>(50 line logfile is at the bottom)
>
>/kc
>-- 
>Ken Chase, Velocet Communications Inc.	   math@velocet.ca	Toronto CANADA
>--
>"Sometimes two [harmless] words, when put together, strike fear in the
>  hearts of men -- Microsoft Wallet." 				- Dave Gilbert
>
>
>---------------------------------------------------------------------------
---
>
>Feb 23 16:51:16.35: [29129]: SESSION BEGIN 00000110 14169550882
>Feb 23 16:51:16.36: [29129]: SEND FAX: JOB 32 DEST 9550882 COMMID 00000110
>Feb 23 16:51:16.36: [29129]: DELAY 2600 ms

>Feb 23 16:51:18.97: [29129]: <-- [17:ATE0V1Q0X4S0=0H0\r]
>Feb 23 16:51:19.11: [29129]: --> [2:OK]
>Feb 23 16:51:19.11: [29129]: <-- [32:ATS8=2S7=60&H1&I0&R2S13=1&D2&C1\r]
>Feb 23 16:51:19.26: [29129]: --> [2:OK]
>Feb 23 16:51:19.26: [29129]: <-- [14:AT+FCLASS=2.0\r]
>Feb 23 16:51:19.40: [29129]: --> [2:OK]
>Feb 23 16:51:19.40: [29129]: <-- [9:AT+FLO=2\r]
>Feb 23 16:51:19.54: [29129]: --> [2:OK]
>Feb 23 16:51:19.54: [29129]: <-- [9:AT+FPP=0\r]
>Feb 23 16:51:19.68: [29129]: --> [2:OK]
>Feb 23 16:51:19.68: [29129]: <-- [9:AT+FBO=0\r]
>Feb 23 16:51:19.82: [29129]: --> [2:OK]
>Feb 23 16:51:19.82: [29129]: <-- [10:AT+FCT=30\r]
>Feb 23 16:51:19.96: [29129]: --> [2:OK]
>Feb 23 16:51:19.96: [29129]: <-- [15:AT+FNR=1,1,1,1\r]
>Feb 23 16:51:20.10: [29129]: --> [2:OK]
>Feb 23 16:51:20.10: [29129]: <-- [9:AT+FIE=0\r]
>Feb 23 16:51:20.24: [29129]: --> [2:OK]
>Feb 23 16:51:20.24: [29129]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
>Feb 23 16:51:20.39: [29129]: --> [2:OK]
>Feb 23 16:51:20.39: [29129]: <-- [5:ATM0\r]
>Feb 23 16:51:20.52: [29129]: --> [2:OK]
>Feb 23 16:51:20.53: [29129]: <-- [14:AT+FCLASS=2.0\r]
>Feb 23 16:51:20.77: [29129]: --> [2:OK]
>Feb 23 16:51:20.77: [29129]: <-- [9:AT+FLO=2\r]
>Feb 23 16:51:21.01: [29129]: --> [2:OK]
>Feb 23 16:51:21.01: [29129]: <-- [9:AT+FPP=0\r]
>Feb 23 16:51:21.25: [29129]: --> [2:OK]
>Feb 23 16:51:21.25: [29129]: <-- [9:AT+FBO=0\r]
>Feb 23 16:51:21.49: [29129]: --> [2:OK]
>Feb 23 16:51:21.49: [29129]: <-- [10:AT+FCT=30\r]
>Feb 23 16:51:21.73: [29129]: --> [2:OK]
>Feb 23 16:51:21.73: [29129]: <-- [15:AT+FNR=1,1,1,1\r]
>Feb 23 16:51:21.97: [29129]: --> [2:OK]
>Feb 23 16:51:21.97: [29129]: <-- [9:AT+FIE=0\r]
>Feb 23 16:51:22.21: [29129]: --> [2:OK]
>Feb 23 16:51:22.21: [29129]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
>Feb 23 16:51:22.46: [29129]: --> [2:OK]
>Feb 23 16:51:22.46: [29129]: <-- [13:AT+FLI="CDA"\r]
>Feb 23 16:51:22.70: [29129]: --> [2:OK]
>Feb 23 16:51:22.74: [29129]: DIAL 9,9550882
>Feb 23 16:51:22.74: [29129]: <-- [14:ATDT9,9550882\r]
>Feb 23 16:51:39.63: [29129]: --> [4:+FCO]
>Feb 23 16:51:42.11: [29129]: --> [15:+FNF:CI:"   ]
>Feb 23 16:51:42.11: [29129]: REMOTE NSF "CI:""
>Feb 23 16:51:42.11: [29129]: --> [32:      4169550882"s+FIS:1,3,0,2,0]
>Feb 23 16:51:42.11: [29129]: --> [43:0,0,3�wHC�:F����
>
/���˯�����^`���V+/��b�]
>Feb 23 16:51:42.23: [29129]: --> [24:������������������������]
>Feb 23 16:51:42.23: [29129]: --> [2:OK]
>Feb 23 16:51:42.23: [29129]: REMOTE HANGUP: Unspecified Transmit Phase B
error (code 20)
>Feb 23 16:51:42.23: [29129]: SEND FAILED: Unspecified Transmit Phase B error
>Feb 23 16:51:42.23: [29129]: <-- [5:ATH0\r]
>Feb 23 16:51:42.47: [29129]: --> [2:OK]
>Feb 23 16:51:42.48: [29129]: SESSION END
>