¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Shari node

 

What is the command to the second photo?


Re: AllStarLink.org - New ASL3 version just released - HUGE upgrade for all Pi & PC versions

 

Michael,

That was what I did on both of my PiHAT U and V.

COS LED lit up when I keyed up the node.

[events]
;;;;; Events Management ;;;;;
;status,2 = c|f|RPT_NUMLINKS ? ? ? ? ? ? ? ; Say time of day when all links disconnect.

cop,62,GPIO4:1 = c|t|RPT_RXKEYED
cop,62,GPIO4:0 = c|f|RPT_RXKEYED

?


Re: Beep after transmission

 

¿ªÔÆÌåÓý

I changed mine to linkunkeyct = ct3
Now I have a low pitch tone that no longer rips my ears.
You get the original tone if you kerchunk and you're not connected.

On 2024-07-12 11:39, Patrick Perdue wrote:

There are? a few ways, depending on how granular you want to make it.

On my simplex nodes, I like to disable the courtesy tone of link received transmissions, but still have the one that plays for incoming local transmissions, so I know I'm keying the node.


To disable all telemetry, including courtesy tones (other than ID) as well as disabling all hangtimes, in rpt.conf, change

duplex=1

to

duplex=0.

To just disable the courtesy tone you hear when a network transmission ends, look for the definition in rpt.conf for

linkunkeyct.
By default, this is
linkunkeyct = ct8
and comment out that line.

hth
N2DYI

On 7/12/2024 6:55 AM, Sander [VK6PI] via groups.io wrote:
Hi,

how can I disable the beep after every transmission from the Allstar node (ShariPi)? "Roger beep" is that how it's called?

Cheers,
Sander - VK6PI



Re: Shari node not receiving my HT

 

Glad to hear that your node is working now. Now, my node is broken, and it¡¯s not detecting any transmit audio from my Yaesu FT-5D. I think I¡¯ll have to start again with a new image and configure it to my screenshots of a working node.

Dave KY0L


On Fri, Jul 12, 2024 at 8:35?AM Hendrik Steyn via <groothendrik.steyn=[email protected]> wrote:

Thanks for all the help. I found the culprit! I changed the USBInvert option to plane USB and now it's working -- even the DTMF tones.

73 (Kind regards),
Hendrik (ZS6HBS)
Please visit my QRZ page at 
On 7/11/2024 8:00 PM, Dave via wrote:
I have a Shari PiHat-4U, and it is working with ASL3.?

Here are my configuration parameters:

asl-menu:

image.png

8. Interface Tune CLI:
image.png

sa818-menu:
image.png

On Thu, Jul 11, 2024 at 12:50?PM N8AR via <n8ar73=[email protected]> wrote:
There are new updates for ASL3 available.? Please apply them.

Here are the settings for the SA818 and simpleusb that I am using for ASL3.? Please try them.


Re: Beep after transmission

 

¿ªÔÆÌåÓý

There are? a few ways, depending on how granular you want to make it.

On my simplex nodes, I like to disable the courtesy tone of link received transmissions, but still have the one that plays for incoming local transmissions, so I know I'm keying the node.


To disable all telemetry, including courtesy tones (other than ID) as well as disabling all hangtimes, in rpt.conf, change

duplex=1

to

duplex=0.

To just disable the courtesy tone you hear when a network transmission ends, look for the definition in rpt.conf for

linkunkeyct.
By default, this is
linkunkeyct = ct8
and comment out that line.

hth
N2DYI

On 7/12/2024 6:55 AM, Sander [VK6PI] via groups.io wrote:

Hi,

how can I disable the beep after every transmission from the Allstar node (ShariPi)? "Roger beep" is that how it's called?

Cheers,
Sander - VK6PI


Re: Shari node not receiving my HT

 

SHARI PiXX working with "usb" instead of "usbinvert" for COSFROM is very strange.? Are you referring to CTCSSFROM instead of COSFROM.? Have you looked at simpleusb.conf to see if it set to "usb" there???


Re: Shari node not receiving my HT

 

¿ªÔÆÌåÓý

Thanks for all the help. I found the culprit! I changed the USBInvert option to plane USB and now it's working -- even the DTMF tones.

73 (Kind regards),
Hendrik (ZS6HBS)
Please visit my QRZ page at 
On 7/11/2024 8:00 PM, Dave via groups.io wrote:

I have a Shari PiHat-4U, and it is working with ASL3.?

Here are my configuration parameters:

asl-menu:

image.png

8. Interface Tune CLI:
image.png

sa818-menu:
image.png

On Thu, Jul 11, 2024 at 12:50?PM N8AR via <n8ar73=[email protected]> wrote:
There are new updates for ASL3 available.? Please apply them.

Here are the settings for the SA818 and simpleusb that I am using for ASL3.? Please try them.


Beep after transmission

 

Hi,

how can I disable the beep after every transmission from the Allstar node (ShariPi)? "Roger beep" is that how it's called?

Cheers,
Sander - VK6PI


Re: Shari node not receiving my HT

 

I have a Shari PiHat-4U, and it is working with ASL3.?

Here are my configuration parameters:

