"PTTLink Wiki" - User contributions [en]

PTTLink DEBIAN-9 INSTALL ON VULTR

2019-03-30T15:03:44Z

KB8JNM: updated info, removed less essential info, corrected spelling

Written by Mike (KB8JNM)

Before you start:
You probably should read most of this once before you start (to the +++++++++ anyway). It will help.

1- Get signed up with account on vultr.com and verify email.

2- Add a server (Blue "+" button, Mid-Upper Right), to find a cheaper install, you may need to change server locations till you see one available,
otherwise, you may need to choose a $5 or 1gb Mem server or larger.
You will need to look in advance to Vultr's section (3) for size selection for each location.
Flipping between section (1) & (3) to get that right. Not all size servers are available at all times at all locations. (some sell-out).

3- At Vultr's section (2) - OS's, you will need to select just above the selections, to "UPLOAD ISO".
Plug this "currently valid" link to the ASL Stretch Deb 9 ISO -
http://dvswitch.org/files/ASL_Images/Intel-AMD/Stretch/ASL_1.01-20180417-amd64-i386-debian-stretch-netinst.iso

Place that link into the load iso. Go to next step.

4- You should be able to move forward to Vultr's section (7) and select the hostname (i.e. eoh.29999.link), if you wish,
or wait and do that though the ASL-MENU / manually. But this will save you a step.

5- DEPLOY YOUR SERVER

6- Look in the top right hand of the screen and you will see a monitor next to the power button.
Click that for your console and you may enter data as needed for your deployment just as if the system is in front of you.
But note that you are not going to copy paste any instructions at the command line like you might with putty ssh shell.
Also Note: Your mouse will not function inside the CONSOLE window.
Use keyboard / 'TAB' & 'ARROWS' to navigate fields & 'SPACEBAR' or ENTER/CR to select inside ASL-MENU.

7- After all is done in your install, your console screen will be blank.

*** you will need to look at your "vultr server instance" to remove your ISO and that will force a reboot.
*** The way to do that is to click on your server instance, click settings (above)
*** then look on the left for load ISO again, the menu will show big blue button to REMOVE ISO
*** You probably will need to launch the console screen again. Close the old one first if it went blank !

--Now, that's about all I can guide you on with that. See normal install instructions.
--The default user is repeater and pw is allstarlink
--If you get lost somehow, # cd /usr/local/sbin/ - and run - # sudo asl-menu - if you are setting-up with the script.
--Please be careful when setting new root password, it shows at the bottom of the screen and this will give you
--root access in the console only. To get root access in your SFTP, you need to
--edit /etc/ssh/ssh_config and PermitRootLogin yes
--save/exit restart sshd but for your own good, don't leave it this way. Please change the port address while you are there editing from the default of 22. You can do this later.

###!!! A well done job for those responsible for a perfect ASL ISO deployment. Thank You !
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Additional >
If you like to play, Let's go one further step so you can run this as your own website.
You will love to learn this after you have set-up your server and it's verified running.

To make this completely web compatible, so to speak, you will want a 'LAMP STACK'
which is basically Linux (you already have) MySQL database, PHP server-side scripting and Appache2 for your HTML server on port 80.
I'm not writing the how-to for this, but here is a link I found on the web to guide you through it for this Debian 9 install.

https://linuxconfig.org/how-to-install-a-lamp-server-on-debian-9-stretch-linux

AS A ADDED BONUS FOR OTHER WEB WORKINGS:
While after you have installed you lamp stack, you can always get to the server web pages you construct via ip address,
you may want to pick-up a domain name and use that for a pointer to the IP. I have this suggestion for you....

After deploying the LAMP stack (or before anything in my case) I went to NameSilo.com,
Picked up the domain name 29999.link @ $ 8.69 (per year)
Then go to the domain manager and point it at the ip address of the ASL Server.

So you will have basicly, any record you see with a ip address now needs re-pointed to match your server.
You might add one for your hostname... server.29999.link
Some of you know how to set-up a A record, MX for mail and cname.
But it is never to late to learn how it all works before or after your deployment.
But this is 'not required' for the minimal operation of a VPS deployed system.
You or your club could take advantage of your own website & email with what you already have.

But that brings up other issues like security.

So what I will add here is for your own good. Don't do a bunch of other stuff until you get a grip on security of your system.
The ASL install comes with a firewall but it is up to your to set-it and run it and keep a eye on your system.
But to add some flavor to your install,
use valtr's free "snapshot" of your instance for a backup once you know you have a solid working node.
They also provide a scheduled back-up service at $1 a month.
I'm not here to endorse them but it's there and I sometimes use it on instances I have.

