Cheers indeed :) I got it sorted out. Your answer both explained why I had been stuck in precisely that way, and pointed me to the information I needed, but would have had a hard time to navigate to.
Luckily, one of my already set up android devices is rooted, so, now knowing what to look for, I managed to discover the user config at /data/data/org.linphone/files/.linphonerc , and together with the example remote_provisioning.xml file linked in the wiki, and an amount of trial and error, this really solved it for my situation. Merci mille fois, Sylvain - it's by no means common anymore to receive this type of help, a neoprimitive or non-affluent user like me, is getting to hear a lot about deprecated, obsolete, unsupported, EOL, retired API and please update, in quintessence, "your situation is wrong", but creatively working with the situation and available means, is standing out. Thanks a lot :) On May 27, 2025 12:29:41 PM GMT+01:00, Sylvain Berfini <sylvain.berf...@belledonne-communications.com> wrote: >Hi, > >There was a mechanism in 4.4 app that checked (using XMLRPC) an account >existed by doing a query to our subscribe.linphone.org (at the time on port >444). >Problem is we no longer listen on 444 but we're now using the standard 443 >port, and those endpoints no longer exists anyway. > >You can workaround that issue by configuring your device using remote >provisioning (see here: >https://wiki.linphone.org/xwiki/wiki/public/view/Lib/Features/Remote%20Provisioning/). >Feel free to contact me directly if you need help. > >Cheers, > >Sylvain Berfini >*Head of Mobile & Desktop Apps Department* > >+33 (0)9 52 63 65 05 >sylvain.berf...@belledonne-communications.com > >Discover our solutions in 3 minutes! ><https://player.vimeo.com/video/393868225?autoplay=1> > >/Belledonne Communications, the company behind the Linphone project/ >https://linphone.org > >Le 26/05/2025 à 21:32, J.H. a écrit : >> For many reasons (i.e. long, and off topic to discuss here), LineageOS or >> other alt ROMs, are out of the question. I wouldn't come here if I >> considered doing that. >> >> Yes, it did occur to me to try adding my linphone account like a normal sip >> account. The assistant detects this, and throws you back to the add existing >> linphone account form. Even if this worked, I am not sure if free linphone >> sip accounts can be logged into as normal sip accounts at all, e.g. from 3rd >> party sip apps. Only the reverse is getting addressed in the current FAQs, >> but a truncated sentence in duckduckgo's cache/search results makes me >> suspect that you cannot. >> >> Trying a totally different type of internet connection (like a public >> library), will happen when I'm having the opportunity; I had been hoping >> that "I'm not having the means to test that hypothesis and come from >> another, unlisted IP" would convey that this is not the case in this moment, >> rather than that I was out of ideas how to connect differently. >> >> I do *think* that subscribe.linphone.org:444 is (or was) an API, I couldn't >> think of anything else that is making sense, but I'd definitely *love* to >> hear from someone who knows with certainty: that *is* what I'm here for. >> >> I'm still reluctant to publically share partial-, let alone link, complete >> logs here: they'd need manual editing for adequate privacy, but after doing >> more testing today, with freshly reset logs, there's this >> >> UPDATE: >> >> On my newest comparison device, running linphone-app 4.3.1 (the last well >> running version still with PiP mode for video calling :-) ) on android 7, >> failed connection attempts (even before the tls handshake) to >> subscribe.linphone.org:444 do occasionally pop up in the logs, HOWEVER, >> attempting to add a bogus linphone account like user ali passwd baba (I >> don't want to risk deleting and failing to re-add a real account) (yes, I >> didn't mention: I'm using email registration and user | passwd >> login, not a linked phone number), while resulting in a misleading error >> (red dot, connection failed) in linphone's status, and the account being >> added (as new default! despite failure) still makes the app try to REGISTER >> a...@sip.linphone.org with sip:sip.linphone.org via SIP/2.0/TLS, ultimately >> and I assume correctly, given the bogus credentials, failing with a 401 >> Unauthorized reply on first try, and 403 Forbidden on 2nd, all that without >> any attempt to contact subscribe.linphone.org:444 >> >> On the android 4.4.2 device that I'm asking for, where I need to first-time >> set up the linphone 4.0.1 app, however, after trying the assistant, logs >> show that an attempted REGISTER call to sip:sip.linphone.org via SIP >> protocol does not happen in the first place, the account isn't added, but a >> 'failed to query server' message shown that needs to be acknowledged. >> Failed/refused, on the tcp/ip level, connections to >> subscribe.linphone.org:444, on the other hand, there are, I've also spotted >> an additional error resulting from this: [liblinphone] ERROR I/O during >> XML-RPC request sending >> >> On the comparison device that, theoretically, (model, android build, kernel, >> linphone version) is identical, except that there are working, set up >> accounts on the linphone app already, the attempt to add a new linphone >> account with bogus creds, likewise results in a failed to query server error >> that wants to get clicked away, no account added, and no trace of the >> attempt unless you are counting failed attempts to reach >> subscribe.linphone.org:444 and the failed XML-RPC request sending. This >> linphone instance, however is happily communicating with sip.linphone.org >> for registering, publishing, answering checks, for the already set up >> accounts, and all instances happily establish secure connection with >> www.linphone.org:444 for purposes of log uploading >> >> So I'm less sure now what exactly the role of trying to establish an XML-RPC >> handshake with subscribe.linphone.org:444 is, but it's the only visible >> persistent ERROR in the client I'm trying to get through its first steps, >> and that's what I need help with. >> >> >> >> >> On May 25, 2025 11:47:22 AM GMT+01:00, Greg Troxel <g...@lexort.com> wrote: >> >> "J.H."<juanflauti...@gmail.com> writes: >> >> 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. >> >> Wow. I wonder if you can install lineage on those, and get newer AOSP, >> vs running code from 2013 or so. >> >> 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. >> >> subscribe.linphone.org. 706 IN A 176.31.149.177 >> subscribe.linphone.org. 706 IN A 5.135.215.41 >> subscribe.linphone.org. 698 IN AAAA 2001:41d0:203:7fe2::2 >> subscribe.linphone.org. 698 IN AAAA 2001:41d0:303:b0d2::2 >> >> For me, wget fetches the login page via both v4 and v6. >> >> Do you really mean 444? Is this the API? >> >> Have you tried visiting a local library or some other place with wifi, >> that is a different network, or using phone hotspot (really, some other >> network)? >> >> >> I don't understand why you need to use assistant, vs adding a sip >> account manually that happens to be at sip.linphone.org. >> Did you try that? >> >> >> _______________________________________________ >> Linphone-users mailing list >> Linphone-users@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/linphone-users
_______________________________________________ Linphone-users mailing list Linphone-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/linphone-users
