[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hylafax
Subject:    Re: [hylafax-users] Faxing over IAX getting wedged/failing 50% of the time
From:       Federico Heinz <fheinz () gmail ! com>
Date:       2012-03-30 15:59:23
Message-ID: CAOSGdKGt9rGTYeRhigr1r6jtH7qoux3krgzAzQh+YjRwc3QkDA () mail ! gmail ! com
[Download RAW message or body]

On Thu, Mar 29, 2012 at 12:09 PM, Federico Heinz <fheinz@gmail.com> wrote:

> [...] The final log file for all of them finishes with, for instance:
>
> Mar 14 15:46:19.85: [28797]: Failure to receive silence (synchronization
>> failure). {E100}
>> Mar 14 15:46:19.85: [28797]: <-- data [1]
>> Mar 14 15:46:20.25: [28797]: MODEM <Empty line>
>> Mar 14 15:46:20.25: [28797]: <-- [9:AT+FTH=3\r]
>> Mar 14 15:46:27.80: [28797]: SEND FAILED: JOB 3118 DEST XXXXXXXXXX ERR
>> Unspecified Transmit Phase C error {E149}; too many attempts to dial
>> Mar 14 15:46:28.81: [28797]: <-- [5:ATH0\r]
>> Mar 14 15:46:33.83: [28797]: SESSION END
>
>
> However, the converse is not true: not all transmissions that ended this
> same error caused the modem to die afterwards, most such errors did not
> result in any disruption, so my guess is that there must be something more
> going on here.
>

And it just did it again, for another fax. For some reason, faxgetty
sometimes crashes after this kind of error. Unfortunately, it doesn't seem
to leave any evidence of why crashed.

Is there any additional logging I can turn on to track this down?

[Attachment #3 (text/html)]

On Thu, Mar 29, 2012 at 12:09 PM, Federico Heinz <span dir="ltr">&lt;<a \
href="mailto:fheinz@gmail.com">fheinz@gmail.com</a>&gt;</span> wrote:<div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <div \
class="gmail_quote"><div>[...] The final log file for all of them finishes with, for \
instance:</div> <div><br></div><blockquote class="gmail_quote" \
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left \
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">


Mar 14 15:46:19.85: [28797]: Failure to receive silence (synchronization failure). \
{E100}<br>Mar 14 15:46:19.85: [28797]: &lt;-- data [1]<br>Mar 14 15:46:20.25: \
[28797]: MODEM &lt;Empty line&gt;<br>Mar 14 15:46:20.25: [28797]: &lt;-- \
[9:AT+FTH=3\r]<br>

Mar 14 15:46:27.80: [28797]: SEND FAILED: JOB 3118 DEST XXXXXXXXXX ERR Unspecified \
Transmit Phase C error {E149}; too many attempts to dial<br>Mar 14 15:46:28.81: \
[28797]: &lt;-- [5:ATH0\r]<br>Mar 14 15:46:33.83: [28797]: SESSION END</blockquote>

<div><br></div><div>However, the converse is not true: not all transmissions that \
ended this same error caused the modem to die afterwards, most such errors did not \
result in any disruption, so my guess is that there must be something more going on \
here.</div> </div></blockquote><div><br></div><div>And it just did it again, for \
another fax. For some reason, faxgetty sometimes crashes after this kind of error. \
Unfortunately, it doesn&#39;t seem to leave any evidence of why crashed.</div> \
<div><br></div><div>Is there any additional logging I can turn on to track this \
down?</div><div> </div></div>


____________________ 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@ifax.com.*


[prev in list] [next in list] [prev in thread] [next in thread]