[[Category:How to]]

Echolink Channel Driver

2018-06-17T14:55:56Z

KB8JNM:

The chan_echolink channel driver allows AllStar nodes to register on and communicate with the EchoLink network. The following information is originally from [http://docs.allstarlink.org/drupal/node/12 echolink.conf].

=echolink.conf=
With the addition of the chan_echolink Asterisk channel driver direct connections to and from echolink to Asterisk/app_rpt are now supported. No other programs (e.g. rtpDir, or the link box) are required. With chan_echolink, EchoLink nodes become part of the AllStar link number space.

From an app_rpt/Allstar node, Echolink connections look just like Allstar/App_rpt connections except the Echolink node numbers have been prefixed with a 3 and padded out to 7 digits with leading zeroes. For instance, if you want to connect to Echolink node 1234 on your app_rpt system you would dial *3 followed by 3001234. If you have a 6 digit Echolink node number 123456, you would dial *3 followed by 3123456. As you can see we have reserved Allstar node numbers with a leading 3 for the Echolink number space.

For users originating from an Echolink node using Echolink supplied software, nothing changes for them, they just dial the 4 or 6 digit Echolink node number assigned to your app_rpt system and they get connected!

==Setup==
First, if you are behind a NAT router, please make sure the ports for Echolink service are correctly forwarded to your asterisk system.

{| class="wikitable"
! Port To Forward !! Service
|-
| 5198 || UDP
|-
| 5199 || UDP
|-
| 5200 || TCP
|}

Additionally, if you are running a firewall and not a consumer grade router which is configured to limit outbound access to a specific number of ports, you must enable UDP outbound access for 5198, and 5199, and TCP outbound access for port 5200.

Current documentation on what ports need to be forwarded can be found on echolink.org in the [http://echolink.org/firewall-friendly.htm EchoLink, Firewalls, and Routers] section.

To activate the Echolink channel driver, all that's required is a properly formatted configuration file. A base configuration file has been included with Both ACID and Limey Linux and is located in /usr/src/configs/examples/echolink. Copy this file to /etc/asterisk, and edit it to match your callsign, password and node number assignment from Echolink.org. The sample echolink.conf file is as follows:

<pre>
[el0]
confmode=no ; Conference mode
call=W6ABC-R ; Change this to your callsign!
pwd=XXXXX ; Change this to your password!
name=echolinkusername ; Change this to your real name!
qth=echolink-location ; Change this to your actual QTH!
email=foo@bar.com ; Change this to your echolink registered email!
maxstns=20 ; The maximum 'at-once' connections allowed/supported (see ** below)
node=123456 ; Change this to the assigned 'ECHOLINK' node#
astnode=2345 ; Change this to your active Allstar node number!
context=radio-secure ; The allstar context (leave the default unless you have good reason to change)
server1=server1.echolink.org
server2=server2.echolink.org
server3=server3.echolink.org
rtcptimeout=10
recfile=/tmp/recorded.gsm
freq=145.000 ; Freq in MHz
tone=100.0 ; CTCSS Tone (0 for none)
lat=34.74978 ; Latitude in decimal degrees
lon=-92.27666 ; Longitude in decimal degrees
power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts)
height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet)
gain=7 ; Gain in db (0-9)
dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction)
</pre>

** How many stations will your node support ? The 2 most particular factors will be how much CPU/Memory power you have
AND how much bandwidth you have available. So you should not expect a bunch from cpu's under 1ghz or from memory below 1gb.

