# Node is receiving but not transmitting

**URL:** <https://community.allstarlink.org/t/node-is-receiving-but-not-transmitting/24268>\
**Category:** Third-Party Apps\
**Tags:** new-users\
**Created:** [February 14, 2026, 9:32pm UTC](https://community.allstarlink.org/t/node-is-receiving-but-not-transmitting/24268 "2026-02-14T21:32:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_VA3XDT](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/3d9bf3/32.png) [@David\_VA3XDT](https://community.allstarlink.org/u/David_VA3XDT)\
**Post date:** [February 14, 2026, 9:32pm UTC](https://community.allstarlink.org/t/node-is-receiving-but-not-transmitting/24268/1 "2026-02-14T21:32:53Z")

</div>

## Setup Information

_Use `sudo asl-show-version` to obtain this information from the console or SSH_

Asterisk Version: 22.7.0+asl3-3.7.1-1.deb13  
ASL3 Version: 3.7.1

## Inquiry

_I am new to this however in the last 3 weeks I have learned how to get DVMobile Switch to work,and now have installed the AllStarLink image to a Raspbery Pi 4B, o/s Debian GNU/Linux 13 (trixie) and OS Kernal 6.12.62+rpt-rpi-v8. I have registered the node (681561) and have attached a Baofeng UV-82 (I know, I know, it’s a Baofeng) with a new NA6D AIOC cable. I am setup with Radio interface ‘USBRadio’ and Duplex type ‘1’. I am using a second radio, Baofeng UV-82+ locally to connect to the set-up. I have fully tested the AIOC cable with a DigiPi._

I can connect to a local club node (49330) and can hear them. I can connect to a Parrot (55553) and can hear others’ test calls. The problem is TX. The radios appear to be functioning properly and the Allmon3 Monitoring Dashboard tells me I am transmitting, however it appears nothing is actually going our. Neither the club nor the Parrot ever respond.

Clearly my settings are off somewhere. The AIOC is set as the default audio device in the RPi, and the audio settings in the Pi are showing audio out settings at 81%. In the node settings, Transmit Voice Level is set at 750 currently.

I have googled and played with settings, but am stumped. Ideally I would love to be told of a simple, stupid mistake I have made, but will gratefully take any suggestions.

Thanks in advance

David VA3XDT; 681561

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [February 14, 2026, 10:00pm UTC](https://community.allstarlink.org/t/node-is-receiving-but-not-transmitting/24268/2 "2026-02-14T22:00:30Z")

</div>

Make sure you have the latest version of the AOIC and are running firmware 1.4. See this thread:

> [@Allstar node won't key up with AIOC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/25):
>
> SOLVED! I’ve got the v1.2 (hardware) board by s. Kuipper. All the guides had me flashing the AIOC v1.3x FW, but on his site, he specifically states that the v1.2 board REQUIRES v 1.4 and above firmware. I flashed it with 1.4 and now everything works. Thanks everyone!

---

<div class="post-metadata">

**Author:** ![David\_VA3XDT](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/3d9bf3/32.png) [@David\_VA3XDT](https://community.allstarlink.org/u/David_VA3XDT)\
**Post date:** [February 14, 2026, 10:09pm UTC](https://community.allstarlink.org/t/node-is-receiving-but-not-transmitting/24268/3 "2026-02-14T22:09:37Z")

</div>

Thanks for the suggestion. NA6D notes ‘NA6D shiped hardware v1.2 with firmware v1.4.1 since November 2025’, so I should be ok on that score. I just purchased it near the end of January. If necessary though, I am not adverse to re-flashing it.

David VA3XDT

---

<div class="post-metadata">

**Author:** ![David\_VA3XDT](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/3d9bf3/32.png) [@David\_VA3XDT](https://community.allstarlink.org/u/David_VA3XDT)\
**Post date:** [February 15, 2026, 6:14pm UTC](https://community.allstarlink.org/t/node-is-receiving-but-not-transmitting/24268/4 "2026-02-15T18:14:47Z")

</div>

Having thought about it, I figured re-flashing ver. 1.4 wouldn’t hurt. No change unfortunately. I can RX but unable to TX, although the dashboard says I am.

David VA3XDT
