i am attempting to deny connections from an echolink station and it is not working, anyone have any ideas, i have went into my echolink.conf and added deny KF0FPO but he keeps connecting.
Just a thought but after modifying the deny list did you restart asterisk?
GeorgeC W2DB
If you're talking about using the allow/deny lists you have to block by the Echolink node number prefixed by a "3". For example, look up the callsign like echolink dbget callsign KF0FPO-R and you'll get a six-digit number in the first column in the response. Then prefix it with a 3 and use that full seven-digit number for the deny.
Alternatively, you can put a comma-separated list of callsigns or glob expressions in deny= in /etc/asterisk/echolink.conf. You do have to restart after this change.
I did do a restart, when i lookup KF0RPO using that command, it gives me nothing found, when i look it up on echolink’s website i get “185019” so i would enter 3185019 in the node black list?
1 Like
Yes, this is correct.
I have done that and I have restarted but yet he still manages to reconnect
Try blocking in echolink.conf as I suggested. I have some blocks for that and it works fine.
I have kf0fpo on the deny list for echo link.conf
That must be frustrating. This is not a block/allow type solution, but if you only use your Echolink for outgoing calls anyway, consider attaching your Echolink to your private node 1999. Then, connect your main node to your private node as you wish. Your pest will be sitting on your 1999 but it will not affect your main node.
1 Like
On ASL3, echolink.conf uses “context = radio-secure” for processing in extensions.conf, I have been using the “allowlist” or “denylist” in the asterisk database for both Allstar and EchoLink nodes. I would expect in your case, you could run a command like below to add EchoLink node 3185019 to the asterisk database denylist for your node 62225.
asterisk -rx "database put denylist/62225 3185019 KF0FPO"
If you allow web transceiver connections, you may want to add their callsign too.
asterisk -rx "database put denylist/62225 KF0FPO WTMode"
David, WD5M
i went into the command line, and i entered that command, i got back asterisk -rx command not found
To access the asterisk CLI you would use sudo asterisk -rx ....
But, in this case, you could also use asl-menu:
sudo asl-menu
- Node Settings
- Allstar Node Setup Menu
- Update
- Node access list
did anyone work out how to block the echolink stations thanks
There's a command line example above from WD5M.
From asl-menu it's under Node Settings-->AllStar Node Setup Menu-->Update node XXXXXX-->Node access list
The AllStarLink node number for an Echolink node is the Echolink node number with a "3" prepended, so
Echolink node 123456 = AllStarLink node 3123456
You use the AllStarLink node number or the callsign in the node acess lists.
The echolink.conf file has support for permit = and deny = statements.