Dear Osmocom community,
while many people with a long history in FOSS development have no issues
at all with mailing lists as primary form of engaging with their
community, they have undoubtedly fallen out of fashion in favor of
various chat/messaging systems or web based forums.
In Osmocom, we've just launched an installation of the discourse forum
software available at https://discourse.osmocom.org/ providing an
alternative to our traditional mailing lists at https://lists.osmocom.org/
We're looking forward to see whether this web-based approach will
facilitate more and/or other people to engage with the Osmocom
developer/contributor community.
Feel free to join and get the discussions started. If there's a need
for more categories or sub-categories, just let one of the moderators
know and we can help with that.
The old mailing lists will continue to remain available for those who
prefer them.
--
- Harald Welte <laforge(a)osmocom.org> https://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi all,
Vintage Computing Festival Berlin 2022 is scheduled for October 8+9, 2022
It would be great to put together an exhibit there, re-using the small
rack based setup that was at the 2019 CCC congress (Auerswald PBX,
Freeswitch, Portmaster3) as well as a number of modems / ISDN-TA etc. to
show BBS dial-up and the like.
I have all the equipment and can work on the preparation/setup, but I
think it would be very helpful if this was not a one-man show but if
somebody would be around to help particularly on-site when there are
visitors looking for demo, explanation, help, ...
Registration deadline is September 7, as indicated at
https://vcfb.de/2022/call_for_participation.htm
Before we go into what we could/should demo, I would like to get a
feeling if anyone is interested in helping out.
Related redmine issue: https://osmocom.org/issues/5590
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi!
Has anyone tried fiddling around with sl-modemd yet?
(https://web.archive.org/web/20071014010737/http://linmodems.technion.ac.il/…
<https://web.archive.org/web/20071014010737/http://linmodems.technion.ac.il/…>)
I know, it's not free and uses binary blobs for the DSP part, but it's a
full-fledged V.90 softmodem.
Theoretically shouldn't it be possible to modify the sources to not use
ALSA for communicating with the AC97 "modem" hardware but to use an
Asterisk channel instead?
I have fiddled around with asterisk-softmodem for quite some time now,
(that's how I stumbled upon this mailing list while googling) and just
can't get it to work properly.
My intentions were the same, being able to provide a couple of analog
phone lines on vintage computing events for dialup to BBSes or PPP
Internet access. I was pleased to find someone else apparently had the
same idea :)
Regards
David Lutz
(Twitter: @kpanic)
Hello,
yesterday we (myself and Guido Flandero/KHS9NE) have released "A Voip
Wardialer for the phreaking of 2020
"https://github.com/x25today/voipwardialer .
<https://github.com/x25today/voipwardialer>
The main goal of the project is to have a fully working software-only
VoIP-Modem that can be used for wardialing, dialing a favorite BBS
running on Landline number and more.
The design is a bit "creative" but it's done a way to make the "Software
DSP" issue pluggable and remote (now Asterisk-Softmodem connected to a
local asterisk).
It's a Python PJSIP application that call the target phone number via a
VoIP provider, then call the local asterisk with Asterisk-Softmodem is
running, then provide a Terminal.
All this flow is working as MVP, would you enjoy playing with it with
the many improvements needed
https://github.com/x25today/voipwardialer/issues :)
-naif
Dear all,
it was a lot of last-minute stress, but in the end I was able to present a very
well working dial-up setup at 36C3. You can find more information about what
was presented at
* Summary news post: https://osmocom.org/news/121
* 36C3 wiki page: https://osmocom.org/projects/retro-bbs/wiki/36C3
* https://osmocom.org/projects/retro-bbs/wiki/Dialup_Network_In_A_Box
Contrary to earlier plans, the main focus in this first installation was the
physical / telephony setup, and we didn't actualyl operate any BBSs on-site
but merely terminated Modem calls in the Portmaster and forwarded those via
telnet to remote (public and 36C3 specific) BBS installations.
But now as that is working, the setup will remain the same and I can try to
spend some more time on software / protocols. I still want to run at least
one Synchronet and one Mystic BBS in Linux containers, as well as one Zerberus
instance in a qemu-kvm. The related containers/VMs exist, but need to be
connected with the outside world and fully configured. At future events I
then hope to be able to demo ZConnect and FTN style networks, with a QWK
reader and CrossPoint on the client/PC side.
As empty BBSs are of course quite boring, it would be good to get at
least one of them set up rather soon and then start to actually fill it
with messages. One idea would be to gate the osmocom.org mailing lists,
but of course one can also join at least some of those FTN networks that
still exist today, which should at least fill some message areas over
time.
If anyone wants to help out, help is - as always - much appreciated. I
can host some VMs/containers on public IP addresses, as needed.
The main two areas requiring help are, AFAICT:
* set-up of several BBSs, including connectivity to FTN networks
* set-up and test of QWK and point software
* improved qemu/telnet integration (https://osmocom.org/issues/4341)
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
