# Echolink stopped working after update

**URL:** <https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177>\
**Category:** AllStarLink\
**Tags:** asl3\
**Created:** [April 23, 2025, 9:56am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177 "2025-04-23T09:56:49Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![G0TPZ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/g0tpz/32/3842_2.png) [@G0TPZ](https://community.allstarlink.org/u/G0TPZ)\
**Post date:** [April 23, 2025, 9:56am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/1 "2025-04-23T09:56:50Z")

</div>

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'

---

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [April 23, 2025, 11:40am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/2 "2025-04-23T11:40:02Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![G0TPZ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/g0tpz/32/3842_2.png) [@G0TPZ](https://community.allstarlink.org/u/G0TPZ)\
**Post date:** [April 23, 2025, 11:44am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/3 "2025-04-23T11:44:21Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![KD5KNR](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kd5knr/32/3975_2.png) [@KD5KNR](https://community.allstarlink.org/u/KD5KNR)\
**Post date:** [April 23, 2025, 8:08pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/4 "2025-04-23T20:08:20Z")

</div>

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.

```auto
=========================================================================
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'

```

---

<div class="post-metadata">

**Author:** ![N8RAW](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8raw/32/2906_2.png) [@N8RAW](https://community.allstarlink.org/u/N8RAW)\
**Post date:** [April 24, 2025, 1:01am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/5 "2025-04-24T01:01:38Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![G0TPZ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/g0tpz/32/3842_2.png) [@G0TPZ](https://community.allstarlink.org/u/G0TPZ)\
**Post date:** [April 24, 2025, 6:54am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/6 "2025-04-24T06:54:36Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [April 24, 2025, 1:34pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/7 "2025-04-24T13:34:06Z")

</div>

As root:

```auto
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

```

---

<div class="post-metadata">

**Author:** ![KD5KNR](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kd5knr/32/3975_2.png) [@KD5KNR](https://community.allstarlink.org/u/KD5KNR)\
**Post date:** [April 24, 2025, 5:38pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/8 "2025-04-24T17:38:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![G0TPZ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/g0tpz/32/3842_2.png) [@G0TPZ](https://community.allstarlink.org/u/G0TPZ)\
**Post date:** [April 25, 2025, 8:22am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/9 "2025-04-25T08:22:41Z")

</div>

Yep, thanks from this side aswell , all up and running again 👍

---

<div class="post-metadata">

**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\
**Post date:** [April 25, 2025, 5:08pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/10 "2025-04-25T17:08:21Z")

</div>

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](https://allstarlink.github.io/user-guide/betatest/) page for details on installing the updated packages.

---

<div class="post-metadata">

**Author:** ![KD5KNR](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kd5knr/32/3975_2.png) [@KD5KNR](https://community.allstarlink.org/u/KD5KNR)\
**Post date:** [April 25, 2025, 7:50pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/11 "2025-04-25T19:50:11Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\
**Post date:** [April 25, 2025, 8:16pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/12 "2025-04-25T20:16:23Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![N3fyi](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/e8c25b/32.png) [@N3fyi](https://community.allstarlink.org/u/N3fyi)\
**Post date:** [April 28, 2025, 2:50pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/13 "2025-04-28T14:50:03Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![WY0X](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/76d3ee/32.png) [@WY0X](https://community.allstarlink.org/u/WY0X)\
**Post date:** [April 29, 2025, 1:01am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/14 "2025-04-29T01:01:44Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![WY0X](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/76d3ee/32.png) [@WY0X](https://community.allstarlink.org/u/WY0X)\
**Post date:** [April 30, 2025, 2:25am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/15 "2025-04-30T02:25:54Z")

</div>

No issues seen tonight on beta during a Net. FWIW

Nate WY0X

---

<div class="post-metadata">

**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\
**Post date:** [April 30, 2025, 6:47pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/16 "2025-04-30T18:47:16Z")

</div>

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](https://allstarlink.github.io/user-guide/betatest/) page for details on installing the updated packages.

---

<div class="post-metadata">

**Author:** ![KD5KNR](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kd5knr/32/3975_2.png) [@KD5KNR](https://community.allstarlink.org/u/KD5KNR)\
**Post date:** [May 1, 2025, 11:51am UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/17 "2025-05-01T11:51:32Z")

</div>

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

Thanks.

---

<div class="post-metadata">

**Author:** ![G0TPZ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/g0tpz/32/3842_2.png) [@G0TPZ](https://community.allstarlink.org/u/G0TPZ)\
**Post date:** [May 5, 2025, 9:11pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/18 "2025-05-05T21:11:25Z")

</div>

Updated to 3.4.5 today, echolink is working fine.  
Thanks

---

<div class="post-metadata">

**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\
**Post date:** [May 8, 2025, 9:11pm UTC](https://community.allstarlink.org/t/echolink-stopped-working-after-update/23177/19 "2025-05-08T21:11:43Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
