I've set up a node to connect to EchoLink. It logs in OK, and I can connect out to 009999 OK. However, when I try to connect in from an EchoLink running on my mobile (using a VPN, so not on the same network), I see the following:
-- Executing [YYYYYY@radio-secure:1] Set("echolink/el0-3", "NODENUM=XXXXXX") in new stack
-- Executing [YYYYYY@radio-secure:2] NoOp("echolink/el0-3", "Connect from node XXXXXX to node YYYYYYY using echolink") in new stack
-- Executing [YYYYYY@radio-secure:3] ExecIf("echolink/el0-3", "0?Hangup") in new stack
-- Executing [YYYYYY@radio-secure:4] GotoIf("echolink/el0-3", "0?:allowlist") in new stack
-- Goto (radio-secure,YYYYYY,7)
-- Executing [YYYYYY@radio-secure:7] GotoIf("echolink/el0-3", "0?denylist") in new stack
-- Executing [YYYYYY@radio-secure:8] GotoIf("echolink/el0-3", "0?connect") in new stack
-- Executing [YYYYYY@radio-secure:9] NoOp("echolink/el0-3", "YYYYYY not in allowlist, Hangup") in new stack
-- Executing [YYYYYY@radio-secure:10] Hangup("echolink/el0-3", "") in new stack
== Spawn extension (radio-secure, YYYYYY, 10) exited non-zero on 'echolink/el0-3'
> Received OK from Echolink server nasouth.echolink.org.
> Received OK from Echolink server servers.echolink.org.
> Directory completed downloading(partial,compressed), 970 records.
The key line seems to be
-- Executing [YYYYYY@radio-secure:9] NoOp("echolink/el0-3", "YYYYYY not in allowlist, Hangup") in new stack
I don't have permit or deny setup in echolink.conf