Re: flexfax: Unspecified Transmit Phase B error (code 20)

[Mujtaba Ali <mujtaba@zynex.com>]

Hello there,

Here is the log as requested: (see below for thread) Thanks

Feb 15 00:30:46.80: [  650]: SESSION BEGIN 00000008 14104107447753
Feb 15 00:30:46.80: [  650]: SEND FAX: JOB 8 DEST 4107447753 COMMID 00000008
Feb 15 00:30:46.80: [  650]: DELAY 2600 ms
Feb 15 00:30:49.41: [  650]: <-- [17:ATE0V1Q0X4S0=0H0\r]
Feb 15 00:30:49.55: [  650]: --> [2:OK]
Feb 15 00:30:49.55: [  650]: <-- [32:ATS8=2S7=60&H1&I0&R2S13=1&D2&C1\r]
Feb 15 00:30:49.69: [  650]: --> [2:OK]
Feb 15 00:30:49.69: [  650]: <-- [14:AT+FCLASS=2.0\r]
Feb 15 00:30:49.82: [  650]: --> [2:OK]
Feb 15 00:30:49.82: [  650]: <-- [9:AT+FLO=2\r]
Feb 15 00:30:49.95: [  650]: --> [2:OK]
Feb 15 00:30:49.95: [  650]: <-- [9:AT+FPP=0\r]
Feb 15 00:30:50.08: [  650]: --> [2:OK]
Feb 15 00:30:50.08: [  650]: <-- [9:AT+FBO=0\r]
Feb 15 00:30:50.21: [  650]: --> [2:OK]
Feb 15 00:30:50.21: [  650]: <-- [10:AT+FCT=30\r]
Feb 15 00:30:50.35: [  650]: --> [2:OK]
Feb 15 00:30:50.35: [  650]: <-- [15:AT+FNR=1,1,1,1\r]
Feb 15 00:30:50.49: [  650]: --> [2:OK]
Feb 15 00:30:50.49: [  650]: <-- [9:AT+FIE=0\r]
Feb 15 00:30:50.63: [  650]: --> [2:OK]
Feb 15 00:30:50.63: [  650]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
Feb 15 00:30:50.77: [  650]: --> [2:OK]
Feb 15 00:30:50.77: [  650]: <-- [5:ATM0\r]
Feb 15 00:30:50.90: [  650]: --> [2:OK]
Feb 15 00:30:50.92: [  650]: <-- [14:AT+FCLASS=2.0\r]
Feb 15 00:30:51.16: [  650]: --> [2:OK]
Feb 15 00:30:51.16: [  650]: <-- [9:AT+FLO=2\r]
Feb 15 00:30:51.40: [  650]: --> [2:OK]
Feb 15 00:30:51.40: [  650]: <-- [9:AT+FPP=0\r]
Feb 15 00:30:51.64: [  650]: --> [2:OK]
Feb 15 00:30:51.64: [  650]: <-- [9:AT+FBO=0\r]
Feb 15 00:30:51.88: [  650]: --> [2:OK]
Feb 15 00:30:51.88: [  650]: <-- [10:AT+FCT=30\r]
Feb 15 00:30:52.12: [  650]: --> [2:OK]
Feb 15 00:30:52.12: [  650]: <-- [15:AT+FNR=1,1,1,1\r]
Feb 15 00:30:52.36: [  650]: --> [2:OK]
Feb 15 00:30:52.36: [  650]: <-- [9:AT+FIE=0\r]
Feb 15 00:30:52.60: [  650]: --> [2:OK]
Feb 15 00:30:52.60: [  650]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
Feb 15 00:30:52.84: [  650]: --> [2:OK]
Feb 15 00:30:52.84: [  650]: <-- [30:AT+FLI="Bookstore"\r]
Feb 15 00:30:53.08: [  650]: --> [2:OK]
Feb 15 00:30:53.08: [  650]: DIAL 4107447753
Feb 15 00:30:53.08: [  650]: <-- [15:ATDT4107447753\r]
Feb 15 00:31:13.99: [  650]: --> [4:+FCO]
Feb 15 00:31:17.11: [  650]: --> [41:+FNF:+FCI:"            744 7753"+FIS:1,]
Feb 15 00:31:17.11: [  650]: REMOTE NSF "+FCI:"            744 7753"+FIS:1,"
Feb 15 00:31:17.11: [  650]: --> [37:,0,2,0,0,0,4��������� �������� �����]
Feb 15 00:31:17.11: [  650]: --> [2:OK]
Feb 15 00:31:17.11: [  650]: REMOTE HANGUP: Unspecified Transmit Phase B error (code 20)
Feb 15 00:31:17.11: [  650]: SEND FAILED: Unspecified Transmit Phase B error
Feb 15 00:31:17.11: [  650]: <-- [5:ATH0\r]
Feb 15 00:31:17.34: [  650]: --> [2:OK]
Feb 15 00:31:17.36: [  650]: SESSION END

					- Mujtaba Ali

On Tue, 16 Feb 1999, David Woolley wrote:

> > Generic Modem (store worker claimed it was U.S. Robotics compatible and
> > faxaddmodem also "thought" it was U.S. Robotics); 33.6Kbps; Class 1, Class
> > 2.0; V32bis, V.FC, V.34+; Texas Instruments RK 33600 Chipset (as far as I
> > can tell)
> 
> I don't believe that USR sell their hardware for badge engineering in this
> way; it seems more likely that you were being treated as a non-technical
> buyer and given the name of the most popular branded modem as a reference
> (although probably the worst choice for Hylafax!)  If they really are of
> USR origin, they may be broken chipsets that USR don't want associated
> with their name!
> 
> > HylaFAX will dial out to whomever and will ALWAYS return a "Unspecified
> > Transmit Phase B error (code 20)" error.  I've tried many different fax
> 
> The full diagnosic log would be helpful; in particular, the real Sporster
> bug is very obvious from that log as garbage characters.
> 
> Note that error 20 is just the code for the textual message you quoted.
> It means that there was a problem negotiating the session parameters for
> which there is not a more specific message.  It could originate from
> Hylafax or the modem; the log is needed to distinguish.
>