# Echolink not active after a power down **URL:** \ **Category:** AllStarLink\ **Created:** [November 4, 2020, 6:46pm UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772 "2020-11-04T18:46:21Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![WB2HKK](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wb2hkk/32/843_2.png) [@WB2HKK](https://community.allstarlink.org/u/WB2HKK)\ **Post date:** [November 4, 2020, 6:46pm UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/1 "2020-11-04T18:46:21Z")
When I shutdown the Pi, and remove power, upon a restart our echolink node is not listed for connection. If I then restart Asterisk from a CLI prompt, it is back?? ---
**Author:** ![K6CBR](https://community.allstarlink.org/user_avatar/community.allstarlink.org/k6cbr/32/1616_2.png) [@K6CBR](https://community.allstarlink.org/u/K6CBR)\ **Post date:** [November 5, 2020, 7:52am UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/2 "2020-11-05T07:52:14Z")
What version of OS did you install? Sounds like the echolink chan is loading too early and failing on a boot. ---
**Author:** ![WB2HKK](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wb2hkk/32/843_2.png) [@WB2HKK](https://community.allstarlink.org/u/WB2HKK)\ **Post date:** [November 5, 2020, 1:41pm UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/3 "2020-11-05T13:41:13Z")
I am using the 2017 ’ Debian Jessie ’ version. Too many issues with ASL, I could never get it to work more than a day without failing. ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [November 8, 2020, 8:44pm UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/4 "2020-11-08T20:44:43Z")
I have probs w EL as well- works after reboot for a period of time but eventually loses connection. Wondering if there is a command I could use over DTMF to restart the EL driver or some way to re-initialize connection to EL servers. Any tips appreciated. ---
**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:** [November 26, 2020, 5:37pm UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/5 "2020-11-26T17:37:57Z")
Nothing for EL in particular that I know of. You can try to restart asterisk from the command line or reload the dialplan from inside of asterisk. Perhaps the network is slow or packet loss on boot ? Like from a lot of wifi activity if you are using wifi. Just suggesting things to look at. But I would add that ‘display’ of connection to EL severs is not immediate. Could take 10/15min ? You may not have a issue other than being in a hurry LOL ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [November 29, 2020, 3:59am UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/6 "2020-11-29T03:59:35Z")
Thanks. The EL connection will be working fine, but after a length of time it will stop. Could be hours could be days I have not tested it. Restarting asterisk does indeed work but that is inconvenient. Maybe a script to restart asterisk daily at 5am or something? ---
**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:** [November 29, 2020, 6:14am UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/7 "2020-11-29T06:14:34Z")
Well, in that case, I would try a minumum that will fix the issue. Reload the dialplan would be my first choice if it works to bring it back. There are so many things it could be causing your problem, you are just going to have to rule them out one at a time. And the hardest one to prove is more likely. Your ISP. So be careful how far out the the way you go to make it work. But a warm boot… set a command to =cop,1 run it from the system sched when you want. Or write a script to execute- asterisk -rx reload XXX=cmd,/some/were/in/your/filesystem.sh ;example to call a script by dtmf command - set to scheduler. But hang in there, perhaps someone has had a near issue and can give better insight than mine. But you might tell us if your connection is on wifi ? ---
**Author:** ![WB2HKK](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wb2hkk/32/843_2.png) [@WB2HKK](https://community.allstarlink.org/u/WB2HKK)\ **Post date:** [November 29, 2020, 1:46pm UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/8 "2020-11-29T13:46:50Z")
All very good suggestions. For me, I do not power down often, but when I do I just check for Echolink availability and restart asterisk if necessary. ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [January 20, 2021, 3:07am UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/9 "2021-01-20T03:07:21Z")
connection is ethernet thx ---
**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:** [January 20, 2021, 3:59am UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/10 "2021-01-20T03:59:30Z")
Might I ask if you have SIP enabled and running ? ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [March 18, 2021, 5:33am UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/11 "2021-03-18T05:33:02Z")
not sure- will look it up- thx ---
**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:** [March 21, 2021, 12:25am UTC](https://community.allstarlink.org/t/echolink-not-active-after-a-power-down/17772/12 "2021-03-21T00:25:01Z")
I am reminded once again from a recent reply on some other EL issue I made. It is often overlooked and the cause of many issues. Echolink will only allow 1 connection per IP address. Most smartphones will run echolink in the background by default. So, once your EL connection on your server is broken from a restart etc… The phone is likely making the connection and that causing a blocking the servers new attempt to initialize a log-in. Remedy ? Turn the wifi off on your phone to force the phone to use cell carrier and not you local nat. This would stop the cell from succeeding a connection during your servers reboot. If you find that is the issue, I would set the phone so it will not allow the EL program to run in the background and only when it is in the foreground. Then you could leave the phones wifi on. Now, don’t be fooled. It may look like both can log-in, but only the first one will be able to communicate from that IP address.