Re: [hylafax-users] Failed to properly open control V.34 channel

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2004.06.28 15:24 Kris Henderson wrote:
> Hello,
>
> Attached is a log file of an error I see about 10% of the time.  The
> log
> file was quite long (still is) but I significantly reduced the size of
> it by deleting redundant lines as marked by <snip xxx>, hopefully I
> didn't remove any useful data.

The log you sent only tells us that the remote hung up (got EOT).  It 
is possible that we got some unexpected T.31 DLE command.  In order to 
see if that's the case you'd have to have logging set like this:

TracingMask: 0x11
SessionTracing: 0xFFF

That will show us the DTE-DCE modem communications, also, and it will 
show us if we did get such a signal.  If we didn't, then the modem 
manufacturer would have to resolve the matter, most likely (and most 
likely that will fall back to the DSP code provider).

> I have also tried turning V.34 faxing of on the sending side and
> occasionally see this error: "No response to PPS repeated 3 times."

This basically means that the remote didn't respond to the post-page 
command, so we don't know what happened, it could have hung up, it 
could have missed the page, it could have .... pretty much anything you 
can think of.  So we just don't know what happened.  Now, if we can 
figure out what *did* happen, then we may be able to fix it or 
implement a workaround.

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*