search

AllStarLink / ASL3

AllStarLink Version 3
https://www.allstarlink.org
GNU Affero General Public License v3.0
18 stars 3 forks source link

Unable to connect to EchoLink node #77

Closed jetski28 closed 4 months ago

jetski28 commented 5 months ago

Describe the bug Cannot connect to EchoLink node and get the following error in the logs... WARNING[1215][C-00000012] pbx.c: Channel 'echolink/el0-4' sent to invalid extension but no invalid handler: context,exten,priority=radio-secure,55,1

To Reproduce Steps to reproduce the behavior:

  1. Configure rpt.conf with node 55 instead of 1999
  2. Configure echolink.conf with our Echolink details
  3. Configure extensions.conf with NODE = 55
  4. Restart ASL

Expected behavior External users to be able to connect to Echolink node

Screenshots N/A

Software versions (listed in asl-menu, option 4)

Have you run a software update and rebooted? YES

What is the platform - e.g. Raspberry Pi 4, Raspberry Pi 5, Virtual Machine, Desktop, etc. Debian 12 on Proxmox

Additional context I compared configuration with our working ASL2 node. As a workaround, I replaced [radio-secure] configuration under extensions.conf with the following one line and now users can connect to Echolink node. It seems something with the default [radio-secure] configuration is preventing echolink conncetions. exten => ${NODE},1,rpt,${NODE}

tsawyer commented 5 months ago

Node number 55 is not a valid node number. The current usage of private node numbers should be at least 4 digits and start with 1. Please try another node number perhaps 1055 and test.

jetski28 commented 4 months ago

I see, moved it to 1055 and appears to be working.