🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #621594

Re: Video Explaining the Rotary Phone

#621594
From: hanc...
Date: Tue, 27 Mar 2018 19:25
42 lines
3452 bytes
On Tuesday, March 27, 2018 at 4:52:45 AM UTC-4, Quadibloc wrote:

> > In _1954_ ? Are you serious? How backward was the US at that time?
> > Just wondering...
> 
> While it is true that automated telephone exchanges were introduced in the 1920s, 
> I'm sure that they started in the major cities. That rural areas still used 
> operator-assisted calling for local calls up until the 1950s in some cases does 
> not strike me as too unbelievable.

While the Bell System first automated a New York City exchange
in 1922, some rural areas were converted earlier, especially by
the Independent companies.  A very tiny village needed only a
part-time operator, and it was not cost-effective to pay
someone to sit 24/7 at a switchboard to handle occasional
calls.  (Indeed, in some places, the switchboard was in
the operator's house, and she or her daughters would answer
calls while doing other house chores.)

The last Bell Telephone manual exchange, on Santa Catalina Island,
was converted in the early 1980s.  I think some Independent
exchanges held on a little longer.

The following from the NYT should be viewable by anyone:
https://timesmachine.nytimes.com/timesmachine/1922/03/12/98782373.pdf

https://timesmachine.nytimes.com/timesmachine/1922/10/08/107071271.pdf

The capital cost of dial switchgear was very expensive; manual
switchboards were far cheaper.  Further, operators could be
economically added or subtracted per the demands of service, e.g.
only one operator during overnight hours.  Dial switchgear had to
be built to handle peak loads.

Also, maintenance staff needed more training to repair dial switchgear.

Lastly, especially in the early days, dial subscribers could only
call within their own town; anything beyond that still required an
operator.

Also, unlike today, Bell believed strongly in full human backup
in case there was an automation malfunction.
Technical Details
Message-ID: <1163a11a-cdaa-430b-830a-c187440b89a8@googlegroups.com>
Path: mbox-mo1.pugleaf.net!c39ni164qta.0!nntp.google.com!k53no152192qtc.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
References: <dbd6aa7b-c413-4403-a07d-9b932d3bc9c8@googlegroups.com> <b3cd2902-923e-4ea9-8ab6-9347c7b673c2@googlegroups.com> <0qapoe-obi.ln1@news.informatik.uni-stuttgart.de> <7ef8b115-130f-42f2-9616-fc0322df097d@googlegroups.com>

Show Full Headers
Complete Article Headers
X-Received: by 10.237.34.14 with SMTP id n14mr16299338qtc.21.1522178747882;        Tue, 27 Mar 2018 12:25:47 -0700 (PDT)
X-BeenThere: alt.folklore.computers@googlegroups.com
Received: by 10.200.38.97 with SMTP id v30ls1366662qtv.4.gmail; Tue, 27 Mar 2018 12:25:47 -0700 (PDT)
X-Received: by 10.200.39.111 with SMTP id h44mr30677837qth.4.1522178747151;        Tue, 27 Mar 2018 12:25:47 -0700 (PDT)
X-Received: by 10.31.173.80 with SMTP id w77mr2788753vke.13.1522178746791; Tue, 27 Mar 2018 12:25:46 -0700 (PDT)
Path: mbox-mo1.pugleaf.net!c39ni164qta.0!nntp.google.com!k53no152192qtc.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: alt.folklore.computers
Date: Tue, 27 Mar 2018 12:25:46 -0700 (PDT)
In-Reply-To: <7ef8b115-130f-42f2-9616-fc0322df097d@googlegroups.com>
Complaints-To: groups...@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=8.41.192.198; posting-account=WKyNOQkAAACNglsCZiIox1kdy9R-66KH
NNTP-Posting-Host: 8.41.192.198
References: <dbd6aa7b-c413-4403-a07d-9b932d3bc9c8@googlegroups.com> <b3cd2902-923e-4ea9-8ab6-9347c7b673c2@googlegroups.com> <0qapoe-obi.ln1@news.informatik.uni-stuttgart.de> <7ef8b115-130f-42f2-9616-fc0322df097d@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <1163a11a-cdaa-430b-830a-c187440b89a8@googlegroups.com>
Subject: Re: Video Explaining the Rotary Phone
From: hanc...@bbs.cpcn.com
Injection-Date: Tue, 27 Mar 2018 19:25:47 +0000
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit