webcall-android
webcall-android copied to clipboard
mehrvarz
please add an option so when user turn it on, the app only make connections through tcp?
Hello
I live in a "internet hostile" reign that manipulate traffics very much and blocks udp or make it unusable to use it for calls and such (tcp also but....)
May you please add an option so when user turn it on, the app only make connections through tcp?
It will be great.
So maybe we can tun the server on local network also in case of internet shutdowns and can call in heavily restricted network with our friends, family and co-workers.
Thank you
I mean the app also use tcp for calls (if my explanation was not clear)
Thank you
And please make that switch client side so we can use it when using thrd party servers.
Thank you
Sorry for several comments, my browsers has issues and I can't edit my comments and issue.
app only make connections through tcp
RTC over TCP through NAT is not technically possible.
If you mean TCP over TURN: Routine (frequent) use of TURN is discouraged due to traffic cost on the server side. Also, using TURN results in degraded quality and higher latency, even if proxying UDP.
I live in a "internet hostile" reign that manipulate traffics very much
Where is this taking place? Does regular WebRTC (over UDP) work sometimes, or never?
Oh, i see. That's unfortunate. Thank you.
Countries like Kazakhstan, china, Syria, Lebanon, Afghanistan, india, Iran and many more that they called enemies of the internet.
Sorry, i prefer to not expose my exact location.
Yes, it works sometimes, sometimes it doesn't work, sometimes it only works for popular messaging apps, sometimes it may work with unpopular services, sometimes it even won't work in the local network of the country, sometimes it get blocked completely.
We also don't know what the hell they are doing.
BTW, Thank you very much. This software is great.
Countries like Kazakhstan, china, Syria, Lebanon, Afghanistan, india, Iran and many more that they called enemies of the internet.
When I call people in (some of) these countries, it usually works fine. Too bad I cannot look at your env. Did you consider fetching your adb logcat? (Android device must be connected via USB and ADB debugging must be enabled:)
adb devices adb -s deviceID logcat |grep -E "WebCall|webcall|Runtime|System.err"
Switching to TCP-over-TURN can certainly not solve "sabotage"-like issues.