Rodrigo-NH
commented
5 years ago Testing further and by this time after a hang server kept transmitter “ON” even after disconnecting successfully. I was the only user connected.
22:11:32 2019: Tx1: Turning the transmitter ON 22:11:33 2019: Tx1: Turning the transmitter OFF 22:11:33 2019: Tx1: Turning the transmitter ON 22:11:41 2019: PU4RNH: EchoLink QSO state changed to BYE_RECEIVED 22:11:41 2019: PU4RNH: EchoLink QSO state changed to DISCONNECTED 22:11:41 2019: WARNING: Could not find audio clip "phonetic_p" in context "Default" 22:11:41 2019: WARNING: Could not find audio clip "phonetic_u" in context "Default" 22:11:41 2019: WARNING: Could not find audio clip "phonetic_4" in context "Default" 22:11:41 2019: WARNING: Could not find audio clip "phonetic_r" in context "Default" 22:11:41 2019: WARNING: Could not find audio clip "phonetic_n" in context "Default" 22:11:41 2019: WARNING: Could not find audio clip "phonetic_h" in context "Default" 22:11:41 2019: WARNING: Could not find audio clip "disconnected" in context "EchoLink" 22:11:41 2019: SimplexLogic: Deactivating module EchoLink... 22:11:41 2019: WARNING: Could not find audio clip "deactivating" in context "Default" 22:11:41 2019: *** WARNING: Could not find audio clip "name" in context "EchoLink"
EDIT: After this occurrence everytime I log into server, server switch to transmitter “ON” automatically when I log in (e.g. I didn’t pressed the transmit button). At first I suspected of some issue in the android Echolink but it happens also if I log using echolink the computer version. Odd enough, it keeps doing this even after restarting svxlink server. The third time repeating this (stop svxlink, start again, log in) the problem occurred again, this time I tried pressing the “transmit” button (while its hang in tx ON) and svxlink crashed with:
svxlink: /home/sstv/svxlink/src/async/audio/AsyncAudioSelector.cpp:445: void Async::AudioSelector::selectBranch(Async::AudioSelector::Branch*): Assertion `(m_selected_branch == 0) || (m_selected_branch->streamState() == STATE_IDLE) || (m_selected_branch->streamState() == STATE_WRITING)' failed. Aborted
I'm running the client using public proxies
sm0svx
Hi. I compiled svxlink from Master in RaspberryPi2. Using latest Echolink for Android is very recurrent transmitter hanging on “ON” after clicking on end transmission. It happens specially while using a proxy connection, but I saw occurring also while using relay. Using Echolink on computer things are better but it happened once after some tries (after 10~15 tries) Unfortunately, I wasn’t able to state this is a server or a client issue but when it happens if I click “END” on android or computer echolink, server releases the transmission "ON" promptly and drops my callsign from the server's user/callsign list, showing client was connected at that moment. Going to try older svxlink versions to see what happens. Thanks
EDIT: Perhaps worth mentioning that im under CGNAT from my ISP. I setup a openvpn tunnel on a secondary router here to be able to redirect connection (and the UDP ports) to/from a VPS. Everything works as expected using echolink client. Using the server from raspberry on this VPN tunnel works great also, except this transmitter hang.