asl-menu:

image.png

8. Interface Tune CLI:
image.png

sa818-menu:
image.png


On Thu, Jul 11, 2024 at 12:50?PM N8AR via <n8ar73=[email protected]> wrote:
There are new updates for ASL3 available.? Please apply them.

Here are the settings for the SA818 and simpleusb that I am using for ASL3.? Please try them.


Re: Shari node not receiving my HT

 

There are new updates for ASL3 available.? Please apply them.

Here are the settings for the SA818 and simpleusb that I am using for ASL3.? Please try them.


Re: ASL3 DTMF not recognized

 

There are new updates for ASL3 available.? Be sure to apply them.


Re: ASL3 DTMF not recognized

 

You need to enable pre-emphasis/deemphasis.? You can do this in the SA818 or in simple USB.? You also need the PLfilter(simpleusb) or thehigh pass filter (SA818) enabled to filter out the CTCSS tone.

I prefer to do the filtering in the SA818.? Here are the settings I am using:


Re: ASL3 DTMF not recognized

 

Thanks for all of the help so far.? Here are my settings.? Let me know if you need more.

Joe

Speed is default


Shari node not receiving my HT

 

¿ªÔÆÌåÓý

Good afternoon,


On Monday I received my Shari USB radio that I use on a Pi4B. It works well in Hamvoip, but not in ASL V3.


I got all kinds of errors while programming it via the sa818-menu, untill I changed it to /dev/tty0USB. Now I can hear Allison talking. When keying up, however, there is nothing happening. I checked asterisk -rv, but nothing is coming in. All the settings on the HT (RT3S) I'm using, is correct, because it works in Hamvoip. ASL V3 also works with Repeater Phone on iOS.


Any ideas?


Below are some screenshots of simple USB and sa818-menu.


sa818-menu
-- 














simple usb
73 (Kind regards),
Hendrik (ZS6HBS)
Please visit my QRZ page at 


Re: ASL3 DTMF not recognized

 

Please post screen clips of your simpleUSB and SA818 settings?


Re: ASL3 DTMF not recognized

 

Here is a connect command to node 534630 that fails. Note the second "3" has a problem and the error is repeatable.? ?They sound fine on the radio (ID-50A) and DTMF speed is set to 300 ms in the radio.? The earlier post was just my running through all the keys.? ? Interestingly if I do the same on my AnyTone 878 UVII where I use the keypad the commands work fine

[2024-07-10 13:47:26.959] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '*' received on SimpleUSB/59753
[2024-07-10 13:47:26.959] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '*' on SimpleUSB/59753
[2024-07-10 13:47:27.257] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '*' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 13:47:27.257] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '*' on SimpleUSB/59753
[2024-07-10 13:47:27.257] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '*' on SimpleUSB/59753
[2024-07-10 13:47:27.620] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:27.620] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:27.855] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 235 ms
[2024-07-10 13:47:27.855] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 13:47:27.855] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:28.175] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 13:47:28.175] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 13:47:28.473] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 13:47:28.473] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 13:47:28.473] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 13:47:28.858] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:28.858] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:28.985] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 127 ms
[2024-07-10 13:47:28.985] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 13:47:28.985] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:29.369] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '4' received on SimpleUSB/59753
[2024-07-10 13:47:29.370] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '4' on SimpleUSB/59753
[2024-07-10 13:47:29.669] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '4' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 13:47:29.669] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '4' on SimpleUSB/59753
[2024-07-10 13:47:29.669] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '4' on SimpleUSB/59753
[2024-07-10 13:47:29.968] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '6' received on SimpleUSB/59753
[2024-07-10 13:47:29.968] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '6' on SimpleUSB/59753
[2024-07-10 13:47:30.266] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '6' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 13:47:30.266] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '6' on SimpleUSB/59753
[2024-07-10 13:47:30.266] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '6' on SimpleUSB/59753
[2024-07-10 13:47:30.833] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:30.833] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 1 ms
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3960 __ast_read: DTMF end '3' detected to have actual duration 1 on the wire, emulation will be triggered on SimpleUSB/59753
[2024-07-10 13:47:30.834] DTMF[3892]: channel.c:3967 __ast_read: DTMF end '3' has duration 1 but want minimum 80, emulating on SimpleUSB/59753
[2024-07-10 13:47:30.835] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 13:47:30.835] DTMF[3892]: channel.c:4012 __ast_read: DTMF begin ignored '3' on SimpleUSB/59753
[2024-07-10 13:47:30.854] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 19 ms
[2024-07-10 13:47:30.912] DTMF[3892]: channel.c:4042 __ast_read: DTMF end emulation of '3' queued on SimpleUSB/59753
[2024-07-10 13:47:31.132] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 19 ms
[2024-07-10 13:47:31.132] DTMF[3892]: channel.c:3921 __ast_read: DTMF begin emulation of '3' with duration 80 queued on SimpleUSB/59753
[2024-07-10 13:47:31.153] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '0' received on SimpleUSB/59753
[2024-07-10 13:47:31.153] DTMF[3892]: channel.c:4012 __ast_read: DTMF begin ignored '0' on SimpleUSB/59753
[2024-07-10 13:47:31.213] DTMF[3892]: channel.c:4100 __ast_read: DTMF end emulation of '3' queued on SimpleUSB/59753
[2024-07-10 13:47:31.461] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '0' received on SimpleUSB/59753, duration 308 ms
[2024-07-10 13:47:31.461] DTMF[3892]: channel.c:3921 __ast_read: DTMF begin emulation of '0' with duration 308 queued on SimpleUSB/59753
[2024-07-10 13:47:31.781] DTMF[3892]: channel.c:4100 __ast_read: DTMF end emulation of '0' queued on SimpleUSB/59753

