From: steve jenkin <sjenkin@canb.auug.org.au>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Known Specimens of Pre-5ESS UNIX Telephone Switching Software?
Date: Tue, 26 Sep 2023 12:13:29 +1000 [thread overview]
Message-ID: <6985E7CD-6C8A-42E5-A58B-2533F635677F@canb.auug.org.au> (raw)
In-Reply-To: <92D94A5E-AE0F-446D-8C26-C8EF1E672230@humeweb.com>
For those playing along at home,
“Gecko” was written up.
Virtual Data Warehousing, Data Publishing and Call Detail
<https://link.springer.com/chapter/10.1007/10721056_8>
and a conference paper of the same name
<https://www.researchgate.net/publication/221629788_Virtual_Data_Warehousing_Data_Publishing_and_Call_Detail>
from
Databases in Telecommunications: International Workshop, Co-located with VLDB-99, Edinburgh, Scotland, UK, September 6th, 1999. Proceedings
<https://www.researchgate.net/publication/321558305_Databases_in_Telecommunications_International_Workshop_Co-located_with_VLDB-99_Edinburgh_Scotland_UK_September_6th_1999_Proceedings>
> On 26 Sep 2023, at 11:50, Andrew Hume <andrew@humeweb.com> wrote:
>
> i’m sure there are standing references to all this. but as i recall,
> the 5ESS was a more or less local switching system.
>
> the guts of the long distance network were embedded in the (roughly) 140 1ESS’s. they ran
> a completely separate (and substantially older) code that supported things like SS7 (signaling code
> that was NOT embedded in the voice channel). the 1ESS was a complex piece of equipment.
>
> my interaction with this was tangential. throughout the 1980-90s, i had a tight grip on how
> accounting messages were handled within AT&T and wrote some C code that handled a
> a transition from one level of the standard software to another level. and that code ran inside
> the 1ESS.
>
> but this was a long time ago.
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
next prev parent reply other threads:[~2023-09-26 2:13 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 [this message]
2023-09-26 11:28 ` Brad Spencer
2023-09-26 2:20 ` Kevin Bowling
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=6985E7CD-6C8A-42E5-A58B-2533F635677F@canb.auug.org.au \
--to=sjenkin@canb.auug.org.au \
--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).