![]() |
Hrmm, well i'm turning up session tracing to see what's happening. Any idea as to what setting i can set? I don't see it just looking. On Thu, Jun 21, 2001 at 09:55:37PM -0600 or thereabouts, Lee Howard wrote: > At 08:29 PM 6/21/01 -0700, will@lashell.net wrote: > > > >Nope you aren't incorrect in that the fax is there, BUT, the sending fax > >machine says its not completed and continues to retry the send. and > Successfully > >sends it, again, and again, and again... etc > > Well, your SessionTracing isn't turned up high enough for us to see the > HDLC frames to confirm this, but your log *does* say that you sent message > confirmation. > > Jun 21 19:05:13.20: [11868]: RECV recv EOP (no more pages or documents) > Jun 21 19:05:13.20: [11868]: --> [2:OK] > Jun 21 19:05:13.20: [11868]: RECV send MCF (message confirmation) > > Now, it is possible, and we have seen it before, that this EOP thing > happens so fast that some fax machines aren't paying attention when EOP or > MCF comes. Slowing MCF down may be advantageous here. I believe that > there is a config setting to do that here. But frankly, the problem here > is with the sender not listening in when he should be. We can accomodate > for that flaw, but maybe the question is, "should we?" > > Lee. > > > > ____________________ HylaFAX(tm) Users Mailing List _______________________ > To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null -- ----------------------------------------------- "Doh.. STUPID STUPID STUPID" --an excerpt taken from every developers cvs commit message at some point ----------------------------------------------- ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null