And as usual with obi, it's an endless rabbit-hole that's now impossible to keep up with unless someone who has it proven to work is nice enough to actually write up some coherent directions that are consolidated. As it is, by the time anyone gets even a handful of pages into that 1st thread for the Raspberry pi, they will surely ditch the effort. I know it seems so cludgy to me I would have to error on the side of you being more the "lottery winner" if you actually have a semi-stable pi still talking to GV. If you are, you REALLY should write up an actual step by step.
I stopped when I tried to figure out which repo was the one to use, which patches were relevant, etc. LOL but certainly would give it a try if I thought it was realistic it might work since I invested over the years into several obi110s that are now apparently paperweights and I can't even find a clear answer as to what to do with the multiple obi202s that have been sitting in the box never powered on for years - do I have something "golden" since unlike most, they have never been updated and should I NOT flash them, do I do the old-school "expert" config, or now with the XMPP death do I have to go back to just dumping them into the obi portal?
....Moral is.....for MANY of us, we got VERY content with our working Obi110s over the years, and now suddenly find ourselves having to re-learn obi-SIP from square one all over again. I personally just thought that after almost a decade here, there would by now (even by OBI) be pinned sticky thread for each supported device, and the 1-2 pages on the "supported" method to set them up, and then perhaps the usual 100+ pages on all the "advanced" dial rules and routing etc. Alas, still not there and does NOT make me that much more eager to rip that shiny new Obi202 out of the box and begin again!
