Echolink Channel Driver - Revision history

Kg7qin at 05:16, 28 January 2022

2022-01-28T05:16:35Z

KM4NNO at 16:32, 1 January 2021

2021-01-01T16:32:01Z

Bryan: /* Node Stanza Keys */

2019-05-23T15:55:28Z

Node Stanza Keys

N8THN: added Node stanza section from drupal site

2019-01-28T15:07:18Z

added Node stanza section from drupal site

Bryan: /* Setup */

2018-09-27T21:23:33Z

Setup

KB8JNM at 14:55, 17 June 2018

2018-06-17T14:55:56Z

KB8JNM: added definition/formatting

2018-06-17T14:52:12Z

added definition/formatting

KB8JNM: Added some definitions/formating

2018-06-17T14:47:14Z

Added some definitions/formating

Kg7qin: /* Caveats */ typo

2018-05-27T17:35:09Z

Caveats: typo

Kg7qin: /* Caveats */

2018-05-27T17:33:10Z

Caveats

@@ Line 1: / Line 1: @@
 The chan_echolink channel driver allows PTTLink nodes to register on and communicate with the EchoLink network.  The following information is originally from [http://docs.pttlink.org/drupal/node/12 echolink.conf].
@@ Line 27: / Line 29: @@
 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>
+<syntaxhighlight lang="ini">
 [el0]
 confmode=no           ; Conference mode
-call=W6ABC-R	      ; Change this to your callsign!
+call=W6ABC-R          ; Change this to your callsign!
-pwd=XXXXX	      ; Change this to your password!
+pwd=XXXXX             ; Change this to your password!
 name=echolinkusername ; Change this to your real name!
 qth=echolink-location ; Change this to your actual QTH!
@@ Line 48: / Line 50: @@
 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)
+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)
+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)
+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)
+dir=0                 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction)
-</pre>
+</syntaxhighlight>
 ** How many stations will your node support ? The 2 most particular factors will be how much CPU/Memory power you have
@@ Line 97: / Line 99: @@
 The audio gain going to and coming from the Echolink system may be set from within a Node Stanza as follows:
-<pre>
+<syntaxhighlight lang="ini">
 erxgain=-3.0      ; defaults to -3.0 db
 etxgain=3.0       ; defaults to 3.0 db.
-</pre>
+</syntaxhighlight>
 =Debugging=
@@ Line 125: / Line 127: @@
 *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 PTTLink node not being able to connect to/register/use the EchoLink servers or other EchoLink nodes.
-<pre>
+<syntaxhighlight lang="text">
 Note: Same network refers to the the Public IP address that both your PTTLink 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>
+</syntaxhighlight>
 ==Caveats==
@@ Line 162: / Line 164: @@
 | o.rec || Turn on/off recording
 |}

@@ Line 1: / Line 1: @@
-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].
+The chan_echolink channel driver allows PTTLink nodes to register on and communicate with the EchoLink network.  The following information is originally from [http://docs.pttlink.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.
+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 PTTLink 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.
+From an app_rpt/PTTLink node, Echolink connections look just like PTTLink/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 PTTLink 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!
@@ Line 37: / Line 37: @@
 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!
+astnode=2345          ; Change this to your active PTTLink node number!
-context=radio-secure  ; The allstar context (leave the default unless you have good reason to change)
+context=radio-secure  ; The PTTLink context (leave the default unless you have good reason to change)
 server1=server1.echolink.org
 server2=server2.echolink.org
@@ Line 68: / Line 68: @@
 |-
 |eannmode
-|0 = do not announce Echolink nodes at all, 1 = announce only the node number (Allstar-translated), 2 = announce only the call of the echolink station, 3 = announce both
+|0 = do not announce Echolink nodes at all, 1 = announce only the node number (PTTLink-translated), 2 = announce only the call of the echolink station, 3 = announce both
 |1
 |-
@@ Line 121: / Line 121: @@
 =Miscellaneous=
 ==Connectivity Issues==
-When debugging EchoLink connectivity issues with your AllStar node, remember the following:
+When debugging EchoLink connectivity issues with your PTTLink 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).
+*Never run the EchoLink application from your mobile device (cell phone/tablet/etc) using the '''same network''' as your PTTLink 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 PTTLink 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.
+*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 PTTLink 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.
+Note: Same network refers to the the Public IP address that both your PTTLink 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>
@@ Line 151: / Line 151: @@
 ==Remote Commands==
-The following '''''remote text commands''''' can be sent to the chan_echolink driver running on your AllStar link node using ''netcat'':
+The following '''''remote text commands''''' can be sent to the chan_echolink driver running on your PTTLink node using ''netcat'':
 {| class="wikitable"

@@ Line 60: / Line 60: @@
 == Node Stanza Keys ==
 {| class="wikitable"
 !Key

← Older revision		Revision as of 15:07, 28 January 2019
Line 58:		Line 58:

	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].		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].
		+
		+	== Node Stanza Keys ==
		+	{\| class="wikitable"
		+	!Key
		+	!Valid Values
		+	!Default
		+	\|-
		+	\|eannmode
		+	\|0 = do not announce Echolink nodes at all, 1 = announce only the node number (Allstar-translated), 2 = announce only the call of the echolink station, 3 = announce both
		+	\|1
		+	\|-
		+	\|echolinkdefault
		+	\|0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode
		+	\|2
		+	\|-
		+	\|echolinkdynamic
		+	\|0 = disallow users to change current echolink telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command
		+	\|1
		+	\|}

	[[Category:Node Configuration]]		[[Category:Node Configuration]]

← Older revision		Revision as of 21:23, 27 September 2018
Line 58:		Line 58:

	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].		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].
		+
		+	[[Category:Node Configuration]]
		+	[[Category:Config Files]]

	==Controlling Access==		==Controlling Access==

@@ Line 17: / Line 17: @@
 |-
 |  5199 || UDP
 |}

@@ Line 122: / Line 122: @@
 * 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"
+* Allows "doubles" (newer version of the software are preventing this. Work in progress)
 ==Remote Commands==

@@ Line 117: / Line 117: @@
 * Does not have any stats.
 * Does not have any callsign prefix restrictions.
-* Does not announce on on connects/disconnects.  ''(Connect/disconnect announcements come from app_rpt's telemetry instead using the 3xxxxxx node number format)''
+* 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"