Here is trying to connect to *355553 again a problem with the "3"

[2024-07-10 14:03:33.953] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '*' received on SimpleUSB/59753
[2024-07-10 14:03:33.953] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '*' on SimpleUSB/59753
[2024-07-10 14:03:34.251] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '*' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 14:03:34.251] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '*' on SimpleUSB/59753
[2024-07-10 14:03:34.251] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '*' on SimpleUSB/59753
[2024-07-10 14:03:34.571] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:34.571] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 42 ms
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3960 __ast_read: DTMF end '3' detected to have actual duration 42 on the wire, emulation will be triggered on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:3967 __ast_read: DTMF end '3' has duration 42 but want minimum 80, emulating on SimpleUSB/59753
[2024-07-10 14:03:34.614] DTMF[3892]: channel.c:4100 __ast_read: DTMF end emulation of '3' queued on SimpleUSB/59753
[2024-07-10 14:03:34.675] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:34.675] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:34.775] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 99 ms
[2024-07-10 14:03:34.775] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:34.775] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:35.169] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:35.169] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:35.467] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 298 ms
[2024-07-10 14:03:35.467] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:35.467] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:35.766] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:35.766] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.065] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 14:03:36.065] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:36.065] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.363] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:36.363] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.663] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 14:03:36.663] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:36.663] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:36.982] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '5' received on SimpleUSB/59753
[2024-07-10 14:03:36.982] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:37.282] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '5' received on SimpleUSB/59753, duration 299 ms
[2024-07-10 14:03:37.282] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '5' on SimpleUSB/59753
[2024-07-10 14:03:37.282] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '5' on SimpleUSB/59753
[2024-07-10 14:03:37.580] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:37.580] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.687] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 107 ms
[2024-07-10 14:03:37.687] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:37.687] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.747] DTMF[3892]: channel.c:4008 __ast_read: DTMF begin '3' received on SimpleUSB/59753
[2024-07-10 14:03:37.747] DTMF[3892]: channel.c:4019 __ast_read: DTMF begin passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.827] DTMF[3892]: channel.c:3894 __ast_read: DTMF end '3' received on SimpleUSB/59753, duration 80 ms
[2024-07-10 14:03:37.827] DTMF[3892]: channel.c:3945 __ast_read: DTMF end accepted with begin '3' on SimpleUSB/59753
[2024-07-10 14:03:37.827] DTMF[3892]: channel.c:3983 __ast_read: DTMF end passthrough '3' on SimpleUSB/59753
[2024-07-10 14:03:37.827] WARNING[3892]: channel.c:6332 request_channel: No channel type registered for 'echolink'
[2024-07-10 14:03:37.827] WARNING[3892]: app_rpt/rpt_link.c:728 connect_link: Unable to place call to echolink/el0/555533
? ? -- Hungup 'DAHDI/pseudo-462280106'
[2024-07-10 14:03:48.001] WARNING[3889]: res_rpt_http_registrations.c:148 curl_post: Failed to connect to register.allstarlink.org port 443 after 1000 ms: Timeout was reached
[2024-07-10 14:03:48.001] WARNING[3889]: res_rpt_http_registrations.c:150 curl_post: Failed to curl URL 'https://register.allstarlink.org/'



Re: ASL3 DTMF not recognized

 

Are you starting each command with an asterisk "*"?? (i.e. *70 for status or *355553 for the level check parrot node)


Re: ASL3 DTMF not recognized

 

Well looks like asterisk detecting your dtmf. What is the output on asterisk cli when you send connect dtmf from your radio?


Re: ASL3 echolink

 

On Wed, Jul 10, 2024 at 07:58 AM, Sander [VK6PI] wrote:
I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.
There's a ASL3 bug that prevents you from connecting to 4/5 digit EchoLink nodes. ?The fix should be out real soon. ?If you want to test your setup without the fix then try connecting to 6-digit node (with no leading zeros) like?ARRLNEWS, #826983.


Re: ASL3 echolink

 

I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.

Any thoughts on how to tackle this problem?

73
Sander


On Tue, 9 Jul 2024 at 12:18, Patrick Perdue via <borrisinabox=[email protected]> wrote:
The firewall problem has been resolved in the latest asl3-appliance package update a couple of days ago. Just install the package maintainers version of ?firewall.xml, and the zone should exist from that point.
Sent from my zippo


On Jul 8, 2024, at 21:44, Omar Asfour via <ve3kdc=[email protected]> wrote:

?Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.


After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73