Echolink stopped working after update

Is there anything in the latest update to stop Echolink from working? After update I can connect but connection drops after 6 seconds or so. Everything looks ok in the cnf files.

This is what I get after connecting to GB3KC repeater direct from Allscan. Does the same from rf DTMF as well, any ideas ?

Connected to Asterisk 22.2.0+asl3-3.4.3-1.deb12 currently running on Allstarlink (pid = 1140)
== Manager 'admin' logged on from 127.0.0.1
== Manager 'admin' logged off from 127.0.0.1
-- Hungup 'DAHDI/pseudo-1282962505'
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Hungup 'DAHDI/pseudo-1525939677'
-- Hungup 'DAHDI/pseudo-444072230'
-- <DAHDI/pseudo-818389090> Playing 'custom/phonetic/g_p.ulaw' (language 'en')
-- <DAHDI/pseudo-818389090> Playing 'custom/phonetic/b_p.ulaw' (language 'en')
-- <DAHDI/pseudo-818389090> Playing 'custom/digits/3.ulaw' (language 'en')
-- <DAHDI/pseudo-818389090> Playing 'custom/phonetic/k_p.ulaw' (language 'en')
-- <DAHDI/pseudo-818389090> Playing 'custom/phonetic/c_p.ulaw' (language 'en')
-- <DAHDI/pseudo-818389090> Playing 'custom/letters/dash.ulaw' (language 'en')
-- <DAHDI/pseudo-818389090> Playing 'custom/phonetic/r_p.ulaw' (language 'en')
-- <DAHDI/pseudo-818389090> Playing 'custom/rpt/connection_failed.gsm' (language 'en')
-- Hungup 'DAHDI/pseudo-818389090'
== Manager 'admin' logged on from 127.0.0.1
== Manager 'admin' logged off from 127.0.0.1
-- Hungup 'DAHDI/pseudo-983323823'
-- Hungup 'DAHDI/pseudo-255567408'
-- <DAHDI/pseudo-1746409052> Playing 'custom/phonetic/g_p.ulaw' (language 'en')
-- <DAHDI/pseudo-1746409052> Playing 'custom/phonetic/b_p.ulaw' (language 'en')
-- <DAHDI/pseudo-1746409052> Playing 'custom/digits/3.ulaw' (language 'en')
-- <DAHDI/pseudo-1746409052> Playing 'custom/phonetic/k_p.ulaw' (language 'en')
-- <DAHDI/pseudo-1746409052> Playing 'custom/phonetic/c_p.ulaw' (language 'en')
-- <DAHDI/pseudo-1746409052> Playing 'custom/letters/dash.ulaw' (language 'en')
-- <DAHDI/pseudo-1746409052> Playing 'custom/phonetic/r_p.ulaw' (language 'en')
-- <DAHDI/pseudo-1746409052> Playing 'custom/rpt/connection_failed.gsm' (language 'en')
-- Hungup 'DAHDI/pseudo-1746409052'

Just a lead to check...

Do you also have a cellphone or pc also logged in to the echolink servers that is using your NAT
(both behind the router)
EL only allows one reg per WAN IP address and cellphones by default allow EL program to run in background. So you may not realize it is blocking your asl server for EL.

Hi, thanks for the reply but no , not got any other machine/system other than Allstarlink on the router, it worked fine before I updated to the latest today.

I am also encountering connection failures with EchoLink after the update released yesterday. This is occurring on two separate nodes, one of which is a complete rebuild from scratch this morning.

=========================================================================
Connected to Asterisk 22.2.0+asl3-3.4.3-1.deb12 currently running on 451050 (pid = 1838)
  == Manager 'admin' logged on from 127.0.0.1
  == Manager 'admin' logged off from 127.0.0.1
    -- Hungup 'DAHDI/pseudo-1742299252'
    -- Hungup 'DAHDI/pseudo-932753248'
    -- Hungup 'DAHDI/pseudo-519510088'
    -- <DAHDI/pseudo-505639091> Playing 'custom/rpt/node.gsm' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/digits/3.ulaw' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/digits/0.ulaw' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/digits/0.ulaw' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/digits/9.ulaw' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/digits/9.ulaw' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/digits/9.ulaw' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/digits/9.ulaw' (language 'en')
    -- <DAHDI/pseudo-505639091> Playing 'custom/rpt/connection_failed.gsm' (language 'en')
    -- Hungup 'DAHDI/pseudo-505639091'

Looks like we broke outbound echolink calls in the latest update.
If you need outbound you should rollback.
We are actively working on this as I type.

Thats easy for you to say 'rollback' :joy: . I've done a restore from the back up from before the update but its still the same , how do you do a rollback ?

As root:

apt install asl3-asterisk=2:22.2.0+asl3-3.3.0-6.deb12 asl3-asterisk-modules=2:22.2.0+asl3-3.3.0-6.deb12 asl3-asterisk-config=2:22.2.0+asl3-3.3.0-6.deb12
1 Like

Thank you for the rollback information. I have successfully rolled back both of my nodes.

Yep, thanks from this side aswell , all up and running again :+1:

A new set of ASL3 packages that should take care of the EchoLink connection issues are now available in our "beta" channel.

Please refer to the ASL3 Manual : Beta Testing page for details on installing the updated packages.

1 Like

Performed a one-time installation of the packages from the beta channel on one of my nodes. No issues when connecting to EchoLink. I'll update the other node later this afternoon.

Thank you for installing the 3.4.4 packages. A few more positive (and no negative) confirmations and I'll push the packages out to everyone.

1 Like

Confirming installed beta channel and echolink issues are resolved (was experiencing crashing of node when someone connected via EL) thanks to all of the devs on squashing this bug!

Installing beta now, should have some EL multi-user traffic tomorrow night...

No issues seen tonight on beta during a Net. FWIW

Nate WY0X

A few more issues showed up in the [3.4.4] "beta" packages that I mentioned a few days ago. These included one related to "incoming" EchoLink connections and a crasher when monitoring more than one active node. These issues have been fixed and I just pushed a new set of [3.4.5] packages to our "beta" channel.

Please refer to the ASL3 Manual : Beta Testing page for details on installing the updated packages.

Applied the aforementioned "beta" packages yesterday evening. Will advise of any problems encountered.

Thanks.