-
Notifications
You must be signed in to change notification settings - Fork 692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always-on VPN immediately changes Linphone's connection status to "Not Connected" #2271
Comments
Hi @twesterhever, I don't have a graphene OS device to test it, nor a VPN subscription. Thanks in advance! |
Thank you for your quick reply. Debug logs are ready, however, as they contain quite a lot of PII, I'm reluctant to share these here. Would a DM be suitable as well?
If the same VPN is enabled, but not configured as being "always on", this part looks different:
I'll try the 6.x alpha release as soon as possible and will report back. |
Hi @twesterhever, You can send the logs to me by email at [email protected] Cheers, |
Hi Linphone development team! :-)
Running the Linphone app on Android only works if any VPN configured with Android itself (i.e., via the internet settings) is not set up to be "always-on", i.e., established under any circumstances. As soon as any active VPN connection is configured to be "always-on", Linphone's connection status immediately changes to "not connected" (accompanied by a grey icon, rather than the usual green one). However, any other apps work fine, as does the VPN itself.
As soon as the same VPN configuration is modified to be active on demand, rather than "always-on", Linphone's status turns to "connected" again (green icon), despite no other aspect of the VPN has changed.
In this scenario, the Linphone app should act VPN-agnostic, and attempt to establish a SIP connection as usual, regardless if an active VPN is configured to be "always-on" or not.
Thank you in advance for looking into this issue!
The text was updated successfully, but these errors were encountered: