There are two providers of the AllStar System:
Both offerings are build on Asterisk.org., an
open source communications project that lets you create telephony apps for
IP PBXs, VoIP Gateways.
The most common build is on the Raspberry Pi, RPi3. The Allstarlink distribution is built on the Raspberian OS and Hamvoip is built on Archlinux OS.
_ _ _____ _ _ _ _ /\ | | |/ ____| | | | (_) | | / \ | | | (___ | |_ __ _ _ __ | | _ _ __ | | __ / /\ \ | | |\___ \| __|/ _` | '__| | | | | '_ \| |/ / / ____ \| | |____) | |_| (_| | | | |____| | | | | < /_/ \_\_|_|_____/ \__|\__,_|_| |______|_|_| |_|_|\_\The AllStar Home Page is here: (You can login form this page) https://web-tpa.allstarlink.org/
In order to become a member of the AllStar Link Network, you must first
Register to become user of the Portal system. To qualify for membership,
you must be a holder
of a valid Amateur Radio license.
A URI or RIM (Radio Interface Module) is required. I purchased the Repeater Builder RIM-Lite, Repeater Builders's RB-RIM-Lite (local) An interface can be constructed using a cheap USB sound FOB. Search the internet for conversion instructions.
Wifi and DHCP are enabled by default and the RPi will attempt to obtain a IP lease.
Secure Shell was not enabled by default.
Try ssh firstname.lastname@example.org
Login: repeater Passsword: allstarlink # The is the default password On first login you will be requested to reset the password for the "repeater" account SSH port: 22 User repeater has sudo privileges (sudo -s)
There may have been updates to the operating system and AllStarLink since this image was built.
Because we use the ADPCM (g726aal2) codec in Asterisk, each connection from/to a remote node will require about 55 kilobits/sec (at the IP packet level) of bandwidth in both directions. The frequency response when ADPCM is used will be very close to telephone voice grade (telephone voice grade is defined as 3db points at 300-3400Hz, 1000Hz 0db reference). Yes. Due to the fact that the system is TDM (Time Domain Multiplexed
) and there is overhead involved to perform DSP functions in Asterisk, there is audio delay for both local connections and there is additional audio delay from connections made over the Internet.
Active simpleusb stanza: [usb] USB device String: 1-1.1.3:1.0 Card is: 0 Name is: usb Rx Level: 500 Rx no-delay: 0 Rx audio-delay: 0 Tx A Level: 700 Tx B Level: 700 preemphasis: no deemphasis: no plfilter: no dcsfilter: no rxboost: no PTT: Active LOW PTT status: Un-Keyed CTCSS (input): Ignored COS (input): CM108/CM119 Active LOW COS (test): Un-Keyed COS (composite): Un-Keyed
Incoming connections are made from any Echolink node in the usual manner. An app_rpt user dials an additional prefix digit in the connect command to distinguish between Allstar (2), Echolink (3) node numbers.
I changed my duplex setting in the rpt.conf file and now that I'm transmitting
telemetry and courtesy tones I am back on the map. Switching off the telemetry
is how I fixed the chasing the tail problem. The docs say that it shouldn't
matter if I dont advertise my node people should still be able to connect but
now no one can connect and I am not on the map at
To check you have no registration issues you do a check_reg.sh from the bash prompt.
To check you have a route to the node you are wishing to contact you do "dns-query <node>"