SvxLink Node not passing audio to SvxLink-Bridge - SvxLink Bridge assigning TG#0 to SvxLink Node traffic.

[KN4YDL]

SvxLink node able to monitor and activate SvxLink-Bridge traffic and pass the audio without issue. The audio traffic from the SvxLink Node to the SvxLink-Bridge does not pass the TG. The Bridge still sees "Talker start on TG #314946: KN4YDL" but immediately resets to TG #0 before the audio reaches DMR/P25. The traffic from the Bridge to the Node works like a charm with no issues.

Logs-
(Node)
Mon Apr 6 19:47:01 2026: ReflectorLogic: Using audio codec "OPUS"
Mon Apr 6 19:47:15 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 19:47:15 2026: ReflectorLogic: Selecting TG #314946
Mon Apr 6 19:47:16 2026: MultiTx: Turning the transmitter ON
Mon Apr 6 19:47:19 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 19:47:20 2026: MultiTx: Turning the transmitter OFF
Mon Apr 6 19:47:30 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 19:47:30 2026: MultiTx: Turning the transmitter ON
Mon Apr 6 19:47:33 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 19:47:33 2026: MultiTx: Turning the transmitter OFF
(Bridge)
Mon Apr 6 14:47:01 2026: ReflectorLogic: Node joined: KN4YDL
Mon Apr 6 14:47:15 2026: ReflectorLogic: Selecting TG #314946
Mon Apr 6 14:47:15 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 14:47:19 2026: Talker stop: unknown TG# 0
Mon Apr 6 14:47:19 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 14:47:30 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 14:47:33 2026: Talker stop: unknown TG# 0
Mon Apr 6 14:47:33 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL-BRIDGE
Mon Apr 6 14:47:38 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL
Mon Apr 6 14:47:38 2026: Transmission starts (TG# 0)
Mon Apr 6 14:47:43 2026: Transmission stops (TG# 0)
Mon Apr 6 14:47:43 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL

Node-->>
Tue Apr 7 17:18:54 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL-BRIDGE
Tue Apr 7 17:18:54 2026: ReflectorLogic: Selecting TG #314946
Tue Apr 7 17:18:54 2026: MultiTx: Turning the transmitter ON
Tue Apr 7 17:19:03 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL-BRIDGE
Tue Apr 7 17:19:03 2026: MultiTx: Turning the transmitter OFF
Tue Apr 7 17:19:08 2026: Rx1: The squelch is OPEN
Tue Apr 7 17:19:09 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL
Tue Apr 7 17:19:13 2026: Rx1: The squelch is CLOSED
Tue Apr 7 17:19:13 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL
Bridge-->>
Tue Apr 7 12:18:53 2026: ReflectorLogic: Selecting TG #314946
Tue Apr 7 12:18:54 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL-BRIDGE
Tue Apr 7 12:19:03 2026: Talker stop: unknown TG# 0
Tue Apr 7 12:19:03 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL-BRIDGE
Tue Apr 7 12:19:09 2026: Transmission starts (TG# 0)
Tue Apr 7 12:19:09 2026: ReflectorLogic: Talker start on TG #314946: KN4YDL
Tue Apr 7 12:19:13 2026: Transmission stops (TG# 0)
Tue Apr 7 12:19:13 2026: ReflectorLogic: Talker stop on TG #314946: KN4YDL

I found this from 2 years ago on Groups.io SvxLink page, (https://groups.io/g/svxlink/message/2046), and did set TG_SELECT_INHIBIT_TIMEOUT=90 In the SvxLink Bridge ReflectorLogic but the TYPE=ReflectorV2 logic keeps treating the TG 314946 as "remote" and resets the simplex response traffic to TG=0.

Sharing my conf file for the Bridge setup-

pi@dvswitch:/etc/svxlink $ cat svxlink.conf
###############################################################################

Configuration file for the SvxLink server

###############################################################################
[GLOBAL]
#MODULE_PATH=/usr/lib/x86_64-linux-gnu/svxlink
LOGIC_CORE_PATH = /usr/lib/arm-linux-gnueabihf/svxlink
LOGICS=ReflectorLogic,UsrpLogic
CFG_DIR=svxlink.d
TIMESTAMP_FORMAT="%c"
CARD_SAMPLE_RATE=48000
#CARD_CHANNELS=1
#LOCATION_INFO=LocationInfo
LINKS=ReflectorLink
LOGLEVEL=4
[ReflectorLogic]
TYPE=ReflectorV2
#DNS_DOMAIN=example.com
HOSTS=north.america.svxlink.net
HOST_PORT=35300
#HOST_PRIO=100
#HOST_PRIO_INC=1
#HOST_WEIGHT=10
CALLSIGN=KN4YDL-BRIDGE
#CERT_PKI_DIR="/var/lib/svxlink/pki"
#CERT_KEYFILE=/var/lib/svxlink/pki/MYCALL.key
#CERT_CSRFILE=/var/lib/svxlink/pki/MYCALL.csr
#CERT_CRTFILE=/var/lib/svxlink/pki/MYCALL.crt
#CERT_CAFILE=/var/lib/svxlink/pki/ca-bundle.pem
#CERT_DOWNLOAD_CA_BUNDLE=1
#CERT_SUBJ_givenName=John
#CERT_SUBJ_surname=Doe
#CERT_SUBJ_organizationalUnitName=SvxLink
#CERT_SUBJ_organizationName=SSA
#CERT_SUBJ_localityName=Stockholm
#CERT_SUBJ_stateOrProvinceName=Södermanland
#CERT_SUBJ_countryName=SE
#CERT_EMAIL=mycall@...
AUTH_KEY="XxXxXxXxXXxXxX"
#JITTER_BUFFER_DELAY=0
DEFAULT_TG=314946
MONITOR_TGS=314946
TG_SELECT_TIMEOUT=300
TG_SELECT_INHIBIT_TIMEOUT=90
ANNOUNCE_REMOTE_MIN_INTERVAL=3
#EVENT_HANDLER=/usr/share/svxlink/events.tcl
#NODE_INFO_FILE=/etc/svxlink/node_info.json
MUTE_FIRST_TX_LOC=0
MUTE_FIRST_TX_REM=0
#TMP_MONITOR_TIMEOUT=3600
UDP_HEARTBEAT_INTERVAL=15
#QSY_PENDING_TIMEOUT=15
DEFAULT_LANG=en_US
VERBOSE=1

[ReflectorLink]
CONNECT_LOGICS = ReflectorLogic,UsrpLogic
DEFAULT_ACTIVE = 1
OPTIONS = DEFAULT_CONNECT,NO_DISCONNECT
#TIMEOUT = 300
ACTIVATE_ON_ACTIVITY = UsrpLogic

The reset is happening inside the bridge’s ReflectorV2Logic (specifically in tg_remote_activation, tg_selected, and talker_start in ReflectorV2LogicType.tcl).

I understand the bridge treats it as "remote" traffic that does not match the current active TG and falls back to the default (TG 0). This is intentional design in ReflectorV2 to prevent stuck TGs, but it breaks the simplex → digital direction in this setup.

Is there a way to fix this as having a bridge is basically useless unless I can reply using the SvxLink Node to respond to QSO traffic?