Hi.
OBi212
fw 3.2.2 (Build: 5921EX)
google voice on SP1 connected to my home phone wiring.
Home phone wiring is disconnected from the outside phone wires.
When calling out, it says, "The number you dialed, xxx xxxx has not received a response from, the service provider.".
This has been an intermittent problem over the last year or so.
Incoming calls go to my voicemail.
I received an email saying "Service Offline Alert -- OBi Device (xxxxxxxxx) is Not Registered".
I think I took care of that.
I use two google accounts on my PC.
The Self-Troubleshooting Guide instructed me to router > DMZ > enable.
I did that.
Now SP1 at obitalk.com says "Connecting to xxx.xxx.xx.xxx;Token Error".
SP2 says "Registered".
SP2 is Anveo E911.
933 test works.
Can you fix it?
thx
What did you do that makes you think you took care of the "service offline" email?
It is almost never necessary to put an OBi in the router's DMZ.
Please delete the other copy of your post and refrain from posting the same thing more than once.
"Service offline" email:
I did the following at...
OBi Dashboard >
SP1 >
Replace Google Account Credentials
Sign-in to the correct account, and then,
Click Here to connect the OBi with your active Google Account
thx
Unfortunately, I get the same error all of a sudden, was working for a several weeks, then today the token error.
I rebooted the device, removed and re-added the SP1 Google Voice service.
Replaced credentials.
No help.
933 test still works.
Outgoing calls say "Has not received a response from the service provider"
All the settings at voice.google.com are fine.
I can see incoming calls at voice.google.com, but the Obi200 never rings.
I received two more emails saying "Service Offline Alert -- OBi Device (xxxxxxxxx) is Not Registered".
Both were for the same device number.
They said exactly the same thing.
One is dated 3:30am, and the other was 6:45am.
I did the following again at...
OBi Dashboard >
SP1 >
Replace Google Account Credentials
Sign-in to the correct account, and then,
Click Here to connect the OBi with your active Google Account
SP1 says "Registration Not Required".
SP2 says "Registered".
AIUI the emails mean that the Obihai server(s)* has lost contact with your OBi. That does not necessarily mean that there is a problem between your OBi and any of your ITSPs.
(* The OBihai server is what powers your dashboard at obitalk.com and also enables calls between OBis made by dialling **9 followed by an 8 digit OBi number. The server plays no part in call set-up nor voice data transmission for any other calls to or from your OBi.)
Now SP1 says "Connecting to xxx.xxx.xx.xxx;Token Error"
Obi device status = Online
Just on forum with same issues and questions.
Keeps logging off for token error.
Then may come back after time as registration not required.
I have two google voice numbers on a 202. Has been working well.
I logged in my credentials again, when it gave token error again. Will see how long it lasts this time before going off line. Started in
lasf couple of days with several errors and system off,
This is not isolated as I am having the same issue. My config has been working fine with no changes since December.
Obi200 with 3 Google Voice lines all having the same issue: Connecting to 216.239.36.145;Token Error
The Anveo E911 is not reporting issues.
Me too, my primary GV line is showing a token error and I had many emails about OBI Device Offline then back Online today.
I am also having the same problem. mine started yesterday around mid day. I have done all of the same steps and thought it could be a router problem.
I am using a Netgear Orbi router. I attempted to DMZ it with the same problems.
Hope we can find a solution. If not does anyone have a good alternative?
I am getting the same token error and message on outgoing calls that cannot connect to service provider. Please help!!!!
So did the sign in with GV credentials and reconnected. Again notices last night system went off at 10pm and notice connected again at around 7 am.
Showing connected now, but patterns of token errors continue.
I have the same issue - sometime last night both of my Google Voice lines went down and now I have the Token issue. I have been running fine for YEARS.
Going to the configuration and updating my Google credentials does not make any difference.
Has anyone found a solution, or at least a work-around?
1. If you have GV and at least one other different ITSP configured and they all go down it is almost certainly a network problem or a faulty OBi. That multiple people are reporting the same issue tends to rule out faulty OBis.
2. If you have GV and at least one other different ITSP configured and only GV goes down it is almost certainly a problem at Google's end. Once you have successfully configured an OBi with GV, the Obihai servers play no further part in maintaining the connection between GV's infrastructure and the OBi, nor in call set-up nor voice data transmission for GV calls to or from the OBi device.
Started a few days ago, same issue as everyone else.
Perhaps Google once again has made a change that require some reconfiguration of the Obi devices?
Like previous poster I have been an Obi user since day 1, never had this issue.
GV worked fine with Obihai 200 last night.
Today I cannot make or receive calls. I just received my first covid dose and due to my age and living alone, have several people calling to check on me but my phone doesn't ring and in case I am not well I cannot call out.
In dashboard, I also see Connecting to (my IP address);Token Error
I tried reregistering, and unplugging and reconnecting the obihai, it doesn't fix the issue.
My GV calls forwarding to my cell works, the cell rings but not my landline phones connected via Obihai 200.
Anyone have any way to report this to Obihai or GV to be fixed?
Thanks
Bob
Today, I just noticed that I'm getting a "Token error", and sometimes "Registration Not Required".
I also had the same problem with that "token error". It is not a problem on one of my Obi devices, which is linked to one Google Voice account, but there exists that problem with another Obi device, which is linked to another Google Voice account.
Isn't there one moderator here who has a contact to report to Google and Obihai?
Obihai support has been unresponsive for years, so I didn't even try.
Did anyone here try Obihai or Google support?
Quote from: magicwine on June 11, 2021, 10:49:01 AM
Isn't there one moderator here who has a contact to report to Google and Obihai?
SteveInWA (who is not a Mod) has an Obihai/Poly contact. Hopefully he will see this and make some inquiries. I have seen a couple of the same error reports in the Google Voice support forum.
It is for issues like this that I HIGHLY recommend configuring one or two additional voip providers on your OBi device.
For instance:
I use Localphone for making outbound calls if I don't want to use GV or it's down. Localphone charges 1/2 cent per minute for outgoing calls. That's pretty cheap. I added $5 a few years ago and still have over a $3 balance. You can easily configure Localphone to display your GV number when making a call.
I use Callcentric for inbound calls forwarded from Google Voice. You can get unlimited inbound calls for $1/month. Callcentric also displays CNAM at no additional charge.
Or if the GV app continues to work fine in your home on your smartphone then that's always an option. I have very poor cell coverage in my home so having additional voip providers on my OBi is a must for me.
Very helpful info! Thank you.
I didn't know you could use this device other than with GV, at least at the same time.
Is there a FAQ or other info on how to configure a second provider such as Callcentric for inbound calls? Can Callcentric also be used for outbound calls at the same time?
I presume it is setup as SP2 and there is a way for Callcentric to call your same GV for inbound calls?
Do you have to temporarily stop inbound calls from GV?
Hi - I found this article - is this current?
http://www.obitalk.com/forum/index.php?topic=17024.0
Would still appreciate your replies to my other questions.
Thank you.
Bob
Quote from: magicwine on June 11, 2021, 12:57:50 PM
Hi - I found this article - is this current?
http://www.obitalk.com/forum/index.php?topic=17024.0
Yes, you can follow those instructions. If you choose the subscription Steve is referring to you will also get 120 outbound minutes per month in addition to unlimited inbound minutes plus E911.*
Yes, you would configure it on SP2. Unsure what you mean in the second part of that question. Incoming calls to your GV number will get forwarded to your Callcentric number which will then ring on your OBi device.
Yes, if you set up Callcentric you will need to disable call forwarding to your OBi device. Although it's not going to hurt anything if you don't. If GV is already not ringing your OBi device then it will ring on SP2 thru Callcentric. But if both SP1 and SP2 are working properly then SP1 will beat out SP2 every time since it is a direct route instead of being forwarded to Callcentric first.
*Note: if you configure Callcentric on SP2 and choose the subscription in question you will need to preface any number you want to call via Callcentric with **2. So it would look like:
**2888-555-1212
I have two obi's at the same location (so the same WAN IP). They are both subscribed to the same GV account. In addition the second device has a second GV account and anveo. The first device (GV account only on the device) works. On the second device only anveo works -- neither of GV accounts are working.
I started receiving service alerts some time yesterday alternately indicating registration problems and informing me that registration was restored. When I logged into the account today saw the token error notice. I reregistered GV on SP1 (without doing anything for the second GV account on SP2) -- no help. Except now instead of the token error the account status says "Registration Nor Required", which is obviously wrong.
So:
Two devices at the same IP -- not a connection problem
One of two obi's connects to GV -- not a google problem
Anveo works on obi with GV issue -- not an obi device problem.
P.S. Spoke too soon -- the second obi can't register either, "No registration required"
I just had this issue for the past 24 hours or so. A little recalling of the same issue with web sites I’ve managed over the years, wherein the solution to this error has nearly always been to delete login credentials and cookies stored in the browser, then renew all login info.
Applying that knowledge I tried, as others here have, resigning into the Google account on the Obi dashboard. That appeared to work, showing me signed in proper, but using the phone still got the no response from service provider message.
Solution for me: Delete the service provider profile entirely then set it up again. Phone works fine now.
The problem is likely that something in the sign in profile probably has expired. Setting it up fresh updates all embedded dates and (so far at least) satisfies Google server security requirements.
If it ain’t one thing, it’s another.
EDIT: FORGET IT. THIS ONLY WORKED FOR ONE CALL.
All four of us in my circle are having issues like this in the past 24 hours, my inbound calls routed through Call Centric are coming through and the valet service where I can call with my GV numbers using ny Call Centric numbers though the web interface are working fine.
Quote from: woland66 on June 11, 2021, 01:43:21 PM
So:
Two devices at the same IP -- not a connection problem
One of two obi's connects to GV -- not a google problem
Anveo works on obi with GV issue -- not an obi device problem.
At least one of those - the second one - is an unjustified conclusion.
After resigning in with google accounts it seemed to work for awhile. And then it would go out. Now that does not even seem to work.
I have had this issue several times over the past couple days. I looked into my obi this morning and noticed the uptime was 254 days so I rebooted. It hasn't connected since. I did a Wireshark capture during a power cycle of the obi and saw an "Unknown CA" error so I am assuming either Google or Obihai has a TLS certificate issue.
If I have two google voice numbers and use sp1 and sp2 for them...can Callcentric solution work for sp3?
Sounds appealing due to problems today and was looking for a 911 provider.
Want to be able to use GV numbers for outbound calling.
Need something to backup google voice token issues.
Quote from: Taoman on June 11, 2021, 01:23:32 PM
Quote from: magicwine on June 11, 2021, 12:57:50 PM
Hi - I found this article - is this current?
http://www.obitalk.com/forum/index.php?topic=17024.0
Yes, you can follow those instructions. If you choose the subscription Steve is referring to you will also get 120 outbound minutes per month in addition to unlimited inbound minutes plus E911.*
Yes, you would configure it on SP2. Unsure what you mean in the second part of that question. Incoming calls to your GV number will get forwarded to your Callcentric number which will then ring on your OBi device.
Yes, if you set up Callcentric you will need to disable call forwarding to your OBi device. Although it's not going to hurt anything if you don't. If GV is already not ringing your OBi device then it will ring on SP2 thru Callcentric. But if both SP1 and SP2 are working properly then SP1 will beat out SP2 every time since it is a direct route instead of being forwarded to Callcentric first.
*Note: if you configure Callcentric on SP2 and choose the subscription in question you will need to preface any number you want to call via Callcentric with **2. So it would look like:
**2888-555-1212
Quote from: Taoman on June 11, 2021, 11:54:53 AM
SteveInWA (who is not a Mod) has an Obihai/Poly contact. Hopefully he will see this and make some inquiries. I have seen a couple of the same error reports in the Google Voice support forum.
I no longer have contacts at Poly. My contacts left the company. However, as you know, I have contacts at Google, and I am going to escalate this problem.
Quote from: Mddd on June 11, 2021, 02:54:31 PM
If I have two google voice numbers and use sp1 and sp2 for them...can Callcentric solution work for sp3?
Absolutely. But I would suggest you go for the North American Basic plan ($1.95/month) which gives you 120 outbound minutes in addition to unlimited inbound and E911. You can have outbound calls display your GV number.
It really doesn't make financial sense to just pay for E911 and the unlimited DID when you can get 120 outbound minutes for an additional 45 cents.
I am so getting the error:
Connecting to 216.239.36.145;Token Error
The phone has dial tine, but is not able to place calls:
The number you dialed, xxx xxxx has not received a response from, the service provider."
UPDATE at 5pm PDT:
This issue is now being actively worked by Google and Poly. No action on your part is needed nor will fix it.
If/when I have new news to report, I'll do it here.
Thank you!
If this is a known issue being worked on, why is there NOTHING at all on the Obitalk website which says that this is a known issue? Wouldn't that save us all time wasted trying different things???
Can you please write additional information about your device that is having issues:
1. The model/version of your obi device
2. What's the version of the firmware that you are on
3. Have you tried to re-link it with google voice, if so did it work ?
All you need to know is that a) I discussed it with my Google contacts on the Google Voice team, and b) they know what's wrong and c) they're actively working the problem with Poly.
A. Fix ASAP
B. Next time, make the error something easily understood such as "Known system issue with Obihai, no need to troubleshoot your device" instead of "Token error" which means nothing to us consumers
Quote from: SteveInWA on June 11, 2021, 09:11:19 PM
All you need to know is that a) I discussed it with my Google contacts on the Google Voice team, and b) they know what's wrong and c) they're actively working the problem with Poly.
I rebooted the Obi a few hours ago when I was having the same issue as everybody else and it didn't work, so I saw this thread which was very helpful.
I can report that my Obi + GV is now working again, and I hope it isn't temporary, and I also hope it is fixed for everybody.
Voice.google.com did work for me throughout the outage.
Just wondering, did the "token error" just disappear or did you have to re-connect the device to google voice?
I've still got the token error on two different devices on two different google voice accounts.
And as you said google voice is working through chrome but not with Obi202.
Quote from: MSRobi on June 12, 2021, 07:27:13 AM
Quote from: SteveInWA on June 11, 2021, 09:11:19 PM
All you need to know is that a) I discussed it with my Google contacts on the Google Voice team, and b) they know what's wrong and c) they're actively working the problem with Poly.
I rebooted the Obi a few hours ago when I was having the same issue as everybody else and it didn't work, so I saw this thread which was very helpful.
I can report that my Obi + GV is now working again, and I hope it isn't temporary, and I also hope it is fixed for everybody.
Voice.google.com did work for me throughout the outage.
Consider yourself lucky. Still seeing token error on all of my devices and gv SPs.
Quote from: SteveInWA on June 11, 2021, 03:20:57 PM
I no longer have contacts at Poly. My contacts left the company. However, as you know, I have contacts at Google, and I am going to escalate this problem.
[/quote]
Thank you! Please keep us in the loop....
Quote from: SteveInWA on June 11, 2021, 09:11:19 PM
All you need to know is that a) I discussed it with my Google contacts on the Google Voice team, and b) they know what's wrong and c) they're actively working the problem with Poly.
Thank you for the update and assist in escalating the issue.
Using the google voice web page, I forwarded my calls to my cell phone until google and poly fix this.
Quote from: Justanod on June 12, 2021, 07:41:51 AM
Just wondering, did the "token error" just disappear or did you have to re-connect the device to google voice?
I've still got the token error on two different devices on two different google voice accounts.
And as you said google voice is working through chrome but not with Obi202.
I never did look at my dashboard, so I didn't see token error. I did get "No response from the service provider" when making outgoing calls, and then I noticed on the Obi202 the usually green lights where I connect the phones were off. A reboot did not help, as I said.
Then about an hour ago I noticed that the green lights to the phones came back on, and all is well since then. I didn't do anything except reboot the device several hours ago, and I don't think that made any difference. The problem is/was on the back end, and probably something simple like an expired certificate.
Just want to thank SteveinWA for escalating this and getting it worked on by both GV and Poly - thanks!
Well I decided to take Steveinwa's advice and set up callcentric account which will cost me about $30 a year. I now have 911 service and google voice backup which is strange as I am still using google voice number. With that said landline is up and running.
here is steveinwa link with instructions to set up callcentric using obitalk
http://www.obitalk.com/forum/index.php?topic=17024.msg103812#msg103812
Mine still not working. Rebooted, resigned in with GV log in, lights on, says registration not required.
Can not make calls.
When callingoutbound still says "the number has not gotten reaponse from the service provider"
Still not working for me "Registration not required" instead of "Connected"
(https://i.ibb.co/DRLrkfJ/Screen-Hunter-318-Jun-12-12-32.jpg)
All fixed for me, just started to work was down 4 days.
Thanks to who ever got this fixed!
I also successfully set a callcentric account with North Am plan plus a phone number plans..... backup for inbound. So at least one of my GV numbers rings cell phone and my Phones thru OBI.
Thanks for that tip, coming in handy right now until this is fixed.
I don't want to create a new thread, as I assume with the Google Voice issues and the same timing of my issue (~11 June thru today), this is all related... but... my symptoms:
- No Google Voice integration with ObiTalk and my Obi1022.
- Status however says "Connecting to 0.0.0.0" I've never seen anything about tokens or registrations.
- Behavior is: "Call Error" message when hitting the line button on the phone, amber light, if dialing from the recent numbers I get a "cannot be completed" tone, inbound Google Voice doesn't ring the ObiHai (but does work on my other linked phones). Rebooting has no effect, other than to sometimes turn the light green until trying and failing to make a call, at which point the light goes amber again.
- Interestingly: late afternoon ET 11 June, the service came up (after a reboot), I used it for a couple hours, then it went down again.
I assume this is all related to the same issues being worked w/ Google & Obi?
Thanks @SteveInWA for following-up on this.
My device stopped working again. I see "Registration Not Required" as the status on my Obi dashboard. The green lights on my Obi202 for phone lines are off again. I do get a dialtone, but after placing the call I get "No response from the service provider".
I reported this to Google Voice engineering staff yesterday afternoon. They have identified the problem and they are working with Poly to resolve it.
To be clear: no action on your part is necessary nor will fix it at this time. This outage is a good reminder that nobody should depend on Google Voice as their sole source of telephone service, and you can configure your OBiTALK device to use one or more other service providers, such as Callcentric or voip.ms.
I'm sorry, but I don't have any status update to report, since my Google contacts are off for the weekend. Nonetheless, it's safe to assume that they are working on it, and I will pass along any news I can get.
Quote from: TomForum on June 12, 2021, 09:59:41 AM
I don't want to create a new thread, as I assume with the Google Voice issues and the same timing of my issue (~11 June thru today), this is all related... but... my symptoms:
- No Google Voice integration with ObiTalk and my Obi1022.
- Status however says "Connecting to 0.0.0.0" I've never seen anything about tokens or registrations.
- Behavior is: "Call Error" message when hitting the line button on the phone, amber light, if dialing from the recent numbers I get a "cannot be completed" tone, inbound Google Voice doesn't ring the ObiHai (but does work on my other linked phones). Rebooting has no effect, other than to sometimes turn the light green until trying and failing to make a call, at which point the light goes amber again.
- Interestingly: late afternoon ET 11 June, the service came up (after a reboot), I used it for a couple hours, then it went down again.
I assume this is all related to the same issues being worked w/ Google & Obi?
Thanks @SteveInWA for following-up on this.
Yah, that sounds like a symptom of the same problem.
For the moment I've reassigned my cell as forwarding # in GV and turned on ringing in my tablet. I'm a boomer so not my favorite option but it works and can still take calls. Hope they resolve this soon. 😎
I have an OBI200 and OBI202. Neither work now.
I also have Google Fiber Internet and I have Centurylink DSL internet.
Last night I could get the OBI202 to work on Centurylink DSL internet but not on Google Fiber.
Both units say "Registration Not Required" and then turn to token error when connected to Google Fiber Internet.
Is Google blocking Poly units which are connected to Google Fiber?
They won't even show as registered in Google Voice now when I tried to re-do ObiTalk registration to Google Voice (yes, I removed the devices on Google Voice before I re-registered).
Quote from: FixItDad on June 12, 2021, 12:18:12 PM
I have an OBI200 and OBI202. Neither work now.
I also have Google Fiber Internet and I have Centurylink DSL internet.
Last night I could get the OBI202 to work on Centurylink DSL internet but not on Google Fiber.
Both units say "Registration Not Required" and then turn to token error when connected to Google Fiber Internet.
Is Google blocking Poly units which are connected to Google Fiber?
They won't even show as registered in Google Voice now when I tried to re-do ObiTalk registration to Google Voice (yes, I removed the devices on Google Voice before I re-registered).
Please read the entire thread. There's nothing we can do. Google and Polycom are working on it.
https://support.google.com/voice/thread/112962833/obi202-will-not-connect-to-gv?authuser=3&msgid=113251887
Seems to have been resolved. Got an email saying it’s reconnected. Outgoing calls work again. Incoming working too.
The nice thing with GV besides being free.......can have backup options like app and forwarding to cell phone.
And with the tip from here, I got another backup with callcentric account.
Appreciate the efforts and that it has been reported.
Quote from: Moonwalker on June 12, 2021, 01:02:16 PM
Seems to have been resolved.
Umm... I don't see no 'yellow triangles'... Still don't have outbound calls.
Same 'Registration not required'.
I'm OBi200. How do I make sure my firmware is upgraded?
Still not working for me either. When changing device parameters Configuration churns for quite a while but then still gives token error. Hopefully fix is in process or rolling out.
Negative on it being resolved (for me). Dashboard still showing:
Connect Failed: 403 Forbidden;Token Error
for 2 of my 3 GV lines. But they have been showing connected and then not periodically.
Have any of you tried refreshing your Google credentials? Delete the settings and sign in again?
That didn't work for me until just about an hour or two ago. I refreshed the credentials, then sometime afterward I got the email and it's now working again still. Not sure if that's the difference for me but it could be. It could also be that whatever fix was done may take time to fully propagate to all servers. If they actually fixed it that is.
I have the Home Base & the Obi 202,
Same issue.
Rebooted modem today as well...
NOte: (the 202 will not work if the homebase is not working, although it should, since it plugged directly into an extension router.)
6/12-- update 1: ON Homebase, attempted .. endless saying: Google Voice. Configuring, now says "Connecting to 0.0.0.0" again..
honestly, i do not remember how to get into what fire-ware we have... (as the website isn't very helpful)...
update 2:(yesterday phone stopped working, today deleted & re-added google, still didn't work... now 7p tried again and got his additional error.)
update 3: 6/13-- my 202 (2ndary port is trying to connect to "216.239.36.145" .
Connecting to 216.239.36.145;Token Error
while my HOmebase is still 0.0.0.0...
Do not recogized this IEP address, is this an OBI one????
If this is related to Google pulling the plug on Hangouts, then we're screwed...
Tried deleting device and recreating GV connection but no luck. Still "Registration Not Required" whatever this means.
Have refreshed credentials, yesterday and today. Sometimes it worked for a very short time. Other times not at all.
Quote from: Moonwalker on June 12, 2021, 02:21:28 PM
Have any of you tried refreshing your Google credentials? Delete the settings and sign in again?
That didn't work for me until just about an hour or two ago. I refreshed the credentials, then sometime afterward I got the email and it's now working again still. Not sure if that's the difference for me but it could be. It could also be that whatever fix was done may take time to fully propagate to all servers. If they actually fixed it that is.
Quote from: Mddd on June 12, 2021, 03:02:43 PM
Have refreshed credentials, yesterday and today. Sometimes it worked for a very short time. Other times not at all.
Quote from: Moonwalker on June 12, 2021, 02:21:28 PM
Have any of you tried refreshing your Google credentials? Delete the settings and sign in again?
That didn’t work for me until just about an hour or two ago. I refreshed the credentials, then sometime afterward I got the email and it’s now working again still. Not sure if that’s the difference for me but it could be. It could also be that whatever fix was done may take time to fully propagate to all servers. If they actually fixed it that is.
Yeah unfortunately mine is back to throwing the error again. I did say it “seemed” to be fixed, but what seems to be and what is is often not the same thing, Guess we’ll just have to wait until Google and Poly figure it out. In the meantime I recall when hardline phones sometimes went dead for days. At least we have alternate workarounds now. Back then your only choice was to get in your car and drive to whomever you wanted to talk with. Or just wait.
There is nothing you can do, the problem is not with your device, it isn't with refreshing google credentials, etc. It is out of our control.
I've been up and down all day, and the easiest way for me to tell is the green lights on my Obi202 where the phone lines are plugged in. If they are green, I'm working. If not, I'm not working and get "registration not required" or "token error" on my dashboard.
Fortunately GVoice is not affected, so I can use voice.google.com with my headset and make/receive calls. I also linked my cell phone to my GVoice account a long time ago, but usually don't forward to it because forwarding to OBi202 has been bulletproof until today. Now I have my GVoice number forwarding to my cell phone.
If things get really bad, I'll look into CallCentric.
Quote from: Hoeveer on June 12, 2021, 02:38:30 PM
If this is related to Google pulling the plug on Hangouts, then we're screwed...
I has nothing to do with hangouts. Hangouts and Voice have been disconnected from each other for a long time in anticipation of Chat, which isn't intended for calling or messaging phones at all. Voice has been designed for that from its inception. Google integrated Voice with Hangouts in the hopes of creating a one size fits all solution to communications. Technology and regulation changes killed that dream.
This is nothing more than a glitch in the authorization systems wherein Poly and Google auth systems aren't playing well together. More than likely because of something Google changed. It's happened before with other apps that couldn't, or just didn't, keep up with Google's changes.
Quote from: MSRobi on June 12, 2021, 03:45:48 PM
There is nothing you can do, the problem is not with your device, it isn't with refreshing google credentials, etc. It is out of our control.
I've been up and down all day, and the easiest way for me to tell is the green lights on my Obi202 where the phone lines are plugged in. If they are green, I'm working. If not, I'm not working and get "registration not required" or "token error" on my dashboard.
Fortunately GVoice is not affected, so I can use voice.google.com with my headset and make/receive calls. I also linked my cell phone to my GVoice account a long time ago, but usually don't forward to it because forwarding to OBi202 has been bulletproof until today. Now I have my GVoice number forwarding to my cell phone.
If things get really bad, I'll look into CallCentric.
THIS^^^^^^^^^^^
While awaiting a fix between Poly-GV, I tried to place calls directly from the GV web interface using my PC and Chrome browser. For some reason the phone button icon you click to dial is greyed out (web UI).
I'm assuming this shouldn't be related to the current Poly-GV issues because another forum stated even if Polycom devices are having issues, that using the GV app or the browser interface directly supposedly still works fine because they are unrelated to Obi devices.
However, as stated, my Dial (call) button is greyed out. So, anyone else newly experiencing this? Could this somehow still be related? Or should I treat/troubleshoot this as a separate issue? I will add that - Google recently sent me an email stating my "Linked number" will be removed unless I requested otherwise. But the wording sounded as if it would NOT affect service, and appeared to be just a house-keeping effort on unused phone numbers.
Any ideas? Is it related, unrelated? Thanks...
Quote from: G-Man on June 12, 2021, 04:23:05 PM
While awaiting a fix between Poly-GV, I tried to place calls directly from the GV web interface using my PC and Chrome browser. For some reason the phone button icon you click to dial is greyed out (web UI).
It is unrelated. Mine is greyed out until I enter a valid phone number to call, then it becomes enabled. If yours is still disabled, go into settings, "My devices", is "Web" one of the choices and is it on (green)?
I'm also getting a, "Call Failed - 901" error and an orange light on the phone at 8:05 EST.
(ingers crossed on a quick fix from GV and Poly!)
See:
http://www.obitalk.com/forum/index.php?topic=18323.msg108788#msg108788
From other topic:
Quote from: SamirLatif on June 12, 2021, 04:07:57 PM
Looked around other website and this instructions worked for me. Copy and pasting it here for the rest. Hope this will resolve the same issue that I have:
Here's what I managed to do to get both my Obihai devices (200 & 202) "connected" and working again. (Yes, I suffered from the "registration not required", as well as the "token", issues).
In the Obitalk home page, select the desired device ... and then click "OBi Expert Configuration". Confirm that you actually want to go to that screen.
Then click "Enter OBi Expert"
On the left panel, under "Production Information" select:
SYSTEM MANAGEMENT » WAN Settings → or ←
ROUTER CONFIGURATION » WAN SETTINGS (menu changes between 200 & 202)
You then need to unclick the check marks under "OBiTALK Settings" for:
"DefaultGateway"
"DNSServer1"
"DNSServer2"
The check mark of the above 3 items will switch to "Device Default"; unclick those as well.
Default gateway is the IP of your home/business router
DNSServer1 I set to: "1.1.1.1" and DNSServer2 I set to "8.8.8.8"
Save the settings and then reboot your device.
Changing the Default Gateways ... and indicating the proper DNS servers to utilize brought me back to up-and-running; hope it does the same for you!
My comment:
You do not need to change Default Gateway
Just set
DNSServer1 to 1.1.1.1
DNSServer2 to 8.8.8.8
Wait few minutes and it will work.
I agree that you don't have to change the default gateway. The default gateway showing in "Status" was already correct without touching it. I did change DNS 1/2, waited for the device to get the changes from Obi Expert, then for good measure rebooted the device.
I've had a "Connected" status in my dashboard and green lights on my phone ports on the Obi202 ever since (about 15 minutes now). But I've been going up and down all day without touching anything, so I'm a bit suspicious that this could just be coincidental.
On the other hand, it could very well be a DNS server problem between Poly and GV, and this change solves the problem.
Quote from: Dmitry on June 12, 2021, 05:22:44 PM
My comment:
You do not need to change Default Gateway
Just set
DNSServer1 to 1.1.1.1
DNSServer2 to 8.8.8.8
Wait few minutes and it will work.
This worked... There must be something that needs to propagate from the google dns before it will work more widely.
Can someone explain what changing the DNS settings as recommended actually does to enable this "fix?" It seems to be working so far for me.
Quote from: Marc on June 12, 2021, 05:52:19 PM
This worked... There must be something that needs to propagate from the google dns before it will work more widely.
That's what I was thinking but 1.1.1.1 is not a Google DNS server. So unless the secondary Google DNS server is doing the magic I don't get it.
It probably doesn't have to be a google DNS server. I did "ping 1.1.1.1" and got a response, so it is a valid IP address. I already knew about 8.8.8.8 being a google DNS server. So is 8.8.4.4. My hunch is if you changed 1.1.1.1 to 8.8.4.4 it would also work.
Edit: 1.1.1.1 is a DNS server by Cloudflare
Quote from: Moonwalker on June 12, 2021, 03:48:27 PM
Quote from: MSRobi on June 12, 2021, 03:45:48 PM
I've been up and down all day, and the easiest way for me to tell is the green lights on my Obi202 where the phone lines are plugged in. If they are green, I'm working. If not, I'm not working and get "registration not required" or "token error" on my dashboard.
Just a clarification - or at least a difference experience for me...
*All lights on my Obi200 are green - Obitalk web dashboard says 'registration not required'
*Pick up phone and get a dial tone - dial any number and get a recording saying no response rec'd from service provider
*Then phone LED on Obi200 isn't lit at all, and Obitalk web dashboard says 'connecting to xxxIPxxx; token error'
Can receive GV calls on web and mobile phone, but not on phone connected to Obi200 - cannot make outgoing calls on GV web, but can on GV mobile app.
I don't think switching obi to cloudflare/google dns is going to help and/or it's a good idea. Judging by the error I've got, this is an issue between Obi and Google Voice API. Switching DNS and other tricks may beg us through authorization, but we'll ever know which other API limit may be reached.
I would wait and look for alternative to google voice in a meantime :)
I'm still up and running this morning. I'm not quite ready to declare victory though.
http://www.obitalk.com/forum/index.php?topic=18329.msg108740#msg108740
Quote from: MSRobi on June 13, 2021, 04:08:04 AM
I'm still up and running this morning. I'm not quite ready to declare victory though.
Most of us still have no service as of 6/13 a.m. Please, folks - when reporting "success" here - also include your model. 200 or 202? There does appear to be a difference.
I am very surprised more people are not seeing this problem resolved.
My service was interrupted 3-5 days ago, like everyone else the token error connecting to Google Cloud was showing in the dashboard.
I tried removing the device, hard reset/soft reset 3-4 times wasting a couple of hours to no prevail.
I left the unit plugged in and active.
Yesterday in the morning a call came in and it was working. I made 2-3 calls no issue all back to normal.
Other users got the service back around the same time as shown in a few posts.
The question then is why did this start working for some and not others???
With Google it is always a secret, possible they made a change that worked for some users, maybe related to the ISP used??
Anyway still working this am, problem gone.
Thank to whoever did whatever.
Obi 200/Spectrum
OBI200. Same situation as everyone else. Multiple resets etc and still no service as of 9 AM EST. By the way the phone light is not on. Should it be? It comes on during the reset process but then goes off so it is not the LED bulb.
I continue to see this issue on my 200 box—get several emails each day with it losing connection/reconnecting.
Quote from: awriter on June 13, 2021, 05:15:50 AM
Quote from: MSRobi on June 13, 2021, 04:08:04 AM
I'm still up and running this morning. I'm not quite ready to declare victory though.
Most of us still have no service as of 6/13 a.m. Please, folks - when reporting "success" here - also include your model. 200 or 202? There does appear to be a difference.
Despite my relatively good understanding of DNS, I'm not going to pretend to understand way 1.1.1.1/8.8.8.8 is a solution, albeit temporary, to the issue we've all been experiencing. But it 'appears' to be a viable workaround.
These are the devices on which I've made the DNS change and all are now connected to GV accounts, multiple on most of these, and I can make and received calls. And no, I'm not declaring victory nor saying the issue has been resolved! I'm simply saying that what @SamirLatif discovered, is a viable work around.
OBi200 x 2
Polycom 200 x 1
OBi202 x 1
OBi1032 x 2
OBi1062 x 1
OBi2182 x 3
If you've made changes to the DNS and have not had positive results, check to make sure that you don't have DNS (53) blocked on your network from all but your normal chosen provider. I normally have it locked down and had to disable the firewall rule on my phone VLAN in order to see this change work.
Please remember, this is the last update we've received on this issue:
http://www.obitalk.com/forum/index.php?topic=18329.msg108740#msg108740
Looks like you found the smoking gun...
Quote from: igor@chysiuk.com on June 12, 2021, 10:17:47 PM
I don't think switching obi to cloudflare/google dns is going to help and/or it's a good idea. Judging by the error I've got, this is an issue between Obi and Google Voice API. Switching DNS and other tricks may beg us through authorization, but we'll ever know which other API limit may be reached.
I would wait and look for alternative to google voice in a meantime :)
Thank you for this. Your post should be pinned at the top of every post with this issue.
Dumb question: Can I have the same number on GV and also voip.ms so that if one goes down, the other will automatically take over? Or will I need 2 separate numbers?
Quote from: SteveInWA on June 12, 2021, 11:13:37 AM
I reported this to Google Voice engineering staff yesterday afternoon. They have identified the problem and they are working with Poly to resolve it.
To be clear: no action on your part is necessary nor will fix it at this time. This outage is a good reminder that nobody should depend on Google Voice as their sole source of telephone service, and you can configure your OBiTALK device to use one or more other service providers, such as Callcentric or voip.ms.
I'm sorry, but I don't have any status update to report, since my Google contacts are off for the weekend. Nonetheless, it's safe to assume that they are working on it, and I will pass along any news I can get.
My OBi200 is working right now. Looks like everything is back to normal. Looks like they fixed it. I can receive and call now. The status for my two Google Voice lines are saying "Connected" like normal.
I did have to power off and on the Obi200. Deleted the device from the Google Voice account in the setting and in my OBi account tab then re-added the device in my OBi account like almost an hour ago.
UPDATE: Now it's back to "Registration Not Required".
i'm in nyc using obitalk and for the past 2 days had the same issue as you guy. log into obitalk and got the token error. today is 6/13/21 and as of 10:46 am est, it is still saying token error.
am i supposed to do something or it will eventually start working again? someone please help.
What is the numeric ip address for obihai.sip.google.com please? I tried changing the dns to 1.1.1.1 and 8.8.8.8; however, I still cannot ping obihai.sip.google.com.
I did replace the Default DNS providers with the 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google) and the OBi202 is still not working.
Deleted the device from Google account and it won't show up anymore when setting it up from OBiTalk webpage.
obihai.sip.google.com doesn't resolve to anything
Thanks so much for the workaround provided by SamirLatif. My connection is now working (OBi200)
Quote from: derrickearly on June 13, 2021, 07:53:42 AM
What is the numeric ip address for obihai.sip.google.com please? I tried changing the dns to 1.1.1.1 and 8.8.8.8; however, I still cannot ping obihai.sip.google.com.
NSLOOKUP cannot find obihai.sip.google.com or sip.google.com using 8.8.8.8 or 8.8.4.4 or 1.1.1.1 or ns1.google.com
*** dns.google can't find sip.google.com: Non-existent domain
So either Google shut down SIP of google voice, or the A Record was removed on purpose or by attack.
I also noticed Comcast is using only IPv6 for DNS inquiries. It's possible efforts to harden against ransomware or other attacks have google scrambling to secure its subdomains and connections?
In any case, until the A record for sip.google.com is restored, no obihai.sip.google.com, no GV connection.
Read http://www.obitalk.com/forum/index.php?topic=18329.msg108740#msg108740 and take note of the words:
"no action on your part is necessary nor will fix it at this time."
Quote from: jccpa on June 13, 2021, 08:08:17 AM
In any case, until the A record for sip.google.com is restored, no obihai.sip.google.com, no GV connection.
I guess GV application and browser interface don't use the sip.google.com? Because those work.
Just chiming in that as of 11:00 AM EDT in Florida, I still cannot get mine, my sisters, or either of my two friends OBi202's to connect. Many other people have said they got it working by manually setting DNS but that has not worked for me, nor has many hours of tinkering including resetting everything and starting over from scratch. I have a spare OBi202 and can't get it working either.
My DNS entries were already set to 1.1.1.1 (CloudFlare) and 8.8.8.8 (Google) but I went ahead and reversed the order and put the Google DNS first. Static IP, Gateway, Mask are all correctly set as well.
I did notice a couple of things no-one else has mentioned though. First, when you try to reconnect the OBi to Google, the Terms-of-Service you are supposed to agree to comes up blank. The 'Accept' button is there though, and apparently works for you to accept the invisible terms.
Second, I tried deleting/resetting everything as mentioned, including deleting the OBi device from my list of GV devices. After going thru the whole setup process over again from scratch, it has NOT re-added my OBi device to my GV device list, and I see no way to add it from the GV settings page.
And for what its worth, my ISP is AT&T fiber (but not using their DNS). I guess none of this is relevant though if the obihai.sip.google.com address won't resolve. Mostly I think I just wanted to vent 🤬 that it still is not working here. The other people I mentioned bought OBi devices upon my recommendation so this is making me look bad!
If ANYONE who is still working could please get the IP Address of obihai.sip.google.com for us? Here's how.
Windows key + R
cmd (enter)
ping obihai.sip.google.com
Post up the IP address in brackets right after google.com
It is *possible that the server is still up and working, but the DNS entry and resolution are fubar
ping: cannot resolve obihai.sip.google.com: Unknown host
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
For the curious:
If you go to your voice.google.com account, under Legacy Google Voice, Phones, select your OBi device or phone.
Under 'Number' you will see a long code of letters and numbers, followed by '===@obihai.sip.google.com'
This means GV MUST connect to obihai.sip.google.com
That name does not resolve under DNS and cannot be contacted, at least not by name.
Although a few systems may still have had that name's IP address cached, those will be expiring as time goes on.
**If someone whose system still is cached and can give the IP address by pinging it, we might be able to add the domain to a hosts file or RIP table until the DNS is fixed. At this point I cannot yet confirm the server is still operational until someone provides the IP address.
These are troubleshooting techniques and temporary tests/workarounds. Nothing for a typical user to configure or do. Our collective hope is by providing info about the failure and the precise problem, that the right folks will get the info and perhaps speed up their corrective actions.
Quote from: GeeObi on June 13, 2021, 09:10:29 AM
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
Can you ping that URL and give us the IP Address, it doesn't resolve via DNS, either
I've used GV and Obihai for 10 years (bought an early Obi100) and it has been very reliable up until this outage. In the first couple years, it had more issues, but that could have been due to slower internet speeds when 5 or 10 or 15 MBPS up/down were considered fast. I'm still hopeful this will all get resolved soon and let your family and friends know it has been great overall. Right now, I just make calls through my PC and browser or iPad and GV app.
FYI - my fathers Obi200 in CA is showing connected, but my mother-in-laws Obi200 in MD is showing "Connecting to 216.239.36.145;Token Error" even though configurations are very similar (dns 1.1.1.1. and 8.8.8.8.). My two Obi202s are also having the same token error
Quote from: DoctorWizard on June 13, 2021, 08:46:32 AM
Just chiming in that as of 11:00 AM EDT in Florida, I still cannot get mine, my sisters, or either of my two friends OBi202's to connect. Many other people have said they got it working by manually setting DNS but that has not worked for me, nor has many hours of tinkering including resetting everything and starting over from scratch. I have a spare OBi202 and can't get it working either.
My DNS entries were already set to 1.1.1.1 (CloudFlare) and 8.8.8.8 (Google) but I went ahead and reversed the order and put the Google DNS first. Static IP, Gateway, Mask are all correctly set as well.
I did notice a couple of things no-one else has mentioned though. First, when you try to reconnect the OBi to Google, the Terms-of-Service you are supposed to agree to comes up blank. The 'Accept' button is there though, and apparently works for you to accept the invisible terms.
Second, I tried deleting/resetting everything as mentioned, including deleting the OBi device from my list of GV devices. After going thru the whole setup process over again from scratch, it has NOT re-added my OBi device to my GV device list, and I see no way to add it from the GV settings page.
And for what its worth, my ISP is AT&T fiber (but not using their DNS). I guess none of this is relevant though if the obihai.sip.google.com address won't resolve. Mostly I think I just wanted to vent 🤬 that it still is not working here. The other people I mentioned bought OBi devices upon my recommendation so this is making me look bad!
Quote from: jccpa on June 13, 2021, 08:54:53 AM
If ANYONE who is still working could please get the IP Address of obihai.sip.google.com for us? Here's how.
Windows key + R
cmd (enter)
ping obihai.sip.google.com
Post up the IP address in brackets right after google.com
It is *possible that the server is still up and working, but the DNS entry and resolution are fubar
Interesting.
>ping obihai.sip.google.com
Ping request could not find host obihai.sip.google.com. Please check the name and try again.
I tried various web based DNS lookups and saw the same. Google's lookup return results. I changed my primary DNS server to Google's 8.8.8.8, rebooted and now have phone service again.
https://dns.google.com/query?name=obihai.sip.google.com
That's a temporary fix.
Do as I posted above for a permanent fix.
to GeeObi :
Quote from: GeeObi on June 13, 2021, 09:35:38 AM
That's a temporary fix.
Do as I posted above for a permanent fix.
I got to expert set up but could not find the ones you refered to ! Can you give more details . Thks
Quote from: GeeObi on June 13, 2021, 09:10:29 AM
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
Under Service Providers -> ITSP Profile A General, I found the STUNserver and X_STUNServerPort settings already as suggested. All I needed to change was the checkbox for STUNEnable.
But sadly, this change accomplished nothing.
I used the local GUI on mine but if you normally make changes to your device through the Obitalk portal then you'll have to do it there otherwise the portal will overwrite your changes and will be back to the way it was.
Quote from: GeeObi on June 13, 2021, 10:28:22 AM
I used the local GUI on mine but if you normally make changes to your device through the Obitalk portal then you'll have to do it there otherwise the portal will overwrite your changes and will be back to the way it was.
I used the Obitalk portal, and as for @Mickey613, it didn't work (I also only needed to check STUNEnable on ITSP Profile A General).
I went back and unchecked it. It now has a red exclamation next to the unchecked box....
http://www.obitalk.com/forum/index.php?topic=18389.0
It should look like this:
Obi2xx device contacts Google OAuth server to refresh token.
Google OAuth server address is www.googelapis.com
If changing DNS works, it may be related to the fact that different DNS servers may return different IPs for this server.
Can anyone post the dns resolution output:
In Mac computer:
# Get answer from your ISP DNS server
dig www.googelapis.com
# Get answer from specific DNS server
dig @1.1.1.1 www.googleapis.com
Please also include your city/state.
Quote from: GeeObi on June 13, 2021, 11:01:31 AM
It should look like this:
It looks like that (but slightly different layout for me). I unchecked STUNEnable since it didn't help. See image here:
https://i.gyazo.com/ac54496c7b678553a3cbbb70beb65aa0.png (https://i.gyazo.com/ac54496c7b678553a3cbbb70beb65aa0.png)
Quote from: SteveInWA on June 12, 2021, 11:13:37 AM
I reported this to Google Voice engineering staff yesterday afternoon. They have identified the problem and they are working with Poly to resolve it.
To be clear: no action on your part is necessary nor will fix it at this time. This outage is a good reminder that nobody should depend on Google Voice as their sole source of telephone service, and you can configure your OBiTALK device to use one or more other service providers, such as Callcentric or voip.ms.
I'm sorry, but I don't have any status update to report, since my Google contacts are off for the weekend. Nonetheless, it's safe to assume that they are working on it, and I will pass along any news I can get.
Hey Steve,
You have my thanks for reaching out on behalf of the community. Please know, that there are people who are thankful for people like yourself. I think people fail to appreciate after buying their OBi (or other) device that they are getting completely free service through Google Voice and expect that free service to always be perfect. I was only relying on Google Voice before. I am using mine as a business phone, I will probably follow your CallCentric guide later today so I have a viable backup. Thanks again!
This didn't achieve even a temporary fix, for me.
Quote from: GeeObi on June 13, 2021, 09:10:29 AM
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
Quote from: GeeObi on June 13, 2021, 09:10:29 AM
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
NO fix!
I tried these changes via OBI expert and via the built in UI of the device (local IP). Also rebooted after each change.
Still exactly the same token error!
Will undo these changes.
Quote from: jccpa on June 13, 2021, 08:08:17 AM
NSLOOKUP cannot find obihai.sip.google.com or sip.google.com using 8.8.8.8 or 8.8.4.4 or 1.1.1.1 or ns1.google.com
*** dns.google can't find sip.google.com: Non-existent domain
So either Google shut down SIP of google voice, or the A Record was removed on purpose or by attack.
In any case, until the A record for sip.google.com is restored, no obihai.sip.google.com, no GV connection.
obihai.sip.google.com has never had an A record or SRV record. It doesn't matter. Whenever there is an OutboundProxy setting it overrides any Proxy server setting.
All SIP requests go to
obihai.telephony.goog, not obihai.sip.google.com. From there it gets redirected as needed.
Look at many of the error messages people are getting:"Connecting to 216.239.36.145;Token Error"
And what does 216.239.36.145 resolve to? The OutboundProxy setting which is
obihai.telephony.goog.
You're wasting your time worrying about obihai.sip.google.com.
Quote from: ppan on June 13, 2021, 11:16:21 AM
Quote from: GeeObi on June 13, 2021, 11:01:31 AM
It should look like this:
It looks like that (but slightly different layout for me). I unchecked STUNEnable since it didn't help. See image here:
https://i.gyazo.com/ac54496c7b678553a3cbbb70beb65aa0.png (https://i.gyazo.com/ac54496c7b678553a3cbbb70beb65aa0.png)
That's exactly the settings I had BEFORE making any changes. I'm still down with or without this setting change.
Quote from: GeeObi on June 13, 2021, 09:10:29 AM
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
The purpose of a STUN server is to allow the local client to traverse your local NAT successfully. The current issue some people are experiencing is not related to any STUN setting.
Your OBi device may have connected after making a STUN setting change but I guarantee it was purely coincidental.
The following was recently posted on Reddit supposedly by a Google Voice engineer:
QuoteGV eng here: There is some kind of OAuth refresh token problem with some devices. We haven't been able to track it down as of yet. It seems to be only affecting some OBiTALK devices, but it's unclear why because neither us nor Polycom have rolled anything out that would do this, not that we know of at least. We are continuing to investigate, but Google has no access to the devices so there's not a lot to go on. If you have paid support from Polycom, please open a support case with them and give them the serial number of the device that is malfunctioning so they can pull its system logs.
https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1m05vh?utm_source=share&utm_medium=web2x&context=3 (https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1m05vh?utm_source=share&utm_medium=web2x&context=3)
Just ported my Google Voice number to a different Service Provider (Anveo). Didn't realize how dependent I'd become on the VoIP line. Hard to complain given that GV was free.
You are 100% correct, obihai.sip.google.com is just SIP realm name: http://docs.intenogroup.com/v312/en/glossary/s/sip_realm#:~:text=A%20SIP%20realm%20is%20a,as%20a%20the%20SIP%20domain.
216.239.36.145 is the real SIP registration server: obihai.telephony.goog
But before SIP registration, it needs to get OAuth token from another Google server: www.googleapis.com
If changing DNS works, it may be related to the fact that different DNS servers may return different IPs for this server.
Can anyone post the dns resolution output:
In Mac computer:
# Get answer from your ISP DNS server
dig www.googelapis.com
# Get answer from specific DNS server
dig @1.1.1.1 www.googleapis.com
Please also include your city/state.
Quote from: Taoman on June 13, 2021, 11:36:39 AM
Quote from: jccpa on June 13, 2021, 08:08:17 AM
NSLOOKUP cannot find obihai.sip.google.com or sip.google.com using 8.8.8.8 or 8.8.4.4 or 1.1.1.1 or ns1.google.com
*** dns.google can't find sip.google.com: Non-existent domain
So either Google shut down SIP of google voice, or the A Record was removed on purpose or by attack.
In any case, until the A record for sip.google.com is restored, no obihai.sip.google.com, no GV connection.
obihai.sip.google.com has never had an A record or SRV record. It doesn't matter. Whenever there is an OutboundProxy setting it overrides any Proxy server setting.
All SIP requests go to obihai.telephony.goog, not obihai.sip.google.com. From there it gets redirected as needed.
Look at many of the error messages people are getting:"Connecting to 216.239.36.145;Token Error"
And what does 216.239.36.145 resolve to? The OutboundProxy setting which is obihai.telephony.goog.
You're wasting your time worrying about obihai.sip.google.com.
I got an ONLINE note from Obitalk at 13:45 CDT 2021-06-13. Thanks, @SteveInWa for reaching out to Google!
Quote from: Jasmine10 on June 13, 2021, 12:52:09 PM
But before SIP registration, it needs to get OAuth token from another Google server: www.googleapis.com
If changing DNS works, it may be related to the fact that different DNS servers may return different IPs for this server.
Right. Someone posted a SIP trace and it points to a cert issue. I would guess this is correct as it has happened before.
QuoteI did a packet capture and get a "Unknown CA error" so it looks like a certificate issue.
Transport Layer Security
TLSv1.2 Record Layer: Alert (Level: Fatal, Description: Unknown CA)
Content Type: Alert (21)
Version: TLS 1.2 (0x0303)
Length: 2
Alert Message
Level: Fatal (2)
Description: Unknown CA (48)
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: www.googleapis.com
Addresses: 2607:f8b0:400a:80a::200a
2607:f8b0:400a:806::200a
2607:f8b0:400a:805::200a
2607:f8b0:400a:807::200a
142.250.217.106
142.251.33.106
142.250.217.74
172.217.14.234
142.250.69.202
172.217.14.202
142.251.33.74
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.googleapis.com
Addresses: 2607:f8b0:400a:803::200a
2607:f8b0:400a:805::200a
2607:f8b0:400a:807::200a
2607:f8b0:400a:806::200a
172.217.14.234
142.250.69.202
142.251.33.106
142.251.33.74
142.250.217.74
142.250.217.106
172.217.14.202
Server: cdns01.comcast.net
Address: 75.75.75.75
Non-authoritative answer:
Name: www.googleapis.com
Addresses: 2607:f8b0:400a:805::200a
2607:f8b0:400a:807::200a
2607:f8b0:400a:806::200a
2607:f8b0:400a:803::200a
142.250.69.202
142.251.33.106
142.251.33.74
142.250.217.74
142.250.217.106
172.217.14.202
172.217.14.234
Edit: Near Seattle, WA and GV has stayed connected to 2 GV accounts on multiple OBi devices.
Quote from: Jasmine10 on June 13, 2021, 12:52:09 PM
If changing DNS works, it may be related to the fact that different DNS servers may return different IPs for this server.
So is your OBi device not connecting to GV? If so, are you able to do a TCPdump? That's what the GV engineer was asking for. I posted the SIP trace but that wasn't enough. All my OBi devices are connecting normally so a TCPdump from me would do no good.
https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1mm753?utm_source=share&utm_medium=web2x&context=3 (https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1mm753?utm_source=share&utm_medium=web2x&context=3)
Obi 200 still out in New England at 4:30 pm EST. Still shows either token error or registration not required.
However... I just discovered that Alexa can call out using my GV number, no problem! And there's one within the sound of my voice all around the house.
If you have an Echo, give it a try.
Hi, Taoman,
Thanks for your help.
So 1.1.1.1 and 8.8.8.8 work, but 75.75.75.75 doesn't work, correct?
Quote from: Taoman on June 13, 2021, 01:06:10 PM
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: www.googleapis.com
Addresses: 2607:f8b0:400a:80a::200a
2607:f8b0:400a:806::200a
2607:f8b0:400a:805::200a
2607:f8b0:400a:807::200a
142.250.217.106
142.251.33.106
142.250.217.74
172.217.14.234
142.250.69.202
172.217.14.202
142.251.33.74
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.googleapis.com
Addresses: 2607:f8b0:400a:803::200a
2607:f8b0:400a:805::200a
2607:f8b0:400a:807::200a
2607:f8b0:400a:806::200a
172.217.14.234
142.250.69.202
142.251.33.106
142.251.33.74
142.250.217.74
142.250.217.106
172.217.14.202
Server: cdns01.comcast.net
Address: 75.75.75.75
Non-authoritative answer:
Name: www.googleapis.com
Addresses: 2607:f8b0:400a:805::200a
2607:f8b0:400a:807::200a
2607:f8b0:400a:806::200a
2607:f8b0:400a:803::200a
142.250.69.202
142.251.33.106
142.251.33.74
142.250.217.74
142.250.217.106
172.217.14.202
172.217.14.234
Edit: Near Seattle, WA and GV has stayed connected to 2 GV accounts on multiple OBi devices.
Quote from: Jasmine10 on June 13, 2021, 01:46:02 PM
Hi, Taoman,
Thanks for your help.
So 1.1.1.1 and 8.8.8.8 work, but 75.75.75.75 doesn't work, correct?
Not using Comcast's DNS servers. Using 8.8.8.8 as primary and 8.8.4.4 as secondary.
My OBi is working, so we need someone with a failed device to do a TCPdump.
Quote from: Taoman on June 13, 2021, 01:26:11 PM
So is your OBi device not connecting to GV? If so, are you able to do a TCPdump? That's what the GV engineer was asking for. I posted the SIP trace but that wasn't enough. All my OBi devices are connecting normally so a TCPdump from me would do no good.
https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1mm753?utm_source=share&utm_medium=web2x&context=3 (https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1mm753?utm_source=share&utm_medium=web2x&context=3)
Can you provide DNS resolution output for www.googelapis.com with 1.1.1.1?
Also the output of below command if you are on Mac or Linux:
curl -v --tlsv1.2 "https://www.googleapis.com/"
Quote from: SoNic67 on June 13, 2021, 08:01:44 AM
I did replace the Default DNS providers with the 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google) and the OBi202 is still not working.
Deleted the device from Google account and it won't show up anymore when setting it up from OBiTalk webpage.
obihai.sip.google.com doesn't resolve to anything
Can you provide DNS resolution output for www.googelapis.com with your ISP DNS?
Also the output of below command if you are on Mac or Linux:
curl -v --tlsv1.2 "https://www.googleapis.com/"
Quote from: awriter on June 13, 2021, 01:39:01 PM
Obi 200 still out in New England at 4:30 pm EST. Still shows either token error or registration not required.
However... I just discovered that Alexa can call out using my GV number, no problem! And there's one within the sound of my voice all around the house.
If you have an Echo, give it a try.
on Win10
>curl -v --tlsv1.2 "https://www.googleapis.com/"
* Trying 142.251.33.202...
* TCP_NODELAY set
* Connected to www.googleapis.com (142.251.33.202) port 443 (#0)
* schannel: SSL/TLS connection with www.googleapis.com port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: sending initial handshake data: sending 189 bytes...
* schannel: sent initial handshake data: sent 189 bytes
* schannel: SSL/TLS connection with www.googleapis.com port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with www.googleapis.com port 443 (step 2/3)
* schannel: encrypted data got 2937
* schannel: encrypted data buffer: offset 2937 length 4096
* schannel: sending next handshake data: sending 93 bytes...
* schannel: SSL/TLS connection with www.googleapis.com port 443 (step 2/3)
* schannel: encrypted data got 292
* schannel: encrypted data buffer: offset 292 length 4096
* schannel: SSL/TLS handshake complete
* schannel: SSL/TLS connection with www.googleapis.com port 443 (step 3/3)
* schannel: stored credential handle in session cache
> GET / HTTP/1.1
> Host: www.googleapis.com
> User-Agent: curl/7.55.1
> Accept: */*
>
* schannel: client wants to read 102400 bytes
* schannel: encdata_buffer resized 103424
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: encrypted data got 1974
* schannel: encrypted data buffer: offset 1974 length 103424
* schannel: decrypted data length: 1401
* schannel: decrypted data added: 1401
* schannel: decrypted data cached: offset 1401 length 102400
* schannel: encrypted data length: 544
* schannel: encrypted data cached: offset 544 length 103424
* schannel: decrypted data length: 515
* schannel: decrypted data added: 515
* schannel: decrypted data cached: offset 1916 length 102400
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: decrypted data buffer: offset 1916 length 102400
* schannel: schannel_recv cleanup
* schannel: decrypted data returned 1916
* schannel: decrypted data buffer: offset 0 length 102400
< HTTP/1.1 404 Not Found
< Content-Type: text/html; charset=UTF-8
< Referrer-Policy: no-referrer
< Content-Length: 1561
< Date: Sun, 13 Jun 2021 21:25:22 GMT
< Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
<
<!DOCTYPE html>
<html lang=en>
<meta charset=utf-8>
<meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
<title>Error 404 (Not Found)!!1</title>
<style>
*{margin:0; ...
</style>
<a href=//www.google.com/><span id=logo aria-label=Google></span></a>
<p><b>404.</b> <ins>That's an error.</ins>
<p>The requested URL <code>/</code> was not found on this server. <ins>That's all we know.</ins>
* Connection #0 to host www.googleapis.com left intact
Quote from: PusBucket on June 13, 2021, 11:25:11 AM
This didn't achieve even a temporary fix, for me.
Quote from: GeeObi on June 13, 2021, 09:10:29 AM
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
that dude is lying out of his buttcheek. i ignore dude like him.
Quote from: PusBucket on June 13, 2021, 11:25:11 AM
This didn't achieve even a temporary fix, for me.
Quote from: GeeObi on June 13, 2021, 09:10:29 AM
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
For gawd's sake; ignore all alleged fixes by random users on the Internet. None of them will solve the problem, which is on the Poly/Google interface backend. You can't fix this yourself.
Quote from: TheFoxRocks on June 13, 2021, 11:21:50 AM
Quote from: SteveInWA on June 12, 2021, 11:13:37 AM
I reported this to Google Voice engineering staff yesterday afternoon. They have identified the problem and they are working with Poly to resolve it.
To be clear: no action on your part is necessary nor will fix it at this time. This outage is a good reminder that nobody should depend on Google Voice as their sole source of telephone service, and you can configure your OBiTALK device to use one or more other service providers, such as Callcentric or voip.ms.
I'm sorry, but I don't have any status update to report, since my Google contacts are off for the weekend. Nonetheless, it's safe to assume that they are working on it, and I will pass along any news I can get.
Hey Steve,
You have my thanks for reaching out on behalf of the community. Please know, that there are people who are thankful for people like yourself. I think people fail to appreciate after buying their OBi (or other) device that they are getting completely free service through Google Voice and expect that free service to always be perfect. I was only relying on Google Voice before. I am using mine as a business phone, I will probably follow your CallCentric guide later today so I have a viable backup. Thanks again!
Thanks for your kind words. Yeah, I have been spending most of the weekend on this, between this forum, the official Google Voice Help Community, Reddit, and chats with Google Voice staff.
As always, the "tough love" statement: Consumer Google Voice has never been intended nor recommended for business use. This a perfect example of why. Any pittance in phone bills saved by using consumer GV is quickly offset by loss of business or reputation when clients/customers can't reach you. Google does have a business-class, paid service (https://cloud.google.com/voice/ (https://cloud.google.com/voice/)) or use a reliable, proven SIP ITSP such as Callcentric, voip.ms, etc.
My Obi200 has been having this issue since last few days.
Just for the sake of, i deleted my device from obitalk.com and reconfigured it. I am now connected to google voice service. I am not too sure if this will work for all or if this is just a temporary resolution, but would be worth a try.
Here are some high level steps:
1) Log on to ObiTalk.com
2) Click on Device Configuration on the left side.
3) Click Delete Device in Device Information tab.
4) Once the device is deleted, click Add Device.
5) Follow prompts to add obi device and configure GV service.
I am hoping this resolves the issue permanently. I will post again if my service status changes.
A quick packet sniff shows that my Obi202 during TLS key exchange is replying "Unknown CA" to 142.250.81.205 (one of the IPs for accounts.google.com).
It looks like it's possible to install more CA certs into the Obi202 but not quite sure how to upload them.
I just tested and things are now working fine again (Los Angeles Area).
Thanks for the fix!
Update as of 6/13 at 4:40 PM PDT:
Google Voice engineering has identified the cause of the problem and they have implemented a temporary fix. Your devices should resume working later tonight, if not already.
Again: no changes you make to your device(s) will fix this problem.
A longer-term fix will require more work on Poly's side.
got an email from obitalk at 7:45 pm est 6/13/21 saying "your voice sevice has reconnected. you will be able to make and receive calls now. No action is required."
I just test and able to make and receive call now. since this is a temporary fix by google on the back end. don't know how long will last?
The fix will last for now, until it is superseded by a longer-term fix later.
Still receiving the token error here. Is this going to take some time to roll out to all affected units?
Quote from: kes601 on June 13, 2021, 05:19:20 PM
Still receiving the token error here. Is this going to take some time to roll out to all affected units?
Yes. Be patient. If yours is still down tomorrow morning, power it off, wait 10 seconds, and power it on again.
Hello, just wanted to check one thing. My errors are varying over time. The most frequent one in the portal is "Registration Not Required." Is that basically all the same issue and hopefully the upcoming fix will help me? Thanks.
I'm up again. Got the email about a half hour ago but waited. Working so far. Hopeful... 😎
Quote from: garv on June 13, 2021, 05:59:34 PM
Hello, just wanted to check one thing. My errors are varying over time. The most frequent one in the portal is "Registration Not Required." Is that basically all the same issue and hopefully the upcoming fix will help me? Thanks.
Yes.
Quote from: SteveInWA on June 13, 2021, 05:04:43 PM
Update as of 6/13 at 4:40 PM PDT:
Google Voice engineering has identified the cause of the problem and they have implemented a temporary fix. Your devices should resume working later tonight, if not already.
Again: no changes you make to your device(s) will fix this problem.
A longer-term fix will require more work on Poly's side.
thanks very much for your work on this
I appreciate all you've done to try and temper frustrations Steve. Nothing like broadcasting that there is no solution, only to have the very next thread offer "advice" on front-end fixes.
What I find intriguing is that of the two 202 boxes I have (both registered to the same two GV accounts - one in the house, one in the barn), only one of them has been exhibiting this issue. The other has been working/reporting no issues solidly since all of this began.
Is the "known" issue a systemic one that should affect ALL 202s devices or is this a hit/miss kinda thing?
You will see "Registration not required", or you will see a bogus registration to 0.0.0.0, if you repeatedly attempt to re-register by re-booting the device. This is an anti-DOS measure. Don't keep re-trying. Just have a nice evening and look again tomorrow. You should find that the device will successfully register with no action needed on your part.
Quote from: erkme73 on June 13, 2021, 06:10:14 PM
I appreciate all you've done to try and temper frustrations Steve. Nothing like broadcasting that there is no solution, only to have the very next thread offer "advice" on front-end fixes.
What I find intriguing is that of the two 202 boxes I have (both registered to the same two GV accounts - one in the house, one in the barn), only one of them has been exhibiting this issue. The other has been working/reporting no issues solidly since all of this began.
Is the "known" issue a systemic one that should affect ALL 202s devices or is this a hit/miss kinda thing?
Google has many hundreds of servers, load balanced around the world, that support Google Voice. Some of the servers were impacted by the problem, and others were not. When you connect to a server, a load balancing algorithm picks the "best" server for you, based on several factors, including your location and distance to the servers (latency) and which servers are the least busy.
So, it is entirely possible that your devices were connected to different servers.
I can make calls out, but still cannot receive calls. I have the dreaded "Registration Not Required" status.
Many thanks @SteveInWA!!
Still no service, but I'll continue to check it.
I assume this temporary fix should work for the issue "Connecting to 0.0.0.0" as well?
Somewhat OT, but for those that are getting status emails saying service is back--can someone please point me to the instructions to set those up? I've never once received an Obi status email nor see where to configure them.
thx
Quote from: SteveInWA on June 13, 2021, 05:04:43 PM
Update as of 6/13 at 4:40 PM PDT:
Google Voice engineering has identified the cause of the problem and they have implemented a temporary fix. Your devices should resume working later tonight, if not already.
Again: no changes you make to your device(s) will fix this problem.
A longer-term fix will require more work on Poly's side.
Steve, made no changes per your suggestion - but just checked and I'm connected! Thanks for all your help.
Obi200/new england 10:40 pm est
Quote from: TomForum on June 13, 2021, 07:16:44 PM
Many thanks @SteveInWA!!
Still no service, but I'll continue to check it.
I assume this temporary fix should work for the issue "Connecting to 0.0.0.0" as well?
Somewhat OT, but for those that are getting status emails saying service is back--can someone please point me to the instructions to set those up? I've never once received an Obi status email nor see where to configure them.
thx
Yes, "Connecting to 0.0.0.0 is another symptom of the same problem.
The emailed status notes are only sent to devices that are under warranty or on an extended service program AFAIK. The settings are on the OBiTALK web portal's main page.
I have been down for 2 days. Reading this thread since early on, and have tried every "solution" suggest. Unfortunately none of them worked. The last few posts in here mention that google is getting things back online. I unplugged my OBI for about 20 minutes, and when I plugged it back in the status went to connected. I hope this is a long term fix. Located in NEPA. Good luck!
I just got the ObiTalk email saying my device is registered i.e. working again.
This came just after trying incoming and outgoing calls and restarting Obi device. Not sure if that triggered it.
Also, status just changed to "connected".
Outgoing calls seem to work but still not incoming calls.
Update: Never mind that last part. Incoming calls are working too. I had set up GV calls to forward to a cell phone and another family member was using that connection so when I tried to call the home phone, it didn't ring. Doh. The GV line was busy.
QuoteYes, "Connecting to 0.0.0.0 is another symptom of the same problem.
The emailed status notes are only sent to devices that are under warranty or on an extended service program AFAIK. The settings are on the OBiTALK web portal's main page.
Thanks much; you had suspected it was a symptom of the same problem before, just confirming the fix should work for this issue too.
I don't see any such option on the main page (dashboard), but I don't think mine are under warranty. No worries.
Appreciate all of the support!!
My OBi202 went back "Connected" overnight, without my intervention. S-E VA here.
Placed a call, all works.
As of this morning I am connected again.
Left it unplugged overnight since it wasn't doing anything anyway, and on repowering it this morning, success.
Glad I managed to find this thread when I did.
Unplugged and replug in - all three are working again. They did not connect on their own overnight, but had to manually unplug. One Obi200 and two Obi202s, all located in MD with some on Fios and one on Cox
Many thanks to the folks who worked on this for us. My phone is back online.
In Pennsylvania all my phones connected overnight without any intervention.
Thanks to those who got this escalated and fixed quickly. Mine came back online overnight in VA.
Also back on line this Monday morning. Checked Google Voice Settings, and my OBi200 is again listed.
Thanks again to whoever addressed the problem. Power cycling my Obi this morning did the trick.
Maryland suburb of Washington DC on FIOS.
Mapguy.
As of 11:50 EST (2021.6.14) (Virginia) I'm up an running with no intervention on my part!
Thanks to folks behind the scene.
Ditto and Amen!!
Quote from: TomForum on June 13, 2021, 07:16:44 PM
Somewhat OT, but for those that are getting status emails saying service is back--can someone please point me to the instructions to set those up? I've never once received an Obi status email nor see where to configure them.
Quote from: SteveInWA on June 13, 2021, 08:20:13 PM
The emailed status notes are only sent to devices that are under warranty or on an extended service program AFAIK. The settings are on the OBiTALK web portal's main page.
Mine is at:
1... https://www.obitalk.com/obinet/pg/obhdev
2... Click on your device name... Middle pane, top.
3... "Enable OBi Notify"... Check box to the right of "Enable OBi Notify".
4... "Save"... Under "Enable Obi Notify".
It says, "OBiTALK Premium Support required to use this feature".
But I'm not a paid OBiTALK subscriber or under warranty, and I get email notifications.
Sometimes they go to my Yahoo spam.
Quote from: SteveInWA on June 13, 2021, 08:20:13 PM
The emailed status notes are only sent to devices that are under warranty or on an extended service program AFAIK. The settings are on the OBiTALK web portal's main page.
Mine is at:
1... https://www.obitalk.com/obinet/pg/obhdev
2... Click on your device name... Middle pane, top.
3... "Enable OBi Notify"... Check box to the right of "Enable OBi Notify".
4... "Save"... Under "Enable Obi Notify".
It says, "OBiTALK Premium Support required to use this feature".
But I'm not a paid OBiTALK subscriber or under warranty, and I get email notifications.
Sometimes they go to my Yahoo spam.
[/quote]
When I try to check Enable Obi Notify - a popup box says I need to buy a year of Premium support for $10 from Amazon. Won't ley me check the box without that.
Many thanks again SteveInWA!! (and anyone else behind the scenes)
Mine was back up by morning.
Thanks @chiptape for the breadcrumbs. I found it. One is now enabled that's still in warranty.
Still a little weirdness happening?
I just started getting the no response from service provider again on all calls, but the dashboard said connected. I trashed the settings and signed in again and this seemed to fix it for now. Is this issue still a work in progress?
The issue has returned this morning on our Google Voice numbers that connect to OBi202 and Obi200's via VoIP.ms. Calls ring only one time, the caller gets a voice recording with an error message.
Yesterday, all calls were connecting correctly.
*Update*: 'Issue Cleared' after I disabled routing to NoMoRobo.
Checking 'Call History' on my OBi200, I noticed that all calls routed to
NoMoRobo for SPAM filtering were connecting.
To SP4(*18667326184@sipbroker.com) Call Connected
I disabled routing to: 'NoMoRobo' and my test calls to our Google Voice numbers are working correctly now, 'Forwarding' to our VoIP.ms DID 3's, ringing phones on our two OBi202's and the OBi200. I'm able to answer, connect and talk on each one.
Yesterday routing to NoMoRobo was working correctly and did NOT connect on regular calls.
Quote from: BigJim_McD on June 15, 2021, 10:46:07 AM
and Obi200's via VoIP.ms. Calls ring only one time, the caller gets a voice recording with an error message.
Just to clarify........ Are you saying that inbound calls to your GV number that then get forwarded to Voip.ms are not working properly? Even though it's being forwarded it still only rings one time and the caller gets the error message?
Still not working for me. I'm getting the female voice with a 503 error
Verified that I show Connected in Obitalk Dashboard
Rebooted
Power Cycled
Confirmed sign in with GV
Since this issue was reported as resolved by multiple, I went a step further and tried to reregister my device with GV. Deleted settings and tried to recreate
Signing into GV fails with: support.google.com refused to connect.
Verified that I can connect to support.google.com from another browser tab, so the issue appears to be with connections originating from Obitalk
Don't know if this is related to the recent mess - or if anyone here can help - but here goes:
Obi200 / LG Stylus 4 phone, True Wireless.
I've had my GV number, Obi200 and LG phone for years. Whenever someone called my GV number, it rang simultaneously on my 'home phone' and mobile.
The last week it only rings my home phone. I don't believe I changed any GV settings and don't use a Call Blocker.
I have no 'linked' numbers in GV settings on the web - but - when I open the GV app on the phone/settings - it shows my mobile number IS linked. Don't understand why they are different.
Under Incoming Calls - the only 2 devices "enabled" to ring with calls is the Obi200 and my cell. I'm not Screening Calls or have anything else checked. Spam filter is on. Prefer Wi-Fi and mobile data is checked. That's it.
Any help will be appreciated!
Lisa
Quote from: awriter on June 15, 2021, 01:48:06 PM
Don't know if this is related to the recent mess - or if anyone here can help - but here goes:
Obi200 / LG Stylus 4 phone, True Wireless.
I've had my GV number, Obi200 and LG phone for years. Whenever someone called my GV number, it rang simultaneously on my 'home phone' and mobile.
The last week it only rings my home phone. I don't believe I changed any GV settings and don't use a Call Blocker.
I have no 'linked' numbers in GV settings on the web - but - when I open the GV app on the phone/settings - it shows my mobile number IS linked. Don't understand why they are different.
Under Incoming Calls - the only 2 devices "enabled" to ring with calls is the Obi200 and my cell. I'm not Screening Calls or have anything else checked. Spam filter is on. Prefer Wi-Fi and mobile data is checked. That's it.
Any help will be appreciated!
Lisa
Your post is off-topic for this discussion thread, which was about an entirely different issue.
Since your question isn't about your OBiTALK device, you can post it over on the Google Voice help forum:
https://support.google.com/voice/thread/new?hl=en (https://support.google.com/voice/thread/new?hl=en)
I'm wondering if it's possible that a setting on the *OBI* got messed up that's blocking anything but it to ring got changed in this mess. If not, my post is off-topic - but if it's possible, I couldn't know that without posting the problem here.
I didn't mean to chastise you, but no; if your current problem is that inbound Google Voice calls are not ringing on your LG handset, then that is completely unrelated to the token error issue. No-ring issues are very common, and there are some fixes that can be tried to resolve them.
No offense taken, Steve. I'll continue troubleshooting elsewhere. Turns out the phone IS ringing - in the background somewhere - but if it's a GV call, there's no interface to *answer* it! Works fine with calls straight to the phone. If it wasn't maddening, it would be funny. :)
Since Monday June 14, I've been able to place GV calls with my Obihai 200. Have had the three green lights too. However, my Obihai doesn't ring on incoming calls (so I've been answering them on my Android phone.) That had been working just before the whole token error problem started. I logged into my GV account, and it is still set to ring. Any ideas what might be going on here?
Quote from: bartleby on June 18, 2021, 01:34:24 AM
I logged into my GV account, and it is still set to ring. Any ideas what might be going on here?
This is a long shot, but get back into your GV account. Click on the 3-horizontal bar in upper left, and then click on "Legacy Google Voice". Click on "Phones" tab. One of the entries under "Forward calls to:" should start with "sip:", which is your Obi device. If it isn't checked, check it and that should solve your problem. If it is already checked, then I didn't help you.
After nearly a week, it never fixed itself. But for the record, what worked for us was to go to the SP1 configuration page and click the link near the bottom that said "Replace Google Account Credentials." As soon as that update was sent to the phone, the status changed from "Registration not required" to "Connected."
The other shoe has just dropped:
https://support.google.com/voice/thread/114914789/important-information-for-poly-obitalk-consumer-device-use-with-google-voice
I don't blame Google for wanting to move forward with OAuth, they've been moving to it for a few years now.
Basically Google is telling Poly it is time to "sh*t or get off the pot" and update your firmware to the new Certificate. I take hope in this one sentence: "Poly is working on a new firmware release."
If Poly does release the new firmware, this obitalk forum will have plenty of notice and places to get it. However, if Poly is not interested in the consumer Poly devices, we'll see the rest of the approved GVoice poly devices become unsupported and unapproved for Google Voice (like Obi100).
Quote from: MSRobi on June 25, 2021, 06:48:05 PM
The other shoe has just dropped:
https://support.google.com/voice/thread/114914789/important-information-for-poly-obitalk-consumer-device-use-with-google-voice
I don't blame Google for wanting to move forward with OAuth, they've been moving to it for a few years now.
Basically Google is telling Poly it is time to "sh*t or get off the pot" and update your firmware to the new Certificate. I take hope in this one sentence: "Poly is working on a new firmware release."
If Poly does release the new firmware, this obitalk forum will have plenty of notice and places to get it. However, if Poly is not interested in the consumer Poly devices, we'll see the rest of the approved GVoice poly devices become unsupported and unapproved for Google Voice (like Obi100).
This is a digital certificate expiration, which is standard practice across the Internet. All digital certificates have an expiry date, and that's what my announcement was about. It was not about OAUTH.
To be clear: Google has no control over Poly's business decisions. All they can do is to inform Poly of the need for Poly to update their products, and to answer any questions Poly may have. The rest is up to Poly.
There is no point whatsoever to speculate, whine, rant, create conspiracy theories, or otherwise try to determine what Poly will do and when they will do it. All I can confirm is that they are definitely working on it. How and when they will deploy the update is unknown and is up to them.
Quote from: SteveInWA on June 25, 2021, 06:54:53 PM
This is a digital certificate expiration, which is standard practice across the Internet. All digital certificates have an expiry date, and that's what my announcement was about. It was not about OAUTH....
***All I can confirm is that they are definitely working on it...up to them***
My apologies in bringing up OAuth, it was an error. I'm so used to updating credentials due to the OAuth change that I thought it was the reason they are updating the certificate.
I am correct that this new information is all related to why we had the "token error" in the first place, so that is why I posted here in this thread.
Anyhow, the big point is what I bolded in quoting your message, Poly is at least aware they have to do something, and we all hope they follow through....this is the permanent fix discussed in this thread, we are living with a temporary fix now. As a programmer, I suspect that updating the firmware to use a new certificate should be trivial for Poly to implement. How motivated or interested or even capable of doing it is unknown.
I had the Token Error on one of my devices (Obi200) up till yesterday. Reboots or DNS settings didn't help. Then I went into Security settings of the Google account (https://myaccount.google.com/security ) used for that device, and I noticed that "Third-party apps with account access" section (https://myaccount.google.com/permissions ) doesn't have Google Voice listed anymore. I don't know how it fell off, I'm sure I had it configured correctly in the past because I've been using GV on that device for years. Regardless, it's an easy problem to fix: I just did the "Replace Google Account Credentials" operation in Obitalk Dashboard, and it started working right away.
Quote from: andrepod on June 27, 2021, 11:22:59 AM
I had the Token Error on one of my devices (Obi200) up till yesterday. Reboots or DNS settings didn't help. Then I went into Security settings of the Google account (https://myaccount.google.com/security ) used for that device, and I noticed that "Third-party apps with account access" section (https://myaccount.google.com/permissions ) doesn't have Google Voice listed anymore. I don't know how it fell off, I'm sure I had it configured correctly in the past because I've been using GV on that device for years. Regardless, it's an easy problem to fix: I just did the "Replace Google Account Credentials" operation in Obitalk Dashboard, and it started working right away.
I've looked all over the Obitalk Dashboard and have not found a way to "Replace Google Account Credentials" . Can you be a tad more specific on how to do this?
Quote from: Skip367 on June 29, 2021, 12:09:46 PM
I've looked all over the Obitalk Dashboard and have not found a way to "Replace Google Account Credentials" . Can you be a tad more specific on how to do this?
From the Obitalk Dashboard
Click on the blue "gear" icon for your device
Under Settings column, click on the blue gear icon for the SP containing your GV config
You should see Replace Google Account Credentials at the bottom of the page
Quote from: SteveInWA on June 25, 2021, 06:54:53 PM
This is a digital certificate expiration, which is standard practice across the Internet. All digital certificates have an expiry date, and that's what my announcement was about.
All I can confirm is that they are definitely working on it...up to them.
Here's the announcement: http://www.obitalk.com/forum/index.php?topic=18430.0
In the meantime, it appears the "fix" for users is to delete their google credentials for whichever SP(1,2 or whatever) is producing the problem, then reenter them as at the first time it was set up. Hopefully that will stop the errors mentioned in this thread. No guarantees.
I'd like to extend a HUGE truckload of thanks for SteveInWA's tireless efforts in helping us all get to the bottom of this. Thanks to you (and some nameless others whom I'd also like to thank - please pass the word), my phone is now working again, and has been for a few weeks, and I'm just waiting for the firmware update from Poly.
SteveInWA, I hope you still have some hair left. 😳😬😎
Quote from: Moonwalker on June 30, 2021, 11:10:48 AM
Quote from: SteveInWA on June 25, 2021, 06:54:53 PM
This is a digital certificate expiration, which is standard practice across the Internet. All digital certificates have an expiry date, and that's what my announcement was about.
All I can confirm is that they are definitely working on it...up to them.
Here's the announcement: http://www.obitalk.com/forum/index.php?topic=18430.0
In the meantime, it appears the "fix" for users is to delete their google credentials for whichever SP(1,2 or whatever) is producing the problem, then reenter them as at the first time it was set up. Hopefully that will stop the errors mentioned in this thread. No guarantees.
Thank you for you kind comments!
Actually, no: for the vast majority of users who were impacted by the outage, the problem was fixed remotely, and no user action is required. If a user made changes to their OBi configuration, they may have messed up their device's ability to re-authenticate to Google Voice. In that case, then yes, you would need to follow the bulleted steps in my post, here: https://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076 (https://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076)
I have followed every step 1) set DNS 2) delete and re-add device, 3) uncheck 0auth, and still get the "No registration required" on the Obitalk dashboard. In the Obi device on SP1 I get "Connect Failed: No Response (server=216.239.36.145; retry in 45s)". I have read the chatter on this forum nauseum but have not been able to identify a verified and supported solution. How frustrating. This has every sign of being a authentication problem. Looks like I will have port my number to a pay service provider again after spending four years using googlevoice through Obihia.
Quote from: holtdw01 on July 12, 2021, 11:43:19 AM
I have followed every step 1) set DNS 2) delete and re-add device, 3) uncheck 0auth, and still get the "No registration required" on the Obitalk dashboard. In the Obi device on SP1 I get "Connect Failed: No Response (server=216.239.36.145; retry in 45s)". I have read the chatter on this forum nauseum but have not been able to identify a verified and supported solution. How frustrating. This has every sign of being a authentication problem. Looks like I will have port my number to a pay service provider again after spending four years using googlevoice through Obihia.
Please don't post in this thread. Your question was already addressed elsewhere in this forum.
http://www.obitalk.com/forum/index.php?topic=18338.msg109260#msg109260 (http://www.obitalk.com/forum/index.php?topic=18338.msg109260#msg109260)
Based on the banner now up on obitalk.com, the new firmware is out and will be auto-updated on 8/5/2021 at 17:00 PDT. You can also do the update manually, follow the instructions linked from the banner. I updated my Obi202, no issues, and it connected back up.
I also followed the instructions on the banner to upgrade to the 8680 firmware. No problems so far.
I followed the instructions in that banner to upgrade to 8680. No problems seen in the upgrade process or subsequent operation.
Unfortunately, I just purchased, then upgraded the Obi202 to the latest firmware, and I continue to get configuration errors for Google Voice, namely:
Connect Failed: 403 Forbidden
Not surprisingly, when you try to make a call, you hear:
"The number you dialed XXX-XXX-XXXX has not received a response from the service provider"
I have tried to delete from dashboard, factory reset, multiple times but to no avail. Are there any optics as to why?
Quote from: mattd on September 09, 2022, 04:14:05 PMUnfortunately, I just purchased, then upgraded the Obi202 to the latest firmware, and I continue to get configuration errors for Google Voice, namely:
Connect Failed: 403 Forbidden
Not surprisingly, when you try to make a call, you hear:
"The number you dialed XXX-XXX-XXXX has not received a response from the service provider"
I have tried to delete from dashboard, factory reset, multiple times but to no avail. Are there any optics as to why?
Given that the OBi ATAs are no longer manufactured nor sold as new, where did you get it, and was it claimed to be new or used? It may simply be defective.
Have you tried performing a hardware restore to factory defaults (by using a paper clip and pressing and holding down the recessed switch on the bottom of the device for at least 10 seconds, then releasing the paper clip and letting it fully reboot)? If not, do that next.
Then, add it back to the OBiTALK dashboard following the **5xxxx procedure. If that's successful, try calling the echo test number (**9 222 222 222). Do you hear "Welcome to OBiTALK...."? If not, something basic is wrong with the device or its Ethernet connection.
If that works, then use a desktop or laptop computer's web browser, sign into the correct Gmail account that holds your Google Voice number, and go here: https://voice.google.com/settings (https://voice.google.com/settings).
Do you see your Google Voice number at the top of the page? If not, then either you don't have one, or this is the wrong account. Find the right account and number.
If you found it, then try to make an outbound call from the browser. Does that work? If so, call your Google Voice number from some other telephone number, not a linked number. Does that work? If so, then your Google Voice service is working correctly.
If that all worked, then follow my instructions carefully to set up the device from scratch (omitting the steps we've already done here):
url]https://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076[/url]
Fix from Reddit Post: https://www.reddit.com/r/Googlevoice/comments/pth6oi/obi_200_not_working_again_with_google_voicetoken/ (https://www.reddit.com/r/Googlevoice/comments/pth6oi/obi_200_not_working_again_with_google_voicetoken/)
"go to the OBiTALK dashboard, click on the SP1-SP4 slot you are using for Google Voice, acknowledge the emergency calls warning, then click "Replace Google Account Credentials" and follow the instructions. Be absolutely certain that you are signed into the correct Gmail account that holds your Google Voice phone number.:"