From: Kevin Bowling <kevin.bowling@kev009.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Known Specimens of Pre-5ESS UNIX Telephone Switching Software?
Date: Mon, 25 Sep 2023 19:20:54 -0700 [thread overview]
Message-ID: <CAK7dMtCFj-TqP_FnEg5LmASiiCm_hm6PwoMxZBquUV1kBWnR4w@mail.gmail.com> (raw)
In-Reply-To: <E-OYSKkB0M31Co1IajKVcPWjRwihVSSg_YrjKrVrsPdHdaUWOM4vnu0PpqncYVEO2bCuylKXUfqFJ0122l3ZmqoEmBHab5l3frfAVYwydu4=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]
On Mon, Sep 25, 2023 at 6:25 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
> Hello, my studies lately bring me to the question: Are there any extant
> examples of telephone switching software, built on UNIX, from the various
> parts of the Bell System prior to the introduction of the 5ESS and 3B20D?
> My focus veers earlier as some 5ESS/3B20D/DMERT technology is still in
> active use, that sleeping dragon can lie.
>
Your best bet may be to contact Sarah Autumn at the Connections Museum,
they have a 1ESS and 3ESS.
http://www.telcomhistory.org/connections-museum-seattle-exhibits/electronic-switching/
I don't remember if they have the 1A variant but they should have the BSPs
for all of this which would give you a lot of what you are after.
> What's gotten me curious is reading about 1ESS in a BSTJ volume I picked
> up, noting the particulars on how previous concerns of manual and
> electro-mechanical systems were abstracted into software. Even without
> surviving examples, were previous systems such as the 1ESS central control
> ever ported to or considered for porting to UNIX, or was the hardware
> interface to the telco lines too specific to consider a future swap-out
> with, say, a PDP11 running arbitrary software? Columbus's SCCS (switching,
> not source code) also comes to mind, although all I know that survives of
> that is the CB-UNIX 2.3 manual descriptions of bits and pieces.
>
> By the way, it's funny, I have UNIX to thank for my current experiments
> with telephones and other signalling stuff, what with making me study the
> Bell System more generally. It's starting to come full circle in that I
> want to take a crack at reading dialing, at least pulse, into some sort of
> software abstraction on a SBC that can, among other things, provide a
> switching service on top of a UNIX-like kernel. I don't know what I'd do
> with such a thing other than assign work conference call rooms their own
> phone numbers to dial with a telephone on a serial line...but if I can even
> get that far I'd call it a success. One less dependency on the mobile...
>
> - Matt G.
>
[-- Attachment #2: Type: text/html, Size: 2804 bytes --]
next prev parent reply other threads:[~2023-09-26 2:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 1:24 [TUHS] " segaloco via TUHS
2023-09-26 1:37 ` [TUHS] " Jon Steinhart
2023-09-27 2:46 ` Heinz Lycklama
2023-10-04 6:52 ` Kevin Bowling
2023-10-05 14:19 ` Kevin Bowling
2023-09-26 1:39 ` Jon Steinhart
2023-09-26 1:50 ` Andrew Hume
2023-09-26 2:13 ` steve jenkin
2023-09-26 11:28 ` Brad Spencer
2023-09-26 2:20 ` Kevin Bowling [this message]
2023-09-26 16:07 ` Sebastien F4GRX
2023-09-26 18:45 ` segaloco via TUHS
2023-09-26 23:32 ` George Michaelson
2023-09-27 6:15 ` Lars Brinkhoff
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=CAK7dMtCFj-TqP_FnEg5LmASiiCm_hm6PwoMxZBquUV1kBWnR4w@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=segaloco@protonmail.com \
--cc=tuhs@tuhs.org \
/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).