# Creeping delay using usbradio on ASL3 3.10.4

**URL:** <https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954>\
**Category:** AllStarLink\
**Created:** [August 27, 2026, 12:31pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954 "2026-08-27T12:31:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![N2DYI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n2dyi/32/1712_2.png) [@N2DYI](https://community.allstarlink.org/u/N2DYI)\
**Post date:** [August 27, 2026, 12:31pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/1 "2026-08-27T12:31:05Z")

</div>

\*\*\*\*\*\*\*\*\*\* AllStarLink [ASL] Version Info \*\*\*\*\*\*\*\*\*\*

OS : Debian GNU/Linux 13 (trixie)  
OS Kernel : 6.18.39+rpt-rpi-v8

Asterisk : 22.10.1+asl3-3.10.4-1.deb13  
ASL [app\_rpt] : 3.10.4

Installed ASL packages :

Package Version  
============================== ==============================  
allmon3 1.9.1-1.deb13  
asl3 3.18.2-2.deb13  
asl3-appliance 2.2.0-1.deb13  
asl3-appliance-pi 2.2.0-1.deb13  
asl3-asterisk 2:22.10.1+asl3-3.10.4-1.deb13  
asl3-asterisk-config 2:22.10.1+asl3-3.10.4-1.deb13  
asl3-asterisk-modules 2:22.10.1+asl3-3.10.4-1.deb13  
asl3-menu 1.18-1.deb13  
asl3-tts 1.0.1-1.deb13  
asl3-update-nodelist 2.1.0-1.deb13  
asl-apt-repos 2.0-1.deb13  
cockpit 337-1+deb13u1  
cockpit-bridge 337-1+deb13u1  
cockpit-networkmanager 337-1+deb13u1  
cockpit-packagekit 337-1+deb13u1  
cockpit-sosreport 337-1+deb13u1  
cockpit-storaged 337-1+deb13u1  
cockpit-system 337-1+deb13u1  
cockpit-wifimanager 2.0-1.deb13  
cockpit-ws 337-1+deb13u1  
dahdi 1:3.1.0-2.1  
dahdi-linux 1:3.4.0-11.asl.deb13

Using ASL3 3.10.4 beta, when Asterisk is freshly restarted, I noticed that the audio latency was longer than it used to be on older versions before the switch to portaudio.

I upgraded my node yesterday morning, then left it sitting in monitor mode on a node all day.

When I checked this morning, audio was about 7 seconds behind real time when comparing to another local node running 3.9.3, also using usbradio. PTT was firing when it should, but audio was extremely delayed, meaning a transmission would be seemingly cut off about 7 seconds too soon when PTT dropped.

If someone keyed during the window when my node wasn't transmitting, I'd get the remainder of the previous transmission, silence, then the start of the next one all in the same transmission.

This is on a simplex node.

Received audio seems to be OK. Only transmitted audio is affected.

It gradually became more and more delayed over time.

Restarting Asterisk (mostly) fixes it, but latency is still not quite what it was at it's best with 3.9.3 and older.

---

<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:** [August 27, 2026, 7:15pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/2 "2026-08-27T19:15:30Z")

</div>

Interesting ... and it does look like we're slowly collecting transmit audio frames.

---

<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:** [August 27, 2026, 7:20pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/3 "2026-08-27T19:20:46Z")

</div>

Q? you commented that you monitoring a single node all day.

- was this a single connection over the entire time interval?
- or were you connecting / disconnecting during the day?
- and would other nodes have been connecting / disconnecting from your node during the day?

---

<div class="post-metadata">

**Author:** ![N2DYI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n2dyi/32/1712_2.png) [@N2DYI](https://community.allstarlink.org/u/N2DYI)\
**Post date:** [August 27, 2026, 8:40pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/4 "2026-08-27T20:40:56Z")

</div>

This node can't currently accept incoming connections. CGNAT with no compensation, currently. It is set up for that but is not currently active, so no one can connect or disconnect from my node. I literally just left it in monitor mode on a single mode all day and touched nothing. No commands, no transmitting to the node, just monitor mode and ran away, basically.

> **···**
>
> Sent from my zippo
> 
> > On Aug 27, 2026, at 16:21, Allan N [noreply@community.allstarlink.org](mailto:noreply@community.allstarlink.org) wrote:
> 
> > Someone replied to a topic you are Watching.
> > 
> > > ![](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/45/3123_2.png "WA3WCO") | [WA3WCO](https://community.allstarlink.org/u/wa3wco) ASL Community Admin  
> > > August 27 |
> > > 
> > > - | - |
> > 
> > Q? you commented that you monitoring a single node all day.
> > 
> > - was this a single connection over the entire time interval?
> > - or were you connecting / disconnecting during the day?
> > - and would other nodes have been connecting / disconnecting from your node during the day?
> > 
> > * * *
> > 
> > [Visit Topic](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/3) or reply to this email to respond.
> > 
> > You are receiving this because you enabled mailing list mode.
> > 
> > To unsubscribe from these emails, click here.

---

<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:** [August 27, 2026, 9:46pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/5 "2026-08-27T21:46:41Z")

</div>

> [@N2DYI](#):
>
> I literally just left it in monitor mode on a single mode all day and touched nothing.

Thank you for your reply. Mike and I have been looking at the code, discussing possibilities ... and I'm starting to work up some code changes 🙂

---

<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:** [August 28, 2026, 3:29pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/6 "2026-08-28T15:29:15Z")

</div>

I too want to thank you for testing and letting us know. These types of bugs can be difficult to find/notice. We should have a fix soon.

---

<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:** [August 29, 2026, 8:29pm UTC](https://community.allstarlink.org/t/creeping-delay-using-usbradio-on-asl3-3-10-4/24954/7 "2026-08-29T20:29:27Z")

</div>

We made a few changes that should help reduce the delay. The updated **asl3-asterisk 22.10.1+asl3-3.10.5-1** packages are now in the "beta" stream.
