ASL3 - Voter not working after latest update

Setup Information

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.1.0-44-cloud-amd64

Asterisk : 22.8.2+asl3-3.8.3-1.deb12
ASL [app_rpt] : 3.8.3

Installed ASL packages :

Package Version
============================== ==============================
asl-apt-repos 1.4-1.deb12
asl3 3.17-1.deb12
asl3-asterisk 2:22.8.2+asl3-3.8.3-1.deb12
asl3-asterisk-config 2:22.8.2+asl3-3.8.3-1.deb12
asl3-asterisk-modules 2:22.8.2+asl3-3.8.3-1.deb12
asl3-menu 1.18-1.deb12
dahdi 1:3.1.0-2
dahdi-linux 1:3.4.0-11.asl.deb12

Inquiry

After updating to asl3 2.22.8.2 our transmit voter will not key the repeater. I'm seeing events in the asterisk cli after keying up, but the audio will not transmit over the repeater. The audio is being received as I'm able to hear audio on echolink.

Troubleshooting steps

  1. Reinstall all ASL3 related packages
  2. Downgrade ASL packages to earlier release
  3. Start a fresh VM using debian 12 bookworm, install all latest ASL3 packages.
  4. Re-point both RTCM clients to the new server.
  5. Verify RTCM clients talking with voter ASL3 VM
  6. Verify chan_voter loaded in modules.conf
  7. verify both voters are showing up in the asterisk cli using the Voter Instance command. The output of the command is below
  8. Voter Instance <REDACTED> Display:
    
    CgrK |=======================================================>| [255]
    CgrE |>                                                       | [  0]
    
    
    Active Clients:
    
          CgrK -- <SOMEIP1>:1667
          CgrE -- <SOMEIP2>:1667
    
    

CLI messages while keying up repeaster, but no audio

  1. Connected to Asterisk 22.8.2+asl3-3.8.3-1.deb12 currently running on asl3 (pid = 9910)
        -- Channel voter/564560: TX On
        -- Channel Announcer/Telemetry-0000000a;2 joined 'softmix' base-bridge <9cb5b3b0-461e-482c-a408-54bce3a3adaa>
        -- Channel Announcer/Telemetry-0000000a;2 left 'softmix' base-bridge <9cb5b3b0-461e-482c-a408-54bce3a3adaa>
        -- Channel voter/564560: TX Off
    asl3*CLI> 
    
  2. If I put the RTCM client in diagnostics mode from the firmware telnet menu, I'm able to hear the repeater transmitter key up and hear the test tones from diagnostics. So the repeater and RTCM equipment is properly configured and connected
  3. RTCM and allstar will work if I use my old ASL VM. Info about the old ASL setup below.
  4. OS            : Debian GNU/Linux 12 (bookworm)
    OS Kernel     : 6.1.0-37-amd64
    
    Asterisk      : 22.2.0+asl3-3.4.5-1.deb12
    ASL [app_rpt] : 
    
    Installed ASL packages :
    
      Package                         Version
      ==============================  ==============================
      allmon3                         1.4.2-1.deb12
      asl3                            3.7.1-1.deb
      asl3-asterisk                   2:22.2.0+asl3-3.4.5-1.deb12
      asl3-asterisk-config            2:22.2.0+asl3-3.4.5-1.deb12
      asl3-asterisk-modules           2:22.2.0+asl3-3.4.5-1.deb12
      asl3-menu                       1.13-1.deb12
      asl3-tts                        1.0.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-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
    
    

You might want to join this group: