No TX/RX audio to/from SA818 SHARI-Pi

All,
A few months ago, I had ASL working great on a Raspberry Pi 4 and (VHF) SHARI-Pi. I put it off to the side for about 6 weeks to work on the enclosure and another project. When I resumed, the SA818 would key up, but I had (and still have) no TX or RX audio.
I messed with configuration settings in simpleusb and rpt.conf. Audio never returned. I decided to restart with a fresh Pi image and a fresh ASL install. Now, I'm back to where I was: no TX or RX audio.
I verified TX and RX frequencies. On my HT, I can receive an unmodulated carrier with a valid CTCSS tone from the SA818.

asl-find-sound: 1-1.3:1.0 --> 0d8c:0012 C-Media Electronics Inc.

In rpt.conf, duplex = 2 in the template and "Your node" setting.

In simpleusb.conf:
txmixa = voice
txmixb = none
carrierfrom = usbinvert
ctcssfrom = usbinvert

In modules.conf, I am loading simpleusb:
load = chan_dahdi.so ; DAHDI Telephony w/PRI & SS7 & MFC/R2
noload = chan_echolink.so ; Echolink Channel Driver
require = chan_iax2.so ; Inter Asterisk eXchange (Ver 2)
noload = chan_mobile.so ; Bluetooth Mobile Device Channel Driver
noload = chan_ooh323.so ; Objective Systems H323 Channel
load = chan_simpleusb.so ; SimpleUSB Radio Interface Channel Driver
noload = chan_tlb.so ; TheLinkBox Channel Driver
noload = chan_usbradio.so ; USB Console Channel Driver
noload = chan_usrp.so ; USRP Channel Module
noload = chan_voter.so ; Voter Radio Channel Driver

Versions:
...
********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.12.34+rpt-rpi-v8

Asterisk : 22.4.1+asl3-3.5.4-1.deb12
ASL [app_rpt] : 3.5.4

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.5.1-1.deb12
asl3 3.8-1.deb
asl3-asterisk 2:22.4.1+asl3-3.5.4-1.deb12
asl3-asterisk-config 2:22.4.1+asl3-3.5.4-1.deb12
asl3-asterisk-modules 2:22.4.1+asl3-3.5.4-1.deb12
asl3-menu 1.14-1.deb12
asl3-pi-appliance 1.10.0-1.deb12
asl3-update-nodelist 1.5.1-1.deb12
cockpit 287.1-0+deb12u3
cockpit-bridge 287.1-0+deb12u3
cockpit-networkmanager 287.1-0+deb12u3
cockpit-packagekit 287.1-0+deb12u3
cockpit-sosreport 287.1-0+deb12u3
cockpit-storaged 287.1-0+deb12u3
cockpit-system 287.1-0+deb12u3
cockpit-wifimanager 1.1.1-1.deb12
cockpit-ws 287.1-0+deb12u3
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-6+asl
dahdi-linux 1:3.4.0-6+asl

lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0d8c:0012 C-Media Electronics, Inc. USB Audio Device
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I saw a post from 2021 that mentioned the CH340 USB device in lsusb. Is the CH340 device missing from my USB devices, or has that been deprecated?

I have 3.29V at pin 5 and 4.37V at pin 8 of the SA818.

I have a feeling that it's going to be a simple setting I missed. But, I can't figure it out.
Any help would be appreciated.
Thank you very much,
-Shawn

An SA818 does not break out separate signaling lines for COS/COR and CTCSS. There’s one signal line that is a combo “valid signal” that is “COS” to SimpleUSB. Change ctcssfrom to no. They way you have it configured, simpleusb will never “see” the CTCSS line pull low because nothing is connected to it.

I made the change and it made no different. No modulated tones and no voice is passing through. But the 'F' commend will key up the transmitter (with no audio).

Even if the Asterisk portion was incorrectly configured, I should still be able to hear locally generated tones, right?
Thanks in advance,
-Shawn

RPT.conf and simpleusb.conf added. I would appreciate it if someone could look these over and see if there is something I'm missing.
Again, the SHARI module keys up, but no transmit audio.
Thank you,
-Shawn

rpt.conf (33.5 KB)
simpleusb.conf (8.4 KB)

Under duplex=3 there is no repeated audio.

Not sure what other you can config, but this is not a error of any kind.

For standard full-duplex use =2
For a simplex node, likely =1

I have no clue what the sa818 is capable of. Just saying your setting seems to be the issue as described.