# Cmd not working in ASL3?

**URL:** <https://community.allstarlink.org/t/cmd-not-working-in-asl3/22681>\
**Category:** AllStarLink\
**Created:** [January 12, 2025, 6:11pm UTC](https://community.allstarlink.org/t/cmd-not-working-in-asl3/22681 "2025-01-12T18:11:18Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![AH6LE](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ah6le/32/1817_2.png) [@AH6LE](https://community.allstarlink.org/u/AH6LE)\
**Post date:** [January 13, 2025, 9:56pm UTC](https://community.allstarlink.org/t/cmd-not-working-in-asl3/22681/7 "2025-01-13T21:56:11Z")

</div>

Arrrggh…

Contrary to the solution in this thread [https://community.allstarlink.org/t/cmd-in-rpt-conf-to-run-a-script/22105](https://community.allstarlink.org/t/cmd-in-rpt-conf-to-run-a-script/22105)

My ASL3 install does NOT run a script when called from rpt.conf.

Yes, the script has proper permissions set. Yes, the script runs fine when called from the shell. Yes, ASL3 is decoding the proper DTMF codes. No, ASL3 is not running the script when called.

I may just fall back to ASL2. This is a game killer for my linked system

---

_[View the full topic](https://community.allstarlink.org/t/cmd-not-working-in-asl3/22681)._