This Dave K5NX and we have a Linkbox 0070 experimental reflector and AllStar 27378 bridged running ASL3 together running on two different Vult machines.
For some reason the Linkbox just stops sending audio to the AllStar machine, but the Linkbox audio still works only on Linkbox but not to AllStar. The minute you key up the AllStar side then the audio from Linkbox starts back up over onto AllStar , they both work perfectly separately, but the bridge seems to drop when idle or it's going to sleep? I've had a couple opinions say it's the tlb driver on the AllStar side. Do you have any suggestions?
Linkbox dashboard this machine is running Debian 11 X64 bit
===== core show version =====
ActionID: cpAction_1397635423
Message: Command output follows
Output: Asterisk 22.9.0+asl3-3.9.3-1.deb13 built by builder @ allstarlink.org on a x86_64 running Linux on 2026-05-28 18:41:49 UTC
Command: /bin/date
-----------------------------------------------------------------
Mon Jun 29 09:42:46 CDT 2026
Command: export TERM=vt100 && sudo /usr/local/sbin/supermon/ssinfo -
-----------------------------------------------------------------
HOST: 27378-AllStar-Hub - PC, TURBO-Mode enabled
CPU: Intel Core Processor (Broadwell, no TSX, IBRS)
Memory: 984MB
Swap: 2399MB
Storage Devices: /dev/vda: 25 GiB, 26843545600 bytes, 52428800 sectors
OS Version: Debian GNU/Linux (Installed on 17Apr2026)
Domain: Standalone(systemd)
Host ID: 007f0100
Location: Kingwood Texas
System: 27378 AllStar Virtual HUB
Service: AllStarLink/EchoLink/IRLP/Digital - Radio Bridging Control Center
Uptime: 1 days
Primary User: linuxuse 22Jun2026
Flags: None
Seems like i'm not the only one having this issue. I had to create a USRP node on my allstar node and connect it to my TLB server, and I have a cron job that disconnects and reconnects every hour just to be able to keep voice packets flowing from my linkbox server to my allstar node.
Yeah, it's been like this for years. When I tried using TLB in 2019, it did the same thing. Tried it again a couple of years later, no difference, so I gave up trying to use it. Too bad, because it would theoretically be a better way to bridge my Echolink conference server (thebridge) than the way I'm doing it now, which is to use a dedicated -R node bridging back to the conference server. It's really reliable like that, though, and I have never achieved that kind of reliability with either ASL or HamVoIP's TLB module.
I prefer hosting Echolink connections from a conference rather than direct from ASL3. Well, I'd prefer not to use Echolink at all, but I support it on my system for those who need it.
I've also seen the same issues for years. It is frustrating, and the only somewhat reliable way of bridging in tlb is to use Echolink, which means having an extra Echolink node registered.
chan_tlb is very unreliable, and tlb (unfortunately) doesn't speak USRP, which would be a neat way to resolve the issue. For my use cases, where I run my systems around a USRP core, the latter would be the best solution.
My ASL1 machine with Deb9 stretch 32 system tlb channel driver (client) works Perfect connecting to my new Deb13 trixie with TLB daemon binary (server)!
Something appears to be broken in ASL3 with the tlb channel driver (client)!
Something appears to be broken in ASL3 with the tlb channel driver (client)!
First off, we track bug reports and feature requests in GitHub. Can someone please create an issue in GitHub : app_rpt : Issues. Please include as many details as you can about how to setup a TLB server, how you have your ASL node configured (rpt.conf, tlb.conf, extensions,conf, etc), and include as many details about how to reproduce the problem(s). If we can't reproduce what's reported then we have no idea if any changes we might make would make a difference.
Is that going to get the problem fixed? Not right away but at least it will be tracked.
What would help get the issue(s) resolved sooner? Ideally, someone who is (or is willing to become) familiar with TLB code will step up and help us out. All of the source code is available and we can certainly help you out with building/compiling asterisk+app_rpt+chan_tlb. Remember, you know how TLB works, you've got TLB servers already setup, you know how to make TLB connections, and you know when everything is (and is not) behaving as expected. That puts you way ahead of us.
Sorry, I didn't make myself clear. I want a link to download that dashboard. If I click on a link with PHP, the source code doesn't download; instead, the PHP runs and the dashboard appears. I hope I've explained myself clearly.