The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Harasing whistlers (Was: UUCP mis-history?)
Date: Thu, 9 Mar 2017 17:54:26 -0500	[thread overview]
Message-ID: <a288af47-2f61-467b-f6e2-344a37149de9@kilonet.net> (raw)
In-Reply-To: <alpine.BSF.2.20.1703100825520.2854@aneurin.horsfall.org>

Or it THOUGHT it heard a tone - some people's voices could trigger it.

Or the actual bells still ringing for a short period of time after you 
picked up the handset even.

Some of the acoustic couplers I played around with would start signing 
when people were talking in the same room, or certain music was playing.

I did a lot of work with 300 (103 standard) and 1200 baud modems (both 
202 and 212 standard), and some of them were very quirky. I'm trying to 
remember if the 202 initiated any tones on the originating side, but I 
can't remember.

The 202 standard is still in use to transmit caller ID on phone lines 
between the 1st and 2nd rings.

Also, if they were used for dial-back, they could have been set to 
originate.



On 3/9/2017 4:29 PM, Dave Horsfall wrote:
> On Thu, 9 Mar 2017, Noel Chiappa wrote:
>
>> Interesting: I've heard this same story, but told about TIPs and the
>> ARPANET. A computer at BBN was set up to regularly dial all the TIP
>> modem lines, to check that they were working. One line was always down,
>> so they listened in, and heard some human say "it's just that pevert
>> with the whistle again".
>>
>> I wonder which one was the original: anyone know for sure?
> Now that takes me back; urban myth, because the calling modem didn't
> squeak until the called modem did.
>



  reply	other threads:[~2017-03-09 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 15:06 Noel Chiappa
2017-03-09 16:31 ` Ron Natalie
2017-03-09 21:29 ` Dave Horsfall
2017-03-09 22:54   ` Arthur Krewat [this message]
2017-03-10  0:31   ` Jason Stevens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a288af47-2f61-467b-f6e2-344a37149de9@kilonet.net \
    --to=krewat@kilonet.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).