Published: November 16, 2025

If you’ve upgraded to ASL3 (AllStarLink on Asterisk 20+), you may have run into this frustrating issue:

“User talks too long → timeout → transmission drops → node won’t come back, even when they unkey. I have to key up locally to reset it!”

Good news: This isn’t a bug — it’s a safety feature in ASL3 to prevent stuck carriers from RF loops or bad USB devices. But for hub operators, it feels like a step backward from ASL2’s smooth recovery.

The Problem (Default ASL3 Behavior)

totime = 180000        ; 3 minutes

• User talks > 3 min → timeout
• TX drops → PTT locks
• Remote unkeys → node stays silent
• Only local key-up resets the channel

The Fix: Just 3 Lines in rpt.conf

totime = 360000        ; 6 minutes (adjust as needed)
timeoutmacro = *1      ; Auto-reset on timeout
lnkactenable = 0       ; Disable link activity timer

And add this macro at the top of your rpt.conf:

[macros]
*1 = cmd,/usr/bin/rpt reset

Why This Works

Apply Without Restart

sudo asterisk -rx "module reload app_rpt.so"

No downtime. No reboot.

Result

Exactly like ASL2 — but with ASL3’s stability.

Pro Tip: Add a 30-Second Warning Beep

Want users to know timeout is coming?

timeoutmacro = *81 30

[macros]
*81 = p,/var/lib/asterisk/sounds/rpt/timeout-warning

Bottom Line

ASL3 isn’t broken — it’s just more cautious. With one macro and two settings, you get:

• Rock-solid timeouts
• Smooth, automatic recovery
• Happy users

Your hub stays live. Your net stays smooth.

Tested on ASL3 v3.0.0, Debian 12, DVSwitch hubs. Always test during a quiet net first.

Got a stuck node? Drop these lines in rpt.conf and reload. Problem solved.

Dows this fix it let me know. If you find a better option please comment.

KJ5MZL/WRXB288

The post AllStarLink ASL3 Timeout Fix first appeared on Louisiana Nationwide.