On unreliable 3G/4G network connections and escpecially when using the original java-based echolink proxy it can happen that the proxy is disconnected when there are established echolink connections.
These connections reduce the remaining connection count and the most critical case is that no more
incoming/outgoing connections are allowed.
Function onStateChange is not called in this case, but state seems to be Qso::STATE_DISCONNECTED,
since DTMF "1" says "no connected stations", but LocationInfo sends the connected list.
Not easy to debug, since system is not physically reachable and only connected to internet via 3G.
dh1dm
commented
4 years ago
On unreliable 3G/4G network connections and escpecially when using the original java-based echolink proxy it can happen that the proxy is disconnected when there are established echolink connections. These connections reduce the remaining connection count and the most critical case is that no more incoming/outgoing connections are allowed. Function onStateChange is not called in this case, but state seems to be Qso::STATE_DISCONNECTED, since DTMF "1" says "no connected stations", but LocationInfo sends the connected list. Not easy to debug, since system is not physically reachable and only connected to internet via 3G.