Can't make or receive calls using GVoice since this morning
drgeoff:
Quote from: danzg on December 24, 2020, 08:01:58 pm
Quote from: SteveInWA on May 05, 2018, 04:32:31 pm
Now, plug in the Ethernet cable and go to the OBiTALK dashboard, and click the button to add a device. Follow the instructions to press **5 xxxx to add your device.
This step is not working for me ... tried several times. Heard "sent to server."
Updated firmware to 3.2.2 (Build: 5921EX).
Still no go.
See the replies to the numerous other posters with the same issue.
OnyejeHome:
Not sure if this applies here, but I added my obi200 device to my obitalk account for the first time just this morning by following the steps that I posted in this thread: http://www.obitalk.com/forum/index.php?topic=17783.msg106501#msg106501
I'll post my response below as well in case the link to the other forum post doesn't work.
"Nice mpotratz!
I just followed your advice and tried the same thing. Before on December 31st, I tried connecting my obi200 device by retrying every 2-3 minutes, and would do research inbetween tries and was unsuccessful, not to mention that I made the DNS changes and swapped out the ethernet cable that came with the obi with my own thinking the cable was at fault, and in the obi firmware settings changed the timezone to match my current timezone (also experimented with keeping the phone on the line during the entire 120 second discovery process, and hanging up after hearing the message the first time, with no success. I think I made 6 connection attempts total yesterday over a 15 minute period before giving up).
However, today, I tried again, and this time just followed the instructions and would hang up immediately after the start of the first message (wouldn't even let the first message audio finish playing). I did this in succession over a 10 or 15 minute period, and was able to squeeze in 10-13 attempts during that time frame and it finally connected on the 13th try.
So, yeah, for those of you having connection issues, just retry the process without thinking into it too much or trying to do anything different than normal. It should start finally reaching the server and properly connecting. It almost seems like there's a timeout issue with their servers, and with each attempt, the device makes it further into the handshake process with the server that it's supposed to talk to. Would almost seem like expanding the discovery period on the obi site from 110 or 120 seconds to 5-10 minutes might solve the issue. But this is all me just hypothesizing without any true understanding of the network process behind the scenes. I just remember on one of my attempts (maybe around #11 or 12), I saw that my browser actually started showing that a TLS handshake was occurring, which is something I recall not seeing the first couple of times I tried. Anyways, everyone, keep on attempting those connections and don't give up, it will eventually work!"
I just finished testing making and receiving calls on my cordless phone attached to my obi200 device and haven't had issues. Last thing I need to figure out before i'm satisfied is how to get my google voice number to show when making outgoing calls from my cordless phone.
---Update---
Not sure if adding my area code in the Obi Dashboard and SP1 Google Voice Configuration made a difference, or whether I just needed to give it more time, but now my phone number/caller ID shows up properly for outgoing calls.
msrrb:
Quote from: drgeoff on December 25, 2020, 04:36:09 am
See the replies to the numerous other posters with the same issue.
So not helpful. Do you mean other replies in this 2 year old 210 post thread or somewhere within the forum? Can you LINK to one of the replies? Or even what search terms to use since the search only searches for each word individually and not as a set? Any of that would be much more helpful than this statement.
msrrb:
FOLLOW THESE INSTRUCTIONS PEOPLE, IF YOU ARE HAVING TROUBLE ADDING YOUR DEVICE AFTER CALLING AND CONNECTING TO THE **5 NUMBER RESULTS IN A TIMEOUT ERROR
(Also note first that there are two * not one before the 5.) Thank you to @OnyejeHome for this explanation.
Quote from: OnyejeHome on January 01, 2021, 10:24:05 am
Not sure if this applies here, but I added my obi200 device to my obitalk account for the first time just this morning by following the steps that I posted in this thread: http://www.obitalk.com/forum/index.php?topic=17783.msg106501#msg106501
I'll post my response below as well in case the link to the other forum post doesn't work. [Shortened by me. Edited for clarity. Use link to see full original response.]
I just followed the instructions and would hang up immediately after the start of the message (wouldn't even let the message audio finish playing). I did this in succession [within the same 120s timeout period]. Over a 10 or 15 minute period, I was able to squeeze in 10-13 attempts and it finally connected on the 13th try.
So, yeah, for those of you having connection issues, just retry the process without thinking into it too much or trying to do anything different than normal. It should start finally reaching the server and properly connecting. It almost seems like there's a timeout issue with their servers, and with each attempt, the device makes it further into the handshake process with the server that it's supposed to talk to....Anyways, everyone, keep on attempting those connections and don't give up, it will eventually work!"
jacek_:
Hi, my OBi 200 stopped working with GV this week. It was originally set up in 2015 with GV account dedicated for it. Device has the latest F/W. I didn't touch neither OBi nor GV settings since creation.
I got initially the "Connecting to 216.239.36.145;Token Error," and the standard "has not received response from SP" voice error when trying to call any number. OBi support asked me to delete that device from GV and redo GV setup on OBi portal. Got the same results (token error). However, this time the device was _not_ added to GV account.
I followed directions from the first page of this thread, but am still ending up with the same thing (token error) and no OBi device in GV setting.
As far as I can see, the initial OAuth looks good, neither Google, nor OBi are complaining. After that, there is long 'Configuring' time ending with "Registration Not Required" and at some point transitioning to "Token Error," but no changes on GV side (no OBi device/app there). My take is that somehow OBi either didn't get OAuth token, is mishandling it, or maybe a new GV permission needs to be requested by OBi. Another thing is that since I didn't touch those two accounts for a long time, maybe there is something new on GV side that I need to enable/disable.
Actually, I have a question about the #4 bullet in Steve's instructions (Third-party apps with account access). When you say "delete all telephony apps" do you mean "Google Voice" app as well? I am not deleting that one, so maybe that is the blocking issue?
Thank you for your help,
Jacek
Navigation
[0] Message Index
[#] Next page
[*] Previous page