The AllStar client software includes a rich set of configuration options which are generally exposed in the various “conf” files. Since ClearNode is intended as a compact personal node, we try to bring the most relevant options up to the mobile applications. As time goes by we try to satisfy end user requests for more options, so you will see this list of Node Setup items expand.
Node Setup Screen
Tap into the Node Detail screen for your node, scroll to the bottom and tap “AllStar Setup”. This will bring up the “Node Setup” screen with a long list of configuration options broken up into sections.
You may “long press” on any item title to activate a dialog with a brief description of the option.
Node Setup screen Toolbar
The title of the toolbar will change depending on which version of the node’s setup it is displaying. A new node that has not been configured will display a default set of configuration items pulled from your mobile ClearNode’s application memory – it will say “Setup (from prefs)” or “Setup (default)“. Once a node has been configured and you return to this screen, the setup will be pulled off the node and the title will be “Setup (from node)“.
Backup and Restore your Node Setup
Once you have configured your node you may return to this screen and use the share/context menu (top right) to backup and restore your node’s configuration to the Node-Ventures server. This is useful for keeping a secure copy of the setup in case your node has to be reinstalled and returned to factory defaults. This is optional, but can get you out of a tight spot.
There are 6 Setup Sections:
- RedNode Interface
- AllStar Identity
- AllStar Server
- Weather Options
- Streaming Audio Setup
- HamVoIP Identity
Note that after changing an option on this screen you must tap Save in the top right corner to make the changes active.
Also note that saving the new configuration will recreate the configuration files from templates – potentially overwriting any manual edits you have made to those files via SSH.
Hardware and Network Section
This section is mostly informational and the first 3 options are read only.
Retry network (n) times: During boot and node startup ClearNode interrogates both the Ethernet and WiFi network to see if it can achieve an internet connection. After each try it waits an increasing period of time and will try “n” times before giving up and activating the WiFiByLight functionality (solid Red LED). Generally 4 is the optimal number of times to try – you may increase this number if you know your WiFi devices “struggle” to get connected.
Enable automatic RedNode updates: if this setting is turned on, each time your node starts up (after a reboot or a power up), it will check with our update server and perform an immediate update if a newer version of the node software is available.
AllStar Identity Section
Node Number & Node Password: These are the bare minimum fields that you must fill out for your ClearNode to function. You may leave everything else on the Node Setup screen at the default values for a very simple installation.
Node Numbers are assigned by the AllStarLink organization, as are the initial passwords. Note that the Node Password is NOT normally your AllStar Portal Login password – each node number has it’s own unique password.
dvswitch/zoiper Password: ClearNode can be configured to accept connections from the Android app “DVSwitch” or the iOS app “Zoiper”. This is where you would configure the password for those apps to use to connect to your node. See Zoiper & DVSwitch for more details.
AllStar Server Section
IAXPort (bindport): This is the UDP network port that your ClearNode uses to pass encoded voice data between nodes. The default is 4569 and if you only have one node on your network, that’s fine. If you have multiple nodes on your home or office network – each node needs to have a different IAX Port so they can work independently of each other.
If you want to enable incoming connections to your node, you must forward this UDP port number through your WiFi or Ethernet router/firewall/hotspot. For outgoing connections only, this is not necessary.
Enable IAX from network (bindaddr): Turn this on to allow network connections to the AllStar Manager from outside of your node. You might want this for other mobile or desktop applications that can control AllStar.
Transmit/Receive timeout (ms): Generally leave these values at the defaults. AllStar will “timeout” a very long QSO, either incoming or outgoing, according to these timings. This is for the good of the larger community to protect the system against “lockups” such as a failed piece of equipment e.g. a “stuck mic”.
Hang time (ms) / Alt Hang time (ms): generally leave this at its default values – those interfacing with repeaters might want to adjust this.
Enable RX Notch Filter / RX Notch Filter: useful if you want to remove unwanted audio artifacts received from your HT. The format is [frequency, bandwidth, frequency, bandwidth …]. The example provided is useful if you are using a Baofeng as your HT.
Use Voice ID: generally your node will ID every 10 minutes, it will transmit your call sign as CW tones. Turn this option on if you would rather your node IDed by speaking your call sign in english.
CW ID Interval/Frequency/Amplitude: these values control how often your node IDs, the frequency and amplitude of the CW tones.
Enable audio analysis: This option enables the SOX Audio Analysis functionality on your node which can be inspected in the “Adjust USB Audio Gain for VOIP” screen. See the AUDIO TUNING page for more information. Once you are done tuning your audio, turn this option off to preserve CPU resources for the normal running of your node.
Enable parrot mode: Turn this on to have your node repeat back your transmission over the embedded radio – useful for assessing the quality of your audio.
Report stats to AllStar/HamVoIP: Normally leave this turned on – some hub and systems will not allow you to connect if you are not reporting statistics to the network operators. Turn this off if you want to hide the state of your node from the public network.
Auto-connect: These 3 settings allow you to automatically connect to a specific node after boot/startup. The delay is the number of seconds ClearNode waits before initiating the auto connect. Be careful here that you don’t forget you have this set and then connect to another system using the mobile app or DTMF commands. Cross connecting big systems is a sure fire way of making yourself unpopular.
Supermon ‘admin’ psw / http port: Supermon is installed in your ClearNode by default. The username is ‘admin’ and the password is set to your ClearNode Key. The page can be accessed using a web browser on the standard http port 80. You can set your Supermon password and http port in this section.
Deny/Permit Mode / List: A comma delimited list of node #s that you wish to explicitly permit inbound connections from, or, deny inbound connections from. If you set a Permit list – all other node #s will be denied.
Propagate DTMF / phone DTMF / remote allowed: See the notes at AllStarLink Wiki for explanation.
Say IP at boot: With this option enabled, each time your node boots up it will transmit a voice that annunciates your LAN side IP Address – the address you would use for a Supermon or SSH connection.
Enable courtesy tones: Courtesy tones give you audio indications and confirmation of activity on your node:
- When your node has no connection to another node and you attempt to transmit, after you key-down your HT, your node will respond with the negative audio “boop” tone to indicate you did not send any audio
- If your node is connected to a remote node, after key-up/down your node will respond with the positive “beep-boop” to indicate successful transmission to the AllStar network.
- Similarly your node will respond with the positive/negative tones to indicate success/failure when you command the node using DTMF signals
Enable link unkey tone: Whenever the remote user ends their transmission your node will respond with a “boop” tone. A lot of folks find this tone unnecessary and turn it off.
Duplex Mode: This generally should be set to “1” for Simplex AllStar nodes. If you want to suppress the 10 minute morse ID announcement set it to “0”. Note that the FCC requires that your node identifies at least every 10 minutes if there is traffic on the radio. The other values are generally not needed by simplex nodes and are included to support future version of the hardware.
Voice Telemetry: When enabled your node will voice announce connections to and from your node, including changes at remote nodes. When set to “On” these announcements can get annoyingly verbose, particularly if you are connected to a busy hub. Setting it to “Limited” will only announce local connection and disconnections and then will silence after 1 minute.
Weather Options Section
Zip for weather: Your ClearNode supports the “*81” and “*82” DTMF commands that prompt your node to announce the local time and weather conditions. Set this Zip Code to the location you want the announcements for.
Enable AutoSky at boot: AutoSky is installed and partially configured in all new ClearNodes. To use it you must enable it at boot and configure the appropriate “National Weather Service County Code” for your station. If you ordered your ClearNode pre-configured this County Code will already be set.
NWS County Code: You can find your Count Code at the NWS website at “alerts.weather.gov” website. Typically the code is 3 capital letters and 3 digits.
Play AutoSky every (ms): If there is an active weather warning for your station and if your node is not busy, the warning will be announced over your ClearNode’s built in radio every so many milliseconds.
Play after busy delay (ms): If your node is busy with QSO traffic at the moment that AutoSky wants to transmit a warning, it will wait this many milliseconds after your node becomes idle to make the transmission.
Note: You must also turn on the “AutoSky Check Advisories” Time Event in the “Manage Timed Events” section – this enables the crontab which checks for advisories every 5 minutes.
Streaming Audio Setup Section
Enable streaming audio: We at Node-Ventures maintain an Icecast server in our data center. If this option is checked your node will automatically connect to that server and publish an audio stream of all the traffic on your node. You can access this stream from your mobile device by returning to the Node Detail screen and tapping the Play button in the top right hand corner. The audio stream is delayed by about 20 seconds. To turn off the stream, return to the Node Detail screen and tap the Pause button in the top right hand corner. Note that the audio will continue to be streamed to the server wether you are listening to it or not. If you are concerned about mobile data consumption, return to the Node Setup screen and disable this option.
Streaming Mode: Since RedNode API version 29, you can configure your audio to stream to your personal account and stream endpoint at Broadcastify. You will need an account and a stream pre-configured at Broadcastify. See the help sections at Broadcastify to get this configuration complete. The following “BCFY” configuration items will displayed on the “Technicals” tab of “Manage Feed” page for your stream on the Broadcastify website.
BCFY Url:Port: This is the destination URL that ClearNode will send your stream to – in other words your streams input.
BCFY Mount Point: You may have multiple streams at Broadcastify – they are uniquely identified using this value.
BCFY Password: Each stream requires a password assigned by Broadcastify.
BCFY Stream Name: Some description for your stream
BCFY Play Url: If you want your stream to play in your ClearNode app in the same way as the standard ClearNode stream does, you must set this Url so the ClearNode mobile app knows where to connect to play the stream. Discovering it is a little tricky – on the “Manage Feed” page at Broadcastify for your stream, in the “General Details” tab, click the value for “Primary Description” to reach the player page for your stream. Select “Windows Media Player” or “Real Player” under “Player Selection and then click the Play icon – a small file will be downloaded to your computer, open this file to find the URL embedded in it. Unfortunately this URL will change over time so you will need to keep resetting it. Broadcastify offers a paid service that makes this URL static so you don’t have to repeatedly reset it.
The EchoLink setup section is now a standalone screen containing just the EchoLink configuration items. Save your setup to the node and wait until your node reboots. In the Node Details screen select the “EchoLink Setup” option.
We will not go through the detail of the EchoLink setup – most of it is self explanatory. Note that “Call”, “Password” and “EchoLink node #” are the 3 important values and must be set correctly for EchoLink to function. The rest of the values are for display purposes and aren’t validated.
Note that there are 3 variations of your call sign at Echolink e.g.: W6WNG, W6WNG-L, W6WNG-R – each must be “validated” separately at EchoLink, they will not be usable until they have. EchoLink is now requiring that ClearNodes must use the -L or -R version (sysop mode). It is typical to use the “-L” version on a simplex node like ClearNode. The current versions of the ClearNode mobile apps will not allow you to use the non-sysop version of your callsign.
Announce mode: At the bottom of the “EchoLink Setup Section” – Echolink provides a secondary option that allows connect/disconnect announcements to state the Node #, or optionally, the Callsign for the connection. Note that “Voice telemetry” in the “Telemetry Section” must be enabled for this option to have any effect.
Pi Operating System Setup
At the bottom of the Node Details page is a link to the “Operating System Setup” page. We will be implementing configuration of the Raspberry Pi’s Linux operating system on this page.
You can set the node Timezone and the Pi ‘root’ password on this page. Click the Timezone row to select a new Timezone. Enter a new ‘root’ password and tap “Save” in the top right corner to save it. Your existing ‘root’ password will NOT be displayed in this field for security reasons.
Digital Bridge Setup: The configuration items for the Digital Bridge are detailed on separate page, see “DIGITAL MODES” in the navigation area at the top of this page.