I need to set up linphone-android on an old android 4.4.2 tablet. Naturally, I
am forced to use an old version of the app, trial and error demonstrated that
4.0.1 from the f-droid archive is what installs and starts up on this
particular device.
When I am trying to use the assistant to add my existing free linphone account,
the app will respond "Failed to query server. Try again later". Obtaining logs,
the underlying error appears to be that the app tries to verify username and
password at subscribe.linphone.org, and while the domain resolves and resolves
to belledonne owned (e.g. 5.135.215.41) addresses, the ipv6 addresses will be
unreachable, the ipv4 ones, give connection refused when tried on port 444 by
the app.
I have other devices with already set up linphone apps, one of them, the same
make of tablet, same android version, and same linphone app version. kernel and
build are identical, the apk used to install linphone, is identical.
Pretending to add a new existing linphone account there, gives the same "Failed
to query server. Try again later"-message, looking at the logs for that later,
shows that registering, at sip.linphone.org, works fine for accounts that the
app already has authentication data for, and that the tls negotiation goes fine
for sip.linphone.org, or, on yet another device lima.linphone.org, based on
ISRG Root X1 and Let's Encrypt, but since on those devices, I also find network
unreachable / connection refused errors for the connection attempt to
subscribe.linphone.org, I suspect that I'd be f***'ed on these devices, too, if
I wasn't so lucky and had my accounts already added since years.
So for one, I'd like to understand what is happening, naturally, I think of
different server settings for the subscribe subdomain, I don;t even think it's
cert- or tls version related, since tls negotiation isn't even beginning. One
far shot would be banlists: the IP I am coming from, is on spamhaus' PBL aka
policy blocklist, but the explicit use case of that list is preventing direct,
unauthenticated emails from ISP controlled, non-permanently assigned IP
addresses (like my mobile internet IP) - I'm not having the means to test that
hypothesis and come from another, unlisted IP, but that would be the wrong list
for the wrong reason. Far shot, as I said, and whatever the real reason is, I'd
like to learn about it.
My other goal is removing this obstacle, which could be linphone revising the
server settings for the subscription server, or, some workable hack that would
allow me to supply the initial secrets needed for registration that the app
would normally get from subscribe.linphone.org when the account is added, in a
different way, e.g. by running a 'remote provisioning server' locally if that
would solve it. I would still need help with obtaining these secrets in the
first place, and how to run minimal remote provisioning as someone who'd at
best know how to start the python built in http server or to send a simple http
api request from the command line with curl, i.e. poweruser perhaps, but in no
way a dev.
Thanks in advance, any productive suggestions welcome, and thanks, too. for
providing this ecosystem
j
_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users