Once you have made the changes, restart Asterisk, and within a few minutes time, the node should show up on the echolink.org website under [http://echolink.org Current Logins].

==Controlling Access==
Echolink connections may be denied on a per-callsign basis. This is done by using the deny and permit key values in the above [el0] stanza. The default is to allow all connections if the permit and deny keywords are not present. If a permit is specified, then only the callsigns specified in the permit statement will be allowed to connect. If deny is specified, then the callsign(s) specified will be denied access and the connection will be terminated. Commas are used to delimit multiple callsigns for permit and deny keys. Wildcards are supported so that whole classes of connections can be rejected. Examples:

Examples:

To deny w6xxx you would add the statement: '''deny=w6xxx'''

To prohibit computer-based connections you would write: '''permit=*-*'''

To allow access to only a select group of callsigns: '''permit=w6abc,w6def,...'''

==Setting Audio Levels==
The audio gain going to and coming from the Echolink system may be set from within a Node Stanza as follows:

<pre>
erxgain=-3.0 ; defaults to -3.0 db
etxgain=3.0 ; defaults to 3.0 db.
</pre>

=Debugging=
The chan_echolink driver supports debugging output.

Debugging can be a activated with the command '''echolink debug level x''' (Where x = 0-7. 0=off). With debugging turned on, chan_echolink will output various messages to the terminal related to connecting to nodes, etc.

In addition to turning on debugging, you can use the following commands to query your node's copy of the EchoLink database:
{| class="wikitable"
! Description !! Command
|-
| Dump EchoLink database || echolink dbdump
|-
| Query EchoLink station by callsign || echolink dbget callsign <EchoLink Callsign> (i.e., KG7QIN-R)
|-
| Query EchoLink station by nodename || echolink dbget nodename <EchoLink node number> (i.e., 407301)
|-
| Query EchoLink station by ip address || echolink dbget ip <EchoLink node ip address>
|}
=Miscellaneous=
==Connectivity Issues==
When debugging EchoLink connectivity issues with your AllStar node, remember the following:
*Never run the EchoLink application from your mobile device (cell phone/tablet/etc) using the '''same network''' as your AllStar node. This will lead to problems with one or the other not being able to connect to/register/use the EchoLink servers or other EchoLink nodes. (This also applies to running the Windows application on the same network as your AllStar node).
*If using the EchoLink application on your mobile device (cell phone/tablet/etc), make sure that the EchoLink application is '''not set to run/is not running in the background'''. Having the application running in the background can cause problems with your AllStar node not being able to connect to/register/use the EchoLink servers or other EchoLink nodes.

<pre>
Note: Same network refers to the the Public IP address that both your AllStar node AND the device running the EchoLink application are using -- even if they are on different subnets internally. The Public IP is what the EchoLink servers/network sees and uses when communicating with your node/device.
</pre>

==Caveats==
The chan_echolink driver currently:

* Does not send its station info.
* Does not process chat text.
* Only recognizes a few remote text commands.
* Does not have a busy, deaf or mute feature.
* Does not have capacity limits.
* Does not have a banned or private station list. ''(Access controls are rudimentary and on a per station basis. See [[Echolink_Channel_Driver#Controlling_Access|Controlling Access]])''
* Does not have an admin list, only local 127.0.0.1 access.
* Does not have a customizable welcome text message.
* Does not support login or connect timeouts.
* Does not have a max TX time limit.
* Does not support activity reporting.
* Does not have event notifications.
* Does not have any stats.
* Does not have any callsign prefix restrictions.
* Does not announce on connects/disconnects. ''(Connect/disconnect announcements come from app_rpt's telemetry using the 3xxxxxx node number format)''
* Does not have any loop detection.
* Allows "doubles" (newer version of the software are preventing this. Work in progress)

==Remote Commands==
The following '''''remote text commands''''' can be sent to the chan_echolink driver running on your AllStar link node using ''netcat'':

{| class="wikitable"
! Command !! Function
|-
| o.conip <IPaddress> || Request a connect
|-
| o.dconip <IPaddress> || Request a disconnect
|-
| o.rec || Turn on/off recording
|}

[[Category:Node Configuration]]

Echolink Channel Driver

2018-06-17T14:52:12Z

KB8JNM: added definition/formatting

The chan_echolink channel driver allows AllStar nodes to register on and communicate with the EchoLink network. The following information is originally from [http://docs.allstarlink.org/drupal/node/12 echolink.conf].

=echolink.conf=
With the addition of the chan_echolink Asterisk channel driver direct connections to and from echolink to Asterisk/app_rpt are now supported. No other programs (e.g. rtpDir, or the link box) are required. With chan_echolink, EchoLink nodes become part of the AllStar link number space.

From an app_rpt/Allstar node, Echolink connections look just like Allstar/App_rpt connections except the Echolink node numbers have been prefixed with a 3 and padded out to 7 digits with leading zeroes. For instance, if you want to connect to Echolink node 1234 on your app_rpt system you would dial *3 followed by 3001234. If you have a 6 digit Echolink node number 123456, you would dial *3 followed by 3123456. As you can see we have reserved Allstar node numbers with a leading 3 for the Echolink number space.

For users originating from an Echolink node using Echolink supplied software, nothing changes for them, they just dial the 4 or 6 digit Echolink node number assigned to your app_rpt system and they get connected!

==Setup==
First, if you are behind a NAT router, please make sure the ports for Echolink service are correctly forwarded to your asterisk system.

{| class="wikitable"
! Port To Forward !! Service
|-
| 5198 || UDP
|-
| 5199 || UDP
|}

Additionally, if you are running a firewall and not a consumer grade router which is configured to limit outbound access to a specific number of ports, you must enable UDP outbound access for 5198, and 5199, and TCP outbound access for port 5200.

Current documentation on what ports need to be forwarded can be found on echolink.org in the [http://echolink.org/firewall-friendly.htm EchoLink, Firewalls, and Routers] section.

To activate the Echolink channel driver, all that's required is a properly formatted configuration file. A base configuration file has been included with Both ACID and Limey Linux and is located in /usr/src/configs/examples/echolink. Copy this file to /etc/asterisk, and edit it to match your callsign, password and node number assignment from Echolink.org. The sample echolink.conf file is as follows:

<pre>
[el0]
confmode=no ; Conference mode
call=W6ABC-R ; Change this to your callsign!
pwd=XXXXX ; Change this to your password!
name=echolinkusername ; Change this to your real name!
qth=echolink-location ; Change this to your actual QTH!
email=foo@bar.com ; Change this to your echolink registered email!
maxstns=20 ; The maximum 'at-once' connections allowed/supported (see ** below)
node=123456 ; Change this to the assigned 'ECHOLINK' node#
astnode=2345 ; Change this to your active Allstar node number!
context=radio-secure ; The allstar context (leave the default unless you have good reason to change)
server1=server1.echolink.org
server2=server2.echolink.org
server3=server3.echolink.org
rtcptimeout=10
recfile=/tmp/recorded.gsm
freq=145.000 ; Freq in MHz
tone=100.0 ; CTCSS Tone (0 for none)
lat=34.74978 ; Latitude in decimal degrees
lon=-92.27666 ; Longitude in decimal degrees
power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts)
height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet)
gain=7 ; Gain in db (0-9)
dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction)
</pre>

** How many stations will your node support ? The 2 most particular factors will be how much CPU/Memory power you have
AND how much bandwidth you have available. So you should not expect a bunch from cpu's under 1ghz or from memory below 1gb.

Once you have made the changes, restart Asterisk, and within a few minutes time, the node should show up on the echolink.org website under [http://echolink.org Current Logins].

==Controlling Access==
Echolink connections may be denied on a per-callsign basis. This is done by using the deny and permit key values in the above [el0] stanza. The default is to allow all connections if the permit and deny keywords are not present. If a permit is specified, then only the callsigns specified in the permit statement will be allowed to connect. If deny is specified, then the callsign(s) specified will be denied access and the connection will be terminated. Commas are used to delimit multiple callsigns for permit and deny keys. Wildcards are supported so that whole classes of connections can be rejected. Examples:

Examples:

To deny w6xxx you would add the statement: '''deny=w6xxx'''

To prohibit computer-based connections you would write: '''permit=*-*'''

To allow access to only a select group of callsigns: '''permit=w6abc,w6def,...'''

==Setting Audio Levels==
The audio gain going to and coming from the Echolink system may be set from within a Node Stanza as follows:

<pre>
erxgain=-3.0 ; defaults to -3.0 db
etxgain=3.0 ; defaults to 3.0 db.
</pre>

=Debugging=
The chan_echolink driver supports debugging output.

Debugging can be a activated with the command '''echolink debug level x''' (Where x = 0-7. 0=off). With debugging turned on, chan_echolink will output various messages to the terminal related to connecting to nodes, etc.

In addition to turning on debugging, you can use the following commands to query your node's copy of the EchoLink database:
{| class="wikitable"
! Description !! Command
|-
| Dump EchoLink database || echolink dbdump
|-
| Query EchoLink station by callsign || echolink dbget callsign <EchoLink Callsign> (i.e., KG7QIN-R)
|-
| Query EchoLink station by nodename || echolink dbget nodename <EchoLink node number> (i.e., 407301)
|-
| Query EchoLink station by ip address || echolink dbget ip <EchoLink node ip address>
|}
=Miscellaneous=
==Connectivity Issues==
When debugging EchoLink connectivity issues with your AllStar node, remember the following:
*Never run the EchoLink application from your mobile device (cell phone/tablet/etc) using the '''same network''' as your AllStar node. This will lead to problems with one or the other not being able to connect to/register/use the EchoLink servers or other EchoLink nodes. (This also applies to running the Windows application on the same network as your AllStar node).
*If using the EchoLink application on your mobile device (cell phone/tablet/etc), make sure that the EchoLink application is '''not set to run/is not running in the background'''. Having the application running in the background can cause problems with your AllStar node not being able to connect to/register/use the EchoLink servers or other EchoLink nodes.

<pre>
Note: Same network refers to the the Public IP address that both your AllStar node AND the device running the EchoLink application are using -- even if they are on different subnets internally. The Public IP is what the EchoLink servers/network sees and uses when communicating with your node/device.
</pre>

==Caveats==
The chan_echolink driver currently:

* Does not send its station info.
* Does not process chat text.
* Only recognizes a few remote text commands.
* Does not have a busy, deaf or mute feature.
* Does not have capacity limits.
* Does not have a banned or private station list. ''(Access controls are rudimentary and on a per station basis. See [[Echolink_Channel_Driver#Controlling_Access|Controlling Access]])''
* Does not have an admin list, only local 127.0.0.1 access.
* Does not have a customizable welcome text message.
* Does not support login or connect timeouts.
* Does not have a max TX time limit.
* Does not support activity reporting.
* Does not have event notifications.
* Does not have any stats.
* Does not have any callsign prefix restrictions.
* Does not announce on connects/disconnects. ''(Connect/disconnect announcements come from app_rpt's telemetry using the 3xxxxxx node number format)''
* Does not have any loop detection.
* Allows "doubles" (newer version of the software are preventing this. Work in progress)

==Remote Commands==
The following '''''remote text commands''''' can be sent to the chan_echolink driver running on your AllStar link node using ''netcat'':

{| class="wikitable"
! Command !! Function
|-
| o.conip <IPaddress> || Request a connect
|-
| o.dconip <IPaddress> || Request a disconnect
|-
| o.rec || Turn on/off recording
|}

[[Category:Node Configuration]]

Echolink Channel Driver

2018-06-17T14:47:14Z

KB8JNM: Added some definitions/formating

The chan_echolink channel driver allows AllStar nodes to register on and communicate with the EchoLink network. The following information is originally from [http://docs.allstarlink.org/drupal/node/12 echolink.conf].

=echolink.conf=
With the addition of the chan_echolink Asterisk channel driver direct connections to and from echolink to Asterisk/app_rpt are now supported. No other programs (e.g. rtpDir, or the link box) are required. With chan_echolink, EchoLink nodes become part of the AllStar link number space.

From an app_rpt/Allstar node, Echolink connections look just like Allstar/App_rpt connections except the Echolink node numbers have been prefixed with a 3 and padded out to 7 digits with leading zeroes. For instance, if you want to connect to Echolink node 1234 on your app_rpt system you would dial *3 followed by 3001234. If you have a 6 digit Echolink node number 123456, you would dial *3 followed by 3123456. As you can see we have reserved Allstar node numbers with a leading 3 for the Echolink number space.

For users originating from an Echolink node using Echolink supplied software, nothing changes for them, they just dial the 4 or 6 digit Echolink node number assigned to your app_rpt system and they get connected!

==Setup==
First, if you are behind a NAT router, please make sure the ports for Echolink service are correctly forwarded to your asterisk system.

{| class="wikitable"
! Port To Forward !! Service
|-
| 5198 || UDP
|-
| 5199 || UDP
|}

Additionally, if you are running a firewall and not a consumer grade router which is configured to limit outbound access to a specific number of ports, you must enable UDP outbound access for 5198, and 5199, and TCP outbound access for port 5200.

Current documentation on what ports need to be forwarded can be found on echolink.org in the [http://echolink.org/firewall-friendly.htm EchoLink, Firewalls, and Routers] section.

To activate the Echolink channel driver, all that's required is a properly formatted configuration file. A base configuration file has been included with Both ACID and Limey Linux and is located in /usr/src/configs/examples/echolink. Copy this file to /etc/asterisk, and edit it to match your callsign, password and node number assignment from Echolink.org. The sample echolink.conf file is as follows:

<pre>
[el0]
confmode=no ; Conference mode
call=W6ABC-R ; Change this to your callsign!
pwd=XXXXX ; Change this to your password!
name=echolinkusername ; Change this to your real name!
qth=echolink-location ; Change this to your actual QTH!
email=foo@bar.com ; Change this to your echolink registered email!
maxstns=20 ; The maximum 'at-once' connections allowed/supported (see ** below)
node=123456 ; Change this to the assigned 'ECHOLINK' node#
astnode=2345 ; Change this to your active Allstar node number!
context=radio-secure ; The allstar context (leave the default unless you have good reason to change)
server1=server1.echolink.org
server2=server2.echolink.org
server3=server3.echolink.org
rtcptimeout=10
recfile=/tmp/recorded.gsm
freq=145.000 ; Freq in MHz
tone=100.0 ; CTCSS Tone (0 for none)
lat=34.74978 ; Latitude in decimal degrees
lon=-92.27666 ; Longitude in decimal degrees
power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts)
height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet)
gain=7 ; Gain in db (0-9)
dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction)
</pre>

** How many stations will your node support ? The 2 most particular factors will be how much CPU/Memory power you have
AND how much bandwidth you have available. So you should not expect a bunch from cpu's under 1ghz or from memory below 1gb.

Once you have made the changes, restart Asterisk, and within a few minutes time, the node should show up on the echolink.org website under [http://echolink.org Current Logins].

==Controlling Access==
Echolink connections may be denied on a per-callsign basis. This is done by using the deny and permit key values in the above [el0] stanza. The default is to allow all connections if the permit and deny keywords are not present. If a permit is specified, then only the callsigns specified in the permit statement will be allowed to connect. If deny is specified, then the callsign(s) specified will be denied access and the connection will be terminated. Commas are used to delimit multiple callsigns for permit and deny keys. Wildcards are supported so that whole classes of connections can be rejected. Examples:

Examples:

To deny w6xxx you would add the statement: '''deny=w6xxx'''

To prohibit computer-based connections you would write: '''permit=*-*'''

To allow access to only a select group of callsigns: '''permit=w6abc,w6def,...'''

==Setting Audio Levels==
The audio gain going to and coming from the Echolink system may be set from within a Node Stanza as follows:

<pre>
erxgain=-3.0 ; defaults to -3.0 db
etxgain=3.0 ; defaults to 3.0 db.
</pre>

=Debugging=
The chan_echolink driver supports debugging output.

Debugging can be a activated with the command '''echolink debug level x''' (Where x = 0-7. 0=off). With debugging turned on, chan_echolink will output various messages to the terminal related to connecting to nodes, etc.

In addition to turning on debugging, you can use the following commands to query your node's copy of the EchoLink database:
{| class="wikitable"
! Description !! Command
|-
| Dump EchoLink database || echolink dbdump
|-
| Query EchoLink station by callsign || echolink dbget callsign <EchoLink Callsign> (i.e., KG7QIN-R)
|-
| Query EchoLink station by nodename || echolink dbget nodename <EchoLink node number> (i.e., 407301)
|-
| Query EchoLink station by ip address || echolink dbget ip <EchoLink node ip address>
|}
=Miscellaneous=
==Connectivity Issues==
When debugging EchoLink connectivity issues with your AllStar node, remember the following:
*Never run the EchoLink application from your mobile device (cell phone/tablet/etc) using the '''same network''' as your AllStar node. This will lead to problems with one or the other not being able to connect to/register/use the EchoLink servers or other EchoLink nodes. (This also applies to running the Windows application on the same network as your AllStar node).
*If using the EchoLink application on your mobile device (cell phone/tablet/etc), make sure that the EchoLink application is '''not set to run/is not running in the background'''. Having the application running in the background can cause problems with your AllStar node not being able to connect to/register/use the EchoLink servers or other EchoLink nodes.

<pre>
Note: Same network refers to the the Public IP address that both your AllStar node AND the device running the EchoLink application are using -- even if they are on different subnets internally. The Public IP is what the EchoLink servers/network sees and uses when communicating with your node/device.
</pre>

==Caveats==
The chan_echolink driver currently:

* Does not send its station info.
* Does not process chat text.
* Only recognizes a few remote text commands.
* Does not have a busy, deaf or mute feature.
* Does not have capacity limits.
* Does not have a banned or private station list. ''(Access controls are rudimentary and on a per station basis. See [[Echolink_Channel_Driver#Controlling_Access|Controlling Access]])''
* Does not have an admin list, only local 127.0.0.1 access.
* Does not have a customizable welcome text message.
* Does not support login or connect timeouts.
* Does not have a max TX time limit.
* Does not support activity reporting.
* Does not have event notifications.
* Does not have any stats.
* Does not have any callsign prefix restrictions.
* Does not announce on connects/disconnects. ''(Connect/disconnect announcements come from app_rpt's telemetry using the 3xxxxxx node number format)''
* Does not have any loop detection.
* Allows "doubles"

==Remote Commands==
The following '''''remote text commands''''' can be sent to the chan_echolink driver running on your AllStar link node using ''netcat'':

{| class="wikitable"
! Command !! Function
|-
| o.conip <IPaddress> || Request a connect
|-
| o.dconip <IPaddress> || Request a disconnect
|-
| o.rec || Turn on/off recording
|}

[[Category:Node Configuration]]

SimpleUSB Channel Driver

2018-06-17T02:37:05Z

KB8JNM:

chan_simpleusb is ideal for smaller computers and those systems that do not need the chan_usbradio driver.

You must enable SimpleUSB.so to load in modules.conf first.

=simpleusb.conf=
The configuration of chan_simpleusb is done with the simpleusb.conf file and is self explanatory:

<pre>
; SimpleUSB configuration
;
[general]

[usb_<node#>]

eeprom=0

hdwtype=0 ; Leave this set to 0 for USB sound fobs modified using
; the instructions from usbfob.pdf. Use a setting of
; 1 is for Dingotel/Sph interfaces.

rxboost=1 ; 0 = 20db attenuator inserted, 1= 20db attenuator removed
; Set to 1 for additonal gain if using a low-level receiver output

carrierfrom=usbinvert ; no,usb,usbinvert
; no - no carrier detection at all
; usb - from the COR line on the modified USB sound fob
; usbinvert - from the inverted COR line on the modified USB sound fob

ctcssfrom=usbinvert ; no,usb,usbinvert
; no - CTCSS decoding, system will be carrier squelch
; usb - CTCSS decoding using input from USB FOB
; usbinvert - from the inverted CTCSS line on the modified USB sound fob

txmixa=voice ; Left channel output: no,voice,tone,composite,auxvoice
; no - Do not output anything
; voice - output voice only

txmixb=no ; Right channel output: no,voice,tone,composite, auxvoice
; See txmixa above.

invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to transmit
; This is the collector lead of the 2n4401 on the modified
; usb sound fob.
; please refer to the howto for the procedure to do this.

duplex=1 ; Full Duplex
</pre>

=Configuration=
==Parallel Port==
When setting chan_simpleusb to use a parallel port for I/O you must set a definition for the port address in rpt.conf:

<pre>
iobase=0x378 ; Parallel port address (using for cor/ptt & switches +dh-rbi - 378,278,3bc common Lpt 1,2,3
</pre>

You must then define the parallel port pins used for I/O in simpleusb.conf:

<pre>
[usb_<node#1>] ( ie [usb_1234] )
pp6=ptt
pp11=cor
...(+ additional info for this nodes usb config)...

[usb_<node#2>]
pp7=ptt
pp12=cor
</pre>
...(+ additional info for this nodes usb config)...

When configuring your simpleusb radio node you '''''MUST''''' ensure that the name of the radio is the same in both rpt.conf and simpleusb.conf.
The system looks inside the file SimpleUSB.conf for the match of the node# to be configured (i.e. usb_1234).

Node names are in format of ''usb_<nodenumber>''. Where <nodenumber> = the AllStar Link node of your system. ''Note that usb and the node number are separated by an underscore (_) character.''

Example:
Your simpleusb.conf file defines your usb radio as '''[usb_1000]'''. Your rpt.conf file would then have:

<pre>
rxchannel = SimpleUSB/usb_1000
</pre>

If you are reusing the simpleusb.conf file from an older installation (i.e., ACID), take special note of the change in naming. When a exact match is not made, the settings that follow will not be loaded.

=Miscellaneous=
==Parallel Port Pin Numbers==
Additional note on parallel port pin numbers:

When you are looking at the '''pp#''' addressing, the actual hardware pin numbers are in computer natural logical format. 
So hardware pin '''''D0''''' on the LPT port is equal to '''''pp1''''' in the software configuration. 

"0" is the first number to a computer as seen at the BIOS and/or hardware addressing. 
Be sure you are testing/setting/attaching the correct pin number.

Here is a listing of hardware pins and the software setup equivalents:

{| class="wikitable"
! Hardware pin !! Software equivalent
|-
| D0 || pp1
|-
| D1 || pp2
|-
| D2 || pp3
|-
| D3 || pp4
|-
| D4 || pp5
|-
| D5 || pp6
|-
| D6 || pp7
|-
| D7 || pp8
|}

Allstar denoted pins pp9 through pp12 are 'Input pins' listed as 'A#' in the parallel port scheme.

Special note: All these pins require 'buffering' by adding a transistor to do the actual switching.
They will not sink much current on their own.
In the case of some older radios you might interface, you might need to buffer with a transistor (2n2222 / 3904/3906)
AND a relay actuated by the buffer transistor. Mainly the PTT lines.
The best design is with optically-coupled transistors to prevent voltages and/or rf from running back through this port.
The unused output pins can be applied to switch things at the site. i.e. fan/light/alarm or even switching off other equipment.
Check command tables for info, not related to simple_usb.conf.
[[Category:Node Configuration]]

SimpleUSB Channel Driver

2018-06-03T03:47:09Z

KB8JNM:

chan_simpleusb is ideal for smaller computers and those systems that do not need the chan_usbradio driver.

You must enable SimpleUSB.so to load in modules.conf first.

=simpleusb.conf=
The configuration of chan_simpleusb is done with the simpleusb.conf file and is self explanatory:

<pre>
; SimpleUSB configuration
;
[general]

[usb_<node#>]

eeprom=0

hdwtype=0 ; Leave this set to 0 for USB sound fobs modified using
; the instructions from usbfob.pdf. Use a setting of
; 1 is for Dingotel/Sph interfaces.

rxboost=1 ; 0 = 20db attenuator inserted, 1= 20db attenuator removed
; Set to 1 for additonal gain if using a low-level receiver output

carrierfrom=usbinvert ; no,usb,usbinvert
; no - no carrier detection at all
; usb - from the COR line on the modified USB sound fob
; usbinvert - from the inverted COR line on the modified USB sound fob

ctcssfrom=usbinvert ; no,usb,usbinvert
; no - CTCSS decoding, system will be carrier squelch
; usb - CTCSS decoding using input from USB FOB
; usbinvert - from the inverted CTCSS line on the modified USB sound fob

txmixa=voice ; Left channel output: no,voice,tone,composite,auxvoice
; no - Do not output anything
; voice - output voice only

txmixb=no ; Right channel output: no,voice,tone,composite, auxvoice
; See txmixa above.

invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to transmit
; This is the collector lead of the 2n4401 on the modified
; usb sound fob.
; please refer to the howto for the procedure to do this.

duplex=1 ; Full Duplex
</pre>

=Configuration=
==Parallel Port==
When setting chan_simpleusb to use a parallel port for I/O you must set a definition for the port address in rpt.conf:

<pre>
iobase=0x378 ; Parallel port address (using for cor/ptt & switches +dh-rbi - 378,278,3bc common Lpt 1,2,3
</pre>

You must then define the parallel port pins used for I/O in simpleusb.conf:

<pre>
[usb_<node#1>] ( ie [usb_1234] )
pp6=ptt
pp11=cor
...(+ additional info for this nodes usb config)...

[usb_<node#2>]
pp7=ptt
pp12=cor
</pre>
...(+ additional info for this nodes usb config)...

When configuring your simpleusb radio node you '''''MUST''''' ensure that the name of the radio is the same in both rpt.conf and simpleusb.conf.
The system looks inside the file SimpleUSB.conf for the match of the node# to be configured (i.e. usb_1234).

Node names are in format of ''usb_<nodenumber>''. Where <nodenumber> = the AllStar Link node of your system. ''Note that usb and the node number are separated by an underscore (_) character.''

Example:
Your simpleusb.conf file defines your usb radio as '''[usb_1000]'''. Your rpt.conf file would then have:

<pre>
rxchannel = SimpleUSB/usb_1000
</pre>

If you are reusing the simpleusb.conf file from an older installation (i.e., ACID), take special note of the change in naming. When a exact match is not made, the settings that follow will not be loaded.

Additional note on parallel port pin numbers:

When you are looking at the pp# addressing, the actual hardware pin numbers are in computer natural logical format.
So hardware pin " D0 " on lpt port is = to pp1 in the software setup and so hardware pin " D7 " is = pp8

"0" is the first number to a computer as seen at the bios and/or hardware addressing.
Be sure you are testing/setting/attaching the correct pin number. D0 - D7 = pp1 - pp8

[[Category:Node Configuration]]