Quote from: B0b. on August 16, 2018, 10:08:05 PM
I just got the WiFi adapter and connected it directly to the hotspot then disconnected the Ethernet. Once WiFi was connected, the test calls went though, but then after waiting 10 minutes or so then placing another test call I got the same error message again.
@A_Friend, I looked for the settings you mentioned, but unfortunately, am still unsure of where they are, what they do, or what to set them to.
When I get the message on the phone, then login to the OBi Dashboard, it still says that the device is connected. Is this being displayed incorrectly?
The "connected" message on the Obitalk dashboard is just talking about the dashboard being able to communicate with the device. It says nothing about whether your device is attached to the carrier (GV). For that, you need to read the Status of the device. (Forgive me, but I'm not a big dashboard fan, so I tend to do everything through the local user interface, but you may also be able to access this under ObiExpert from the Dashboard. Just don't try using the ObiExpert and local UI routines at the same time.)
To access the local User Interface, you need the IP address of the Obi on your LAN, and you need another computer, tablet, or other gizmo with a browser on the same LAN. To find the IP address, you pick up the phone, dial *** and then 1. Then, browse to that address and login. (admin/admin)
The Status screen displays as the first thing when it comes up. The menu is at left where you can look at other things and settings. Scroll down the Status screen and it will show you which SP is connected, which isn't, and sometimes why.
Then, under Status, at left, you might want to check Call History for more clues. There will be error codes for failed calls.
After you find out what's happening, maybe someone else can help you. I haven't had this problem myself on an Obihai before. Years ago, though, when I was running Nextiva on a PAP2T, I remember tech support had me change similar settings for a similar problem. Something is letting your connection expire. That's where my useful wisdom on this subject expires, too. Under SP1 you'll find some settings for keep_alive. I don't know what to change or what to suggest changing it to, but if you do some research, and experiment a bit, maybe you'll get lucky. Just make a note of what the setting was when you started. Or, better yet, maybe someone else here can tell you.
You also might get some useful information from your hotspot service's tech support, but probably not from its level 1, although you never know. I never got anything useful out of AT&T, Verizon, etc., without getting to level 3. Good luck.