search

bildschirmtext / asterisk-modem-box

A Vagrant box with Asterisk and a soft modem to connect old terminals to the BTX mainframe
MIT License
8 stars 3 forks source link

Updates to get this running in 2024 #2

Open hpingel opened 5 months ago

hpingel commented 5 months ago

Hi, I have spent a couple of hours this week to set up the asterisk-modem-box and it is running now fine. Thank you for this great project! Should I create PR's with my code changes that reflect the changes necessary in 2024?

I stuck to Debian 9 (I first tried current Debian but ended up in dependency hell) but repo URLs and other stuff has to be changed. Also, I used vagrant-libvirt instead of vbox. So, I had to do some network configuration for the bridge in libvirt so that it is a routed network and the Fritz!Box has a static route to the gateway.

Just let me know if you want PR's for this project or if this is obsolete and will be replaced soon.

stblassitude commented 5 months ago

Execllent! I didn't really have time the last couple of years to work on this, but I definitely want to pick this up again, so I would be very happy to have a PR or two!

hpingel commented 5 months ago

Created three PRs:

3

4

5

The other stuff I have is more documentation stuff about what to do to get the networking stuff running with vagrant-libvirt. For example, I don't have eth0 any more, instead I have the interface enp2s0 on Ubuntu server. This requires changes in different places: Change interface name in:

/etc/libvirt/qemu/asterisk-modem-box_default.xml
sudo systemctl restart libvirtd

This will avoid the error message:

/usr/lib/ruby/vendor_ruby/fog/libvirt/requests/compute/vm_action.rb:7:in `create': Call to virDomainCreateWithFlags failed: Unable to get index for interface eth0: No such device (Libvirt::Error)

The network interface name then also has to go into the Vagrantfile. For me it looks like: config.vm.network "public_network", bridge: 'enp2s0: DefaultNet'

Then the virtual network bridge created by vagrant-libvirt will be in modus "nat" and has to be changed to "route". Otherwise the virtual host can not be reached from other machines in the LAN except for the libvirt host. And in the Fritz!Box interface a route has to be added for the subnet of the virtual network bridge where the libvirt host is the gateway.

hpingel commented 5 months ago

And now for the fun part: The reason why I wanted to set up this project is that I got my hands on a LOEWE MultiTel-D (with thermoprinter) by coincidence. I made a little Youtube video documenting the success of accessing BTX after I also had to rewire the pinout of the telephone cable between MultiTel-D and Fritz!Box.

https://youtu.be/tX80CNtu8NU

IMG_20240502_184544