Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!hsdndev!wuarchive!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: stanley@phoenix.com (John Stanley)
Newsgroups: comp.dcom.telecom
Subject: Re: COCOT's on the Corner
Message-ID: <15645@accuvax.nwu.edu>
Date: 20 Dec 90 19:30:24 GMT
Sender: news@accuvax.nwu.edu
Organization: One Man Brand
Lines: 19
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 901, Message 12 of 12


motcid!segal@uunet.uu.net (Gary Segal) writes:

> stanley@phoenix.com (John Stanley) writes:

> But did Mr. Stanley experience a case of COCOTery gone bonkers, or did
> the phone get bitten by it's proximity to someone's transmitter?  I'd
> love to blame the COCOT too, but don't forget that there could be
> something else wrong outside of the phone.

   I live about 100' from this phone. The only transmitters in this
area are mine (not a country music broadcast, and not on at the time
anyway) and a paging service. The closest broadcast stations are
several miles away. I guess it is probably a crossed wire in the telco
service, or something in the phone acting as a receiver.

   The point was that there was no way outside calling the operator to
report the problem, and she had no idea where I was calling from.