Re: Clean North Fax is NOT DOWN

[Dan Brosemer <odin@cleannorth.org>]

On Wed, Jun 14, 2006 at 04:24:56PM +0000, Don McGorman wrote:
> Folks:
> 
> So we have narrowed the problem down to that there is at least one fax 
> machine (946-2112) that has somehow developed a problem communicating with 
> the CN fax (and apparently has no known problem communicating with any 
> other fax).
> 
> There may be other fax machines out there that have an issue with CN.  So,  
> if you are expecting a fax at the CN office and it does not arrive, do not 
> assume that the person never tried to send it.
> 
> If you ever find another fax that will not communicate with CN, please 
> report it.  Thanks.

Here are all the times ever we've seen this error:

c00000381:Sep 21 09:25:58.47 7059459958
c00000382:Sep 21 09:31:23.83 7059459958

Received many faxes from this machine later up to and including March 30.
It hasn't tried to send a fax since March 30.

c00000400:Oct 03 15:10:08.22 Fax
c00000402:Oct 03 15:17:29.36 Fax
c00000403:Oct 03 15:21:41.49 Fax
c00000404:Oct 03 15:25:53.52 Fax
c00000405:Oct 03 15:29:02.53 Fax
c00000406:Oct 03 15:36:19.37 Fax
c00000407:Oct 03 15:40:03.76 Fax

Generic FTI, can't check for other attempts

c00000480:Jan 20 18:51:31.77

No FTI, can't check for other attempts

c00000552:May 15 17:46:54.35 7057853220

Received this fax on a later attempt

c00000561:May 29 02:12:21.25 Gov Pol Res Gp
c00000562:May 29 02:24:20.97 Gov Pol Res Gp

Never made another attempt

c00000566:Jun 08 11:33:09.44 705 946 2112
c00000567:Jun 08 11:36:06.80 705 946 2112
c00000573:Jun 09 10:50:34.91 705 946 2112
c00000576:Jun 11 09:49:31.87 705 946 2112
c00000577:Jun 11 09:53:24.51 705 946 2112
c00000578:Jun 11 09:57:33.61 705 946 2112
c00000579:Jun 11 10:01:22.53 705 946 2112
c00000580:Jun 12 11:05:05.43 705 946 2112

Last correctly received from this FTI on March 23.

Documentation on this error says:

>This error is easily possible under noisy line conditions or similar
>communication problems.  If the problem is reproducible then contact
>Multi-Tech.  You might also get the sender to lower the signalling
>rate or constrain it on your end using Class2DCCCmd or Class2DCCQueryCmd
>(though you won't want to do this for all calls, just for a test)

Therefore, there's a signal problem.  It's not impossible that this is
partially due to the fact we moved the machine receiving faxes off the rack
and chained it off the outgoing fax machine.  It's certainly not CN's lines
only, though, as OFRI's fax is the only one to generate these errors this
month.  Clearly there are less than desirable line conditions on both sides
for this to occur.

I'll keep a close eye on it and pay attention if any of these errors are
generated from a different FTI.

Don, when we move the incoming back in to the server rack and use the other
line, I'll ask you to test again from OFRI.

Once again, Don, the sky is not falling.  We have logs of everything that
goes on, and I hope I demonstrated here that if you don't receive a fax you
expect, it's far, far, far more likely that the other end never sent it than
a transmission error.

-Dan

-- 
"Burnished gallows set with red
 Caress the fevered, empty mind
 Of man who hangs bloodied and blind
 To reach for wisdom, not for bread."  -- Deoridhe Grimsdaughter