Here is what I see right after booting and the HB starts.
repeater@node60632:~ $ cat /var/log/asterisk/messages.log
[2024-07-04 10:19:01.938] Asterisk 20.8.1+asl3-3.0.0-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2024-06-13 23:09:36 UTC
[2024-07-04 10:19:01.977] NOTICE[952] loader.c: 70 modules will be loaded.
[2024-07-04 10:19:02.187] NOTICE[952] cdr.c: CDR simple logging enabled.
[2024-07-04 10:19:02.189] NOTICE[952] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
[2024-07-04 10:19:02.208] NOTICE[952] indications.c: Default country for indication tones: us
[2024-07-04 10:19:02.208] NOTICE[952] indications.c: Setting default indication country to ‘us’
[2024-07-04 10:19:02.291] NOTICE[952] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[2024-07-04 10:19:02.303] WARNING[952] chan_dahdi.c: Only FXO signalled channels may belong to a call group
[2024-07-04 10:19:02.303] WARNING[952] chan_dahdi.c: Only FXO signalled channels may belong to a pickup group
[2024-07-04 10:19:02.303] NOTICE[952] chan_dahdi.c: Ignoring any changes to ‘userbase’ (on reload) at line 23.
[2024-07-04 10:19:02.303] NOTICE[952] chan_dahdi.c: Ignoring any changes to ‘vmsecret’ (on reload) at line 31.
[2024-07-04 10:19:02.303] NOTICE[952] chan_dahdi.c: Ignoring any changes to ‘hassip’ (on reload) at line 35.
[2024-07-04 10:19:02.303] NOTICE[952] chan_dahdi.c: Ignoring any changes to ‘hasiax’ (on reload) at line 39.
[2024-07-04 10:19:02.303] NOTICE[952] chan_dahdi.c: Ignoring any changes to ‘hasmanager’ (on reload) at line 47.
[2024-07-04 10:19:02.303] WARNING[952] chan_dahdi.c: Only FXO signalled channels may belong to a call group
[2024-07-04 10:19:02.303] WARNING[952] chan_dahdi.c: Only FXO signalled channels may belong to a pickup group
[2024-07-04 10:19:02.500] WARNING[952] loader.c: Module ‘res_adsi’ has been loaded but may be removed in a future release.
[2024-07-04 10:19:02.595] NOTICE[1032] app_rpt.c: Normal Repeater Init 60632
[2024-07-04 10:19:02.598] NOTICE[1036] chan_simpleusb.c: Channel 60632: Set option TONE VERIFY, mode: OFF(0).
repeater@node60632:~$
Using Allmon3 “Show Node Status”, Allmon hangs with this flashing dot, and the HB stops.
So I got ambitious and installed the latest Supermon 7.4+
Pity. In version 1 and earlier even back to ACID it worked great, just the audio was a problem. I’m not a programmer so not able to really figure it out. HamVoIP uses hamlib but you cannot direct enter a frequency. Thanks for letting me know, I’ll stop beating my head against the wall…
Please include what you are trying to do, what’s worked in the past (even on other/earlier systems), and any configuration files (working and not). Note: to upload .conf files to GitHub you may need to add a “.txt” extension to the file.
If nothing else, this will document that a problem exists.
After all the problems I encountered trying to make ASL3 work, I’m posting the solution so others do not have the same bad experience.
I was discouraged and set the project aside for a week.
I used my second set of identical hardware and it worked perfectly. I even installed Supermon 7.4+. The whole process took less than an hour. Later I did the first set of hardware again and it also worked perfectly.
The solution is after the first RPi boot, WAIT, WAIT, WAIT!!!
The PTT light will go on and off, the COM light will come on, the HB light will start flashing, you can bring up the Launch Pad web page and log in to the Web Admin Portal. DON’T!!!
WAIT, WAIT, WAIT about 5 minutes until all the disc activity has stopped.
This was my solution found by accident.
Even if you can ping the node, view the Launch Pad, log into the Web Admin Portal, DON’T!!! For some reason this was repeatedly corrupting my installs.
I think this needs to be emphasized in the User Guide.
I absolutely love ASL3. Its was so simple to setup and I really like the Raspberry Pi imager. The landing pad is vary nice and useful.
I run a small private network made up of 6 repeaters. Only about 75 users. I am converting it to ASL3. I am setup the backup pi server. Main server is a Google cloud. I got everything working except peers.
I use “iax2 show peers” to grab ip address and port for users nodes. I parse the data and create the user database. ASL3 does not show ip or port anymore. It just says null, what am I missing? I have made sure the “calltokenoptional” is un-commented. Is this because of the new Asterisk security? Is there a way around it. I always run under sudo -s.
I have setup peers for Asl3 just like I did for Asl2. If “iax2 show peers” will not show ip address and ports, like it does for Asl2, I will have to rewite the server code. I was trying to avoid this. Is there a reason why Asl3 does not show ip and port for peer?
I added the line to the peers. It did not seam to change anything, but I left them for good measure. Thanks for responding. It was all me, I did not read the instructions! I am so use to working with cloud servers, I never thought it would be the pi firewall, but it was.
