Skip to content

What's New?

Ready to get on with installation? We thought so, but first consider that ASL3 is very new. You'll probably want to install on removable media or on a non-production system. You probably don't want to install a production system right away. Give yourself some time to test that everything works as you'd expect.

Note: if you have installed an earlier version of ASL you need to know that ASL3 has many changes and that there's a bit of a learning curve. For those who have used ASL2 or other versions of AllStar you should be aware of a few important details:

  • At the risk of repeating ourselves, ASL3 now runs on Asterisk 20! We are no longer stuck in the past. We're so proud!!!
  • There is no update or migration path from ASL2 to ASL3
  • Many of the ASL3 configuration files are different
    • The configuration files now support templates
    • We now favor node registration using HTTP
    • The SimpleUSB and USBRadio tune settings have been moved into their respective (.conf) configuration files. We no longer have separate per-node tune setting files.
  • EchoLink changes
    • EchoLink chat has been enabled
    • EchoLink now honors the app_rpt timeout timer. A text message is sent to the client when they time out.
    • EchoLink longer allows clients to double. A text message is sent to the client when they are doubling.

The two node numbers per user policy remains in effect. Node numbers are a limited resource. Please make a best effort to use new media, a new server, or NNX to build a node for testing. We do make exceptions on a case by case basis but we'd really appreciate it if you could use a resource you already have.

The ASL3 menu has been updated. Our goal is to provide an easy way for you to configure your node and to minimize the need to edit any configuration files.

At the same time, we have removed most of the "OS" configuration options found in earlier implementations. Historically, ASL has been installed on many OS variants and the OS commands that work on one version do not always work on others. For that reason there are no OS related commands in the ASL3 menu.

See Menu for details.

Configuration Changes

The first thing to know about ASL3 configuration is that the menu can be used to make and view common changes. Here are the highlights. You may want to read about Advanced Topics and New Commands details later.

  • You may edit the conf files without concern of switching between editing and using the menu. The tune menus are removing leading white space from comments (we're hoping to fix this).
  • An Asterisk template is now used within rpt.conf, simpleusb.conf, and usbradio.conf. Editing is much easier but it's different than with other versions of AllStar. Node settings are much simpler with only a few lines needed to be added/updated for each node. The ASL3 menu handles the new templated configuration.
  • AllStar registration is now set in rpt_http_registration.conf, not in iax.conf. IAX registration still works but is discouraged. Please do not configure your node for both HTTP and IAX registration. The new Asterisk CLI command to show the registration status of your nodes is rpt show registrations. This command can be performed from the ASL3 menu.
  • The USB configuration files now contain the tune settings. There is no tune file for each node as in ASL2. The tune menus and the Asterisk CLI write to the new tune setting locations.
  • There is no need to edit or use a script to update the access list, formerly known as the blacklist and whitelist. The settings are different because the access list is now per node rather than for all nodes as in other AllStar versions. It's also much easier to use the ASL3 menu to build the access lists.

A&P Measurement

Adoption and Performance measurements are to help ASL understand growth and technical aspects of ASL3. No sensitive or private information is collected. For details see GitHub/AllStarLink/ASL3-Usage. Reports are available at