The number you dialed, has not received a response from the service provider?
B0b.:
Quote from: A_Friend on August 15, 2018, 07:32:21 am
All I can offer you is some speculation and maybe a couple of things to try -- a shot in the dark, so to speak.
Thanks for the help!
I'll look at the ICE/Keep-alive/times on the OBi. Do you know where these are or what to try when setting them?
The only thing I quickly found when looking at the Internet settings on the configuration page is PPPoEKeepAlive set to 60.
I'm getting a Wi-Fi adapter in the mail tomorrow to try to connect the OBi directly to the hotspot and bypass the router.
I already have the same GV account set up on my laptop and spare cell phone that is connected to Wi-Fi and these always ring and can make outgoing calls.
I'll look into getting a SIP account from another provider, but I'm hoping to stick with GV. A cellphone is available to use 911, but it has a limited amount of minutes for other calls, and I would prefer to use the landline handset to make calls at the house.
A_Friend:
Bear in mind I have no idea if any of these will actually help.
Check out the settings under ITSP/General, ITSP/SIP, and possibly more relevant: SP1.
Also, bear in mind, that you'll possibly be paying for additional traffic if you speed up the handshakes. Depending on what your deal is with the hotspot, this may or may not be significant.
You might also want to search this site, and Google, for any incidents of folks needing to change any keep-alive type settings, timeouts, etc. to support an Obi device on a shaky network (or vice versa). They might have posted something more specific than my general speculations.
As for the suggestion you try another SIP provider (and maybe keep one around for 911), that was partly for pure diagnostic purposes, and partly just because I like having backups for things I need to work.
B0b.:
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?
A_Friend:
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.
SteveInWA:
Quote from: A_Friend on August 15, 2018, 07:32:21 am
All I can offer you is some speculation and maybe a couple of things to try -- a shot in the dark, so to speak.
My guess, based on your description of what you're seeing and what you've tried already, is that this may have something to do with keeping the connection alive, most likely at the hotspot, but who knows. You may eventually have to shorten up all the ICE/keep-alive/time-to-whatever/etc. settings on the Obi in order to keep the hotspot awake. Whether or not the router is getting involved or losing awareness that it doesn't have a live connection at some critical juncture, is another mystery.
For starters, though, why don't you isolate the hotspot and see how that's performing on its own? Configure your GV to work through Chat or Hangouts and use a laptop directly connected to the hotspot via wifi to make and receive some calls. Or download the GV app for an Android tablet or phone and use that through wifi. If for some reason that's solid and stays up for a day or three, then you can start fiddling with the Obi and/or your router. But, first steps first.
Another thing to try: Get a SIP account from another provider and see how that works on your current setup. Circlenet can give you a DID with 911 for $1.50 a month. You should probably have 911 service anyway. Callcentric will give you a free account for SIP only dialing, sell you 911 for $1.50 a month, and possibly is still giving away random DID numbers in NY State with free incoming usage. (Overall, Circlenet is still cheaper, especially if you're making outgoing PSTN calls, and is giving away $1 free usage to Obitalk denizens.) Personally, I'm also a big fan (and user) of voip.ms, but their minimum funding amount is $25, and you can't do much without being funded.
Disclaimer: I have no idea what's going on with your setup, but that's what I would try in your position.
OMG, this is the biggest case of male answer syndrome/mansplaing yet. You are just pulling answers out of your ass, and even admitting they are just speculation, or you don't really know. If you don't know, then DON'T answer the freaking question. It wastes the OP's time and accomplishes nothing.
The OP clearly stated that it failed when calling the OBiTALK test number. This proves that it has nothing whatsoever to do with Google Voice, nor any service provider settings.
There are no "keep-alive" settings for the OBi's network connection. From the standpoint of the physical, datalink, network and transport layers, it's just an ordinary Ethernet TCP/IP connection between the hotspot and the connected device. Keep-alive is a VoIP concept, and it is irrelevant here, because a) the device is failing regardless of which service provider it is using, and b) the OBiTALK portal (which you continually dismiss) automatically sets the correct, custom keep-alive values for Google Voice, that should not be tampered with. If this forum would accept screenshots, I'd post the settings, but there is no reason that they would be incorrect, as long as the user is not messing with them.
The issue is with the reliability of the hotspot connection, not any setting in the OBi device.
Bottom line: using a hotspot for this is a crapshoot. If it works, great; if not, tough luck.
Navigation
[0] Message Index
[#] Next page
[*] Previous page