Version: [email protected]
When I using single radio device like
[MYREMOTE]
TYPE=Local
AUDIO_DEV_KEEP_OPEN=1
AUDIO_DEV=udp:127.0.0.1:10100
AUDIO_CHANNEL=0
SvxLink will bind port 10100 and listen.
client will connect to 127.0.0.1:10100 and kernel will give to it some random port. lets say 5000.
now if client send PCM data from port 5000 to port 10100 it work fine, SVXlink hear those audio.
problem is in TX line. without AUDIO_DEV_KEEP_OPEN it will close this socket and tries to connect to 127.0.0.1:10100 but there is nothing listening as long you can not have two apps on same port.
but if you have AUDIO_DEV_KEEP_OPEN it will NOT close it, but start sending packets to themself from 10100 to 10100... In this case it should use that clients kernel port 5000. So client will got those audio data... so it should be 10100 -> 5000
of course I can make two sections like RX/TX radio.. but that means I have to open UDP socket on client application too. Which is easy on localhost,, but bad if client is behind NAT or firewall (without access, like we have now in university).
Consider fix this behaviour because you already have in this mode socket opened as Read/Write
Version: [email protected]
When I using single radio device like
[MYREMOTE]
TYPE=Local
AUDIO_DEV_KEEP_OPEN=1
AUDIO_DEV=udp:127.0.0.1:10100
AUDIO_CHANNEL=0
SvxLink will bind port 10100 and listen.
client will connect to 127.0.0.1:10100 and kernel will give to it some random port. lets say 5000.
now if client send PCM data from port 5000 to port 10100 it work fine, SVXlink hear those audio.
problem is in TX line. without AUDIO_DEV_KEEP_OPEN it will close this socket and tries to connect to 127.0.0.1:10100 but there is nothing listening as long you can not have two apps on same port.
but if you have AUDIO_DEV_KEEP_OPEN it will NOT close it, but start sending packets to themself from 10100 to 10100... In this case it should use that clients kernel port 5000. So client will got those audio data... so it should be 10100 -> 5000
of course I can make two sections like RX/TX radio.. but that means I have to open UDP socket on client application too. Which is easy on localhost,, but bad if client is behind NAT or firewall (without access, like we have now in university).
Consider fix this behaviour because you already have in this mode socket opened as Read/Write