Re: [hylafax-users] problems with Acorp external 56K modem [LONG]

[Lee Howard <faxguy@howardsilvan.com>]

On 2003.06.25 07:06 Daniel PATH wrote:

> we made a log with a port-capture program.
> i can send you that. (attached)

This is great.

Are you sure that this log represents a successful transmission?  At 
the end of that log I see this three times:

<< COM2   16:00:33.886  41 54 2B 46 54 48 3D 33 0D                      
AT+FTH=3.
>> COM2   16:00:33.964  0D 0A 43 4F 4E 4E 45 43 54 0D 0A                
>> ..CONNECT..
<< COM2   16:00:33.964  FF 13 2F 10 03                                  
ÿ./..
>> COM2   16:00:35.276  0D 0A 4F 4B 0D 0A                               
>> ..OK..
<< COM2   16:00:35.292  41 54 2B 46 52 48 3D 33 0D                      
AT+FRH=3.
>> COM2   16:00:35.761  0D 0A 43 4F 4E 4E 45 43 54 0D 0A                
>> ..CONNECT..
>> COM2   16:00:37.041  FF 13 80 00 6E F8 80 80 80 01 ED 66 10 03       
>> ÿ..nø.íf..
>> COM2   16:00:37.104  0D 0A 4F 4B 0D 0A                               
>> ..OK..

That's the transmitter sending EOP (FF 13 2F) and then the receiver 
responding with DIS (FF 13 80 00 6E F8 80 80 80 01).  The receiver 
should be responding with MCF instead, which would indicate success.  
Seems that this log represents failure of the same kind that HylaFAX 
gets (no valid response to EOP).

The Zeta Fax program does some interesting things, like issue 
"AT+FTM=14" (with no carriage return) just prior to TCF, and it gets a 
CONNECT message from the modem even.  That command should be invalid 
per the log's AT+FTM=? response.  Also it seems to send an invalid 1D 
RTC (00 00 00 00 00 00 00 00 00 00).

In any case, this log won't do me much good.  I can see and calculate 
the delay differences as:

Class1SendMsgDelay:    31
Class1TMConnectDelay:  32
Class1EOPWaitCmd:      "<delay:8>"

But, even with those I don't think that you'll have success, and 
they'll probably break other communications with other machines.

Better yet, could you please set (in this order in the config file):

TracingMask:    0x11
SessionTracing: 0xFFF

And then put this port capture program on the receiver (the Windows 
system) and then attempt a fax from HylaFAX to the Windows system 
again.  Then send both the session log from HylaFAX and the log from 
the port capture program.

Thanks.

Lee.

____________________ 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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*