Re: [hylafax-users] T.30 T2 timeout, expected page not received

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Disaster wrote:

> On Thu, 2007-04-12 at 10:18 -0700, Lee Howard wrote:
>
>  
>
> > There is a long-standing issue with the Lucent/Agere chipset that causes 
> > the subsequent AT+FRH=3, CONNECT, NO CARRIER problem: AT+FRH=3 will 
> > report CONNECT during V.29, V.17, or V.27ter modulation when it really 
> > shouldn't - it should only report CONNECT when hearing V.21 HDLC.  
> > However, knowing this, and then observing the timeout following AT+FRS=7 
> > we can plainly see that there really was some kind of audio going on at 
> > that time.
> >    
> Is there any way of increasing this timeout?
>  

I assume that you mean the timeout following AT+FRS=7.  The answer is 
no, not without changing the code.  But it wouldn't likely do you any 
good, anyway.  What HylaFAX is trying to do there is it's trying to wait 
for silence before transmitting CRP.  Inevitably if you increased the 
timeout long enough for it to actually result with OK - then HylaFAX 
would be transmitting CRP at the same time that the sender is 
transmitting the post-page or partial-page signal.  And you'd end up 
with yet another mess.

I think that the "right" thing to do here is for Agere to fix the 
AT+FRH=3 Class 1 bug that I've described.  I've seen it affect more 
software than just HylaFAX.  However, I'm strongly considering 
implementing a workaround into HylaFAX... something that would tell 
HylaFAX to treat AT+FRH=3/CONNECT/NO CARRIER the same as +FCERROR.

> > An audio recording of the call would be very helpful to confirm these 
> > suspicions... although it probably wouldn't help us solve any problem.
> >    
> Uhm, I have absolutely no idea on how to record the call! :-) but if you
> tell me how to do this I'll try.
>  

It takes the right equipment.  It was just wishful thinking on my part.  :-)

> > There may be some kind of audio disturbance from your PBX or your 
> > telephone company or the lines involved that is corrupting the V.29 
> > audio enough to make the modem not be able to detect it.  If not that, 
> > then the modem erred in not detecting it, and that - compounded by the 
> > AT+FRH=3 problem, makes the session fail.
> >
> > Can you get a corresponding session log from the sender?
> >    
> Dear Lee,
> many thanks for your reply.
> I'm unable to get the session log from the sender, I've already asked to
> them but they say that their fax server is old, and that there's no way
> to have the session logs.
> The problem is that I'm experiencing problem only with them (I receive
> 100 faxes a day and send about 60)and they don't have any problem with
> any other client.
> If of any help, they told me that the limit the speed to the fixed speed
> of 9600 (for maximum compatibility :-| )
>  

If you were using Caller*ID then you could use DynamicConfig to, 
perhaps, alter your DIS presentation in a way to this specific sender 
that would avoid the matter.

> I really hope that there is a way of fixing this as the only other
> solution is to switch this line back to zetafax :-(

Well, in my opinion that would be a mistake, but you should do whatever 
is in your best interests.  As for my recommendation, I would suggest to 
ask the sender to use V.17 when sending to you.  If they cannot, then I 
would recommend that you look for a firmware fix from the modem 
manufacturer for the Agere problem or that you hold out for a workaround 
to appear in HylaFAX+.

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