I had a heck of a time today trying to set up a 200 and WiFi.
I did a setup at home and made sure things were working with my router. Because my neighbor only has a Verizon JetPack (hotspot) I got him to give me the SSID and password for his device.
Then up the mountain I went (it's a one lane road with twists and turns and few places for a truck to pull over when a resident passes).
I plug the 200 in and wait and wait for it to connect. Turns out he gave me the wrong SSID (he misread a letter). So I used *27 and tried to access the unit with my cellphone using both 192.168.10.1/wifi and
obiconnect.com/wifi and both failed. I ensured I had airplane mode on, wifi on and checked the IP address of the cellphone t oensure it was in the 192.168.10.x subnet.
After an hour of playing I finally logged into the Obi dashboard here and forced the change online but of course, it will not load until the Obi200 connects to the internet. (He didn't have a LAN cable so I couldn't even try to hardwire the Obi to his PC and see if I could get in).
I ended up driving down the mountain into town and went to a farm where I have access to a router, hooked the OBI there and let it get it's update though a hardwired connection. Then I met the neighbor at the bottom of the mountain and handed hi the updated OBI and await his heading home to try it.
His only internet is a Verizon hotspot. If it will support an Obi we can port his $50 a month landline to a Voip service at about $3 a month.
By the way he is too far from the central office for DSL and the cable company has a line NEAR him, but to get to him, they have to run the cable on a pole in a neighbors yard. The issue is that pole is a private pole and the owner does not want anyone else on it.
The guy I'm working with is considering satellite internet but there may be too many issues to get his internet and phone reliable.