Hello to the group,
I would like to install ASL3 on a Ras Pi 4 already running WPSD. WPSD is running Trixie.
If anyone has a start point for me that would be great.
Thanks, David KE6UPI
You can try a stock Debian install:
However given that WPSD is an appliance and managed holistically as one, you'll likely have a struggles unless you're a Linux expert.
Thanks Jason for the reply.
I get an error doing the Debain Install.
root@wpsd-900:/tmp# apt install asl3
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
Unsatisfied dependencies:
asl3 : Depends: asl3-asterisk but it is not installable
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
- asl3:armhf=3.11-1.deb13 is selected for install
- asl3:armhf Depends asl3-asterisk
but none of the choices are installable:
[no choices]
Oh, WPSD is still based on the old armhf 32-bit platform. In that case, unfortunately, they aren't compatible.
Thanks for the discussion. I was considering a similar situation. I have several Pi’s with a Raspberry Pi screen, that I would like to use. Is the video supported in ASL3? alternately If I install the standard Pi OS, is ASL3 then compatible?
The ASL3 Appliance image is just the normal OS with the ASL3 stuff packaged in automatically. Anything that works on a normal system will work with the ASL3 Appliance image - that was the whole point. The one thing is it's aarch64 and not armhf.
Thank you very much.
But that now means I have yet another project on the workbench. Merry Christmas.
Its the latest Trixie but I wouldnt recommend mixing it with ASL3
pi-star@wpsd:~ $ uname -m
aarch64
Thanks Jason, I had installed once before using the apt-get install command on a Raspberry Pi. I just can’t remember if it was Pi-Star, WPSD or something esle.
Thanks for the support.
David KE6UPI
I have been unable to successfully build and install ASL3 from source on a Raspberry Pi. Although the system does boot when compiled this way, the resulting Asterisk implementation exhibits very poor audio quality (“poppy” / distorted audio). In contrast, the official Raspberry Pi appliance image from the ASL website works perfectly — audio is clean, and everything functions as expected.
In other words:
-
Building from source with the phreaknet script results in an Asterisk build that runs, but with bad audio.
-
Using the provided .img / appliance image from the official site produces a stable, working node with correct audio behavior.
It seems that compiling ASL3 on RPi via source/phreaknet does not produce the same binaries as the prebuilt image, so it’s not a viable option for a working node.
It is correct in that a custom compile will definitely not result in the same binaries as the official packages. But that is by design. It does, in general, work though. Someone with more customization build experience would need to chime in on possible issues.
Correct. We do not use phreaknet to build the binaries included in the packages.
Have you seen :
After spending a week building app_rpt from source using multiple approaches and deploying it on top of a system created from the official image, I can state with certainty that this is not related to system-level tweaks, configuration, or build options. The issue is that different code is being used in these two cases. There is, to put it mildly, no rational explanation for this discrepancy.
Are you bulilding the source from a release tag? And are you using the same asterisk version as that release was shipped with? Release 3.7.1 · AllStarLink/app_rpt · GitHub is the latest relast against Asterisk 22.5. Things in-between release tags may not be stable.
This command will fetch, build, and install current ASL3. You'll need to clone the AllStarLink/asl-asterisk package, but that should be all you need other than configs and dahdi.
time ./build-asl3 -a 22.7.0 -v 3.7.1 -r 1 source build install |& tee build.out
PS: build time on RPi 4 should be 30-40 minutes from scratch.
Hello Chuck
I'm running the last WSPD image (Trixie OS aarch64 and FS amrhf) on a RPI 3 Model B+.
Because of this, I compiled asl3 by using "your command" ./build-asl3 . I choided 22.7.0 and 3.7.1 despite currently verions are 22.9.0 and 3.9.0 (Septembre 26). Yes, previosly I had to install some libbluethoot3 and libasound2 dependencies. Compilation took almost 3h to succeed.
After that, I moved to ../asterisk subfolder. I executed
sudo ./configure
sudo make samples
Then I proceed with sudo /usr/sbin/asterisk -f
I got a larger number of ERROR load_modules for a large number of modules with "declined to load" messages.
May you provide a little bit of guidance to fix it up?
73 de EA3FRB
Sadly, @Chuck is now a SK 
The current ASL3 packages are based on asterisk 2.9.0 and app_rpt 3.9.3 ... and 22.10.1 / 3.10.5 will be out soon.
Using the asl3-asterisk repo's build-asl3 command is still the recommended path to pull together the pieces.
For more info on building / packaging, check out asl3-asterisk / docs / build-asl3.1.md.
Did you move to the ../asterisk directory? or the ../asl3-asterisk-xx.xx.x+asl3-x.xx.x directory? The former has a copy of the "asterisk" source code repository, the latter is the merged/patched sources.
Please keep in mind that our focus remains on Debian OS 64-bit (aarch64) systems.
Hello Allan.
I didn't know about SK. My condolences.
I moved from the "former" Asterisk directory.
Tomorrow I am going to clean the 22.7.0 / 3.7.1 and I will try a new compilation by using 22.9.0 and 3.9.0
After that, I will move to asl3-asterisk-22.9.0+asl3-3.9.0 ant then sudo ./configure + sudo make samples.
Do it has sense to you?
Any additional advice?
BR.
Jaume
I would skip 22.7.0/3.7.1 and minimally start with asterisk 22.9.0 + app_rpt 3.9.3.
If you use ./build-asl3 source build you should have no need to exec "./configure" because that would have already been exec'd as part of the build process. Just make sure that you are in the merged directory.
Hello Allan.
I executed sudo ./build-asl3 -a 22.9.0 -v 3.9.0 -r 1 source build install . As far as I can see, it was completed with no errors.
pi-star@ea3frb5:~/asl3-asterisk $ sudo asterisk -rvvv
Unable to open specified master config file '/etc/asterisk/asterisk.conf', using built-in defaults
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
pi-star@ea3frb5:~/asl3-asterisk $ sudo ls -ltr /var/run/asterisk/
total 0
I take a look at /etc/asterisk which is empty and asterisk.ctl doesn't exist.
Do I miss something for the build process?
73 de EA3